Jump to content

Public Test - Directx11 - New Issues


136 replies to this topic

#101 frag85

    Member

  • PipPipPipPipPip
  • 141 posts

Posted 07 November 2013 - 04:28 PM

Crossfire still bugged like the official patch. Default profile there is next to no scaling even though GPU usage are each high. AFR Friendly there is 100% scaling, but an even worse flicker than DX9.

Win 7 Pro
CF7970, 13.10B8 drivers.

Edited by frag85, 07 November 2013 - 04:29 PM.


#102 Rhialto

    Member

  • PipPipPipPipPipPipPipPipPip
  • Philanthropist
  • 2,084 posts
  • Twitter: Link
  • LocationQuébec, QC - CANADA

Posted 07 November 2013 - 04:37 PM

Win 7 64 - 8GB - GTX660 Ti - 331.65

1920x1080 Full Screen DX11 Very High

I click to search a game and just when it switch to enter game, it crash. ;)

#103 RasputiN

    Member

  • PipPipPip
  • Legendary Founder
  • Legendary Founder
  • 92 posts
  • LocationVenice

Posted 07 November 2013 - 04:37 PM

CPU - Quad Core I7-3770
RAM - 8GB
GPU - Radeon 7870, driver version 9.012-121219a-151592C-ATI
Resolution 1920x1200
Win Vista Home 64bit with last service pack

minor loss of frames but smooth and less texture corruption

minor issue: activating V/sync drop fps from 60/70 to 30 and less

#104 Krav

    Member

  • Pip
  • 19 posts

Posted 07 November 2013 - 04:54 PM

System:
Spoiler


Both red & blue bars were filled in on all cap points on conquest mode in the canyon map.

I'm not smart enough to get my photo to link from dropbox... =/

#105 Rhialto

    Member

  • PipPipPipPipPipPipPipPipPip
  • Philanthropist
  • 2,084 posts
  • Twitter: Link
  • LocationQuébec, QC - CANADA

Posted 07 November 2013 - 04:59 PM

View PostRhialto, on 07 November 2013 - 04:37 PM, said:

Win 7 64 - 8GB - GTX660 Ti - 331.65

1920x1080 Full Screen DX11 Very High

I click to search a game and just when it switch to enter game, it crash. ;)

Got it to work after a few attempts... wonder if it's connectivity/too much load on test servers? I ask because when it crash and I restart, sometimes I get a black screen that last either a few seconds up to like 20 seconds.

Edited by Rhialto, 07 November 2013 - 05:16 PM.


#106 Waldex

    Member

  • PipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 158 posts

Posted 07 November 2013 - 05:02 PM

Two issues

First, I was able to save a loadout with one too many points of armor for a valid weight loadout (CDA-3M) when using ferro and endo.

Second, was unable to import action maps effectively, even after deleting them and a copied file from standard build they did not update controls, even after a restart.

#107 Colddawg

    Member

  • PipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 317 posts
  • LocationYork, Pennsylvania

Posted 07 November 2013 - 05:06 PM

Spoiler


TXAA looks great. There is a good bit of performance drop from using POSTAA
Using TXAA gave me some lag between the controls and the 'Mech at times, but not always.

DX11 seems more stable than DX9 so far.

Not sure if this is a bug, but in thermal and night vision on River City the "emergency shutdown" sign shows up clearly. Night vision, this may be okay, but for thermal the whole sign should be one/similar in temperature.

#108 Muffinator

    Member

  • PipPipPipPipPipPip
  • Mercenary
  • Mercenary
  • 447 posts

Posted 07 November 2013 - 05:13 PM

Spoiler



I am getting a lot of texture 'popping' at around 150m as I walk forwards. All the textures are kind of flickering into a higher res version or something. This was noticeable on all levels I tried but by far the worst on Alpine, where the textures kind of flicker and flash in to view.

First time into any map I get a lot of grey blank textures for a second under dx11 or weird yellow textures under dx9.

When loading canyon network in testing grounds, after the loading screen I get no cockpit and just a view of sky and haze, no geometry. I have to kill the client through task manager from there. This happened twice, then the third time it did load and went through all the texture caching/popping.

First time into any map the cockpit renders in a very weird way - overlays and chunks of cockpit pop in to view bit by bit. I guess this is just the shaders caching but it looks a lot worse than when I am running for the first time under dx9 in production.

In Forest Colony I pressed escape and the game crashed to desktop.

Can't hear footsteps.

This may be minor but I noticed it doesn't play nice with my second monitor. Sometimes on starting it changed the resolution of a browser window on my main monitor so that it poked half way into my second monitor. Sometimes my second monitor went black while the map loaded. This was mainly an issue for my son who was watching playschool on the second monitor.

Edited by Muffinator, 07 November 2013 - 05:15 PM.


#109 Kunae

    Member

  • PipPipPipPipPipPipPipPipPip
  • 4,303 posts

Posted 07 November 2013 - 05:14 PM

GTX 680, no TXAA option.

#110 Percimes

    Member

  • PipPipPipPipPipPip
  • The Flame
  • The Flame
  • 264 posts

Posted 07 November 2013 - 05:17 PM

View PostMatthew Craig, on 07 November 2013 - 10:28 AM, said:


Anyone experiencing this, if you have time to try updating your drivers to latest that may help. If not then we still have some work to do most likely, if you can post your dxdiag info so we can try and repro with your same setup.

Only got this on my first launch, went well for the next 5 matches or so after. Can't update my nvidia drivers past 314.22 though since everything past them are borked on GTX 560Ti.

#111 Weaselball

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 670 posts
  • LocationHell's ********, AKA Fresno.

Posted 07 November 2013 - 05:18 PM

Radeon HD 6670, TXAA not an option. The game ran fine however - or at least just as good as it does in DX9. Not really a noticeable improvement, though not any worse.

#112 Kunae

    Member

  • PipPipPipPipPipPipPipPipPip
  • 4,303 posts

Posted 07 November 2013 - 05:25 PM

View PostMuffinator, on 07 November 2013 - 05:13 PM, said:

This may be minor but I noticed it doesn't play nice with my second monitor. Sometimes on starting it changed the resolution of a browser window on my main monitor so that it poked half way into my second monitor. Sometimes my second monitor went black while the map loaded. This was mainly an issue for my son who was watching playschool on the second monitor.

Turn off Desktop Composition, on the compatibility tab of MWO icon properties.

That is the workaround.

#113 Sarah Dalrymple

    Member

  • PipPipPipPipPipPip
  • 494 posts
  • Google+: Link
  • LocationSkye March, Hesperus II

Posted 07 November 2013 - 05:32 PM

I can't get the test version of MWO to install. It wants to uninstall the production version. I did, and the installer just re-installs the production version... which I then spent 2 hours updating.

Win8 Pro 64-bit, Radeon HD7950

#114 Treye Snow

    Member

  • PipPipPipPipPip
  • 160 posts
  • LocationNot where I want to be

Posted 07 November 2013 - 05:34 PM

Nvidia GTX 460v2
AMD Phenom 9740 2.4ghz
6g DDR2 Ram
Windows 8

Screen resolutions beyond 1280x1080 were non-existent.

Live versions go up to my current resolution of 1768x992 (I have a TV for a monitor, hence the awkward resoltuon) and on the PTR it wouldn't even go near it in any screen format be it windowed, full window, or fullscreen.

Unsure if this is a bug on the options screen or on DX11 itself. Either way,without the resolution suppot I can't even test the darn feature.

#115 Fragger56

    Member

  • PipPipPip
  • Elite Founder
  • Elite Founder
  • 60 posts

Posted 07 November 2013 - 05:37 PM

Specs:
Core I5 3570K
Asrock z77 Extreme 6
16gb ram
win 7 64 bit
6970

Experiencing a cap of 30fps on river city even though vsync is off.
Some maps run at 60fps solid when moving forward, though turning incurs a FPS drop while turning sometimes.

Otherwise, pretty stable

Edit:
After further testing, it seems that river city, river city night, caustic valley, forest colony and parts of crimson strait have this issue.
on crimson strait, its kind of wierd, as depnding on my location and facing direction the FPS cap would come and go.

Also I'm calling this a FPS cap as each time my FPS drops to a SOLID 30fps that does not waver and at the same time my GPU drops to less than 50% core utilization.

Sometimes using regular zoom or advanced zoom will uncap framerates, but again, it varies map to map.

My guess would be bad/incorrect vis data for dx11 causing wierd framerate issues.

Edit 2:
It seems that toggling my hud has a effect at times also, but again is inconsistant in its effects on framerate.

I also noticed when reviewing the video footage i took to document the issues above, while I have motion blur disabled in the options, motion blur effects are still being applied to the inside of the cockpit, IE the frame of the cockpit, while everything outside the mech does not have motion blur.

Edited by Fragger56, 07 November 2013 - 06:08 PM.


#116 JDH4mm3r

    Member

  • PipPipPipPipPipPip
  • The Hammer
  • The Hammer
  • 308 posts

Posted 07 November 2013 - 05:43 PM

system:

Windows 7 64bit
Intel Core i5 3570K @ 3.4GHz
G-skill 8GB total ram
AMD Radeon 7900HD 3gb



here's what i encountered today:

I started the game off in Very High settings and there was some minor FPS issues and minor slow loading graphics, but the game performed smoothly on the first match.

2nd match was problematic: I encountered FPS issues where i normally see 60FPS, it was random from 60-20 while in a jenner. Switched back to high settings and the game was bearable. Once match was done, clicked to go back to lobby, but instead game crashes with no warning message.

reloaded game and ran the next 4-5 matches on high with no issues;

#117 Mister Blastman

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Survivor
  • Survivor
  • 8,444 posts
  • LocationIn my Mech (Atlanta, GA)

Posted 07 November 2013 - 05:48 PM

View PostGalil Nain, on 07 November 2013 - 04:28 PM, said:


Have you tried pressing the Auto-Adjust button on your monitor? I've seen other programs do the same thing (albeit rarely) and this solves it in nearly all cases.

I would guess that the video being sent to your monitor is off-centre, so it simply displays nothing. Power-cycling kicks off an auto-adjust, which fixes it, but an auto-adjust should fix it in less button-presses, not to mention less time. Still doesn't explain why the app, in this case MWO, is sending video to the monitor offset from centred?!?


Exactly. This bug makes no sense.

#118 Pirate2Ninja

    Member

  • PipPip
  • Bridesmaid
  • 32 posts

Posted 07 November 2013 - 05:57 PM

Windows 8, 64-bit
i7-3840QM
RAM 16GB
GTX 670MX
NVidia driver 331.65

(known issues)
-no footsteps sounds
-can't change resolution

Other-
-Sometimes changing vision modes is sluggish
-A couple times after finishing a match, clicking "exit match" on the summary screen closes the client
-If a match is launched and connects when I am focused on another window it starts in a unboardered window instead of fullscreen

#119 NuclearPanda

    Member

  • PipPipPipPipPipPipPip
  • 619 posts
  • LocationUpstate NY

Posted 07 November 2013 - 05:59 PM

Thermal Vision displays incorrectly/not at all

System

Spoiler


Description

Spoiler


Steps to Reproduce

Spoiler


Screencapture
Posted Image

Edited by NuclearPanda, 07 November 2013 - 06:05 PM.


#120 Icebergdx

    Member

  • PipPipPipPipPip
  • Bad Company
  • Bad Company
  • 168 posts
  • LocationEastern Washington

Posted 07 November 2013 - 06:13 PM

Win 7 Home Premium
GTS 240 (old card)
Intel i7 2.67
8 Gig Ram

Normally tun game on Low to stay near 30 FPS, I was able to run on medium at 30 FPS.

I did notice 3-4 FPS drops on the older maps (Forrest, Frozen city), and 3-4 FPS faster on new maps (Tourmaline, Terra Therma)

Has a weird technicolor screen behind the team info on launch a couple of times, and once when clicking to shift from mech to mech after I died, but only a flash for about .5 sec. Other than that, I LIKE IT!!!!





13 user(s) are reading this topic

0 members, 13 guests, 0 anonymous users