112 replies to this topic

[VikingN1nja]

Matthew Craig, on 05 March 2014 - 09:26 AM, said:

Couple of points, for users who recently bought a computer running Windows 8 or that came with DX11 by default they no longer need to downgrade to DX9 to be able to run the game so there is benefit beyond just performance/visuals.

For those that have worked in development you know that engine integrations, especially on a rapidly moving project like this that code branches have a tendency to diverge, its not as simple as keep it on the test servers until we're 100% happy with it. To do that we incur constant integration overhead to keep it up to date with the main trunk and exhaust more QA resources in the process. If you're not happy with where DX11 is at currently you're welcome to continue to use DX9 this is why we didn't switch to DX11 by default at this time, but at least now users have an option.

Personally I'm happy to now be able to push forwards with DX11 to make further improvements to the game knowing its not time invested in a code path that will quickly become legacy code.

Hi i had my game running pretty good in DX9 after patch have resorted to driver sweep,reinstalling drivers, delteting cfg's and running repair tool(something i never had to do).
The min FPS is usually lower and certains games I am gone sub 20.
Sometimes mech lab is 60 fps other times 15.
With everything in dx9 mode there is a ghosting effect on mechs which i never had before and generally fps is lower probabaly due to this effect and it keeps going low 20's never had this before.

Please fix asap it's ruining the game something is broken.

EDIT: further testing consistently 20-25 fps lowest(prepatch: 30-35)
NOTE: settings are the same just less FPS.
SIDE NOTE: HUD eats 20 fps.

Edited by omegagun, 06 March 2014 - 07:06 AM.

[Flapdrol]

I've not tried it yet, but being able to use msaa will be a big improvement for me.

Edited by Flapdrol, 06 March 2014 - 06:24 AM.

[Shamous13]

Shamous13, on 05 March 2014 - 05:40 AM, said:

Try turning v-sync on to reduce your gpu load and temps. your card could be throttling its self causing the CTD.

I had some nasty problems last night running DX11, CTD, missing parts on mechs, missing terrain, when loading in to mech lab the componets on a mech would load in one section at a time. running the repair tool and removing the systemoverride.cfg solved the problems.

I found that I got an average 16% increase in FPS, I did however notice that my gpu usage in crosfire mode was wonky. My 1st gpu was running at 40% avg while my second gpu was running at 99% the hole time. any Ideas?

I've been able to get crossfirex working reliably and found out why my setup wasn't load balancing, its a ATI issue. see this post for the fix.

[VikingN1nja]

So it's broken and needs fixing or buy a 20 core CPU with 2 GTX Titans.

[MercJ]

Just posted this in another thread, since this one is pretty active I thought I'd put it here too, as a POSSIBLE SOLUTION (at least something for more people to try).

Lupin, on 06 March 2014 - 12:54 AM, said:

I have had the same problem on a lot of maps played and testing ground.
In testing ground glitching in FPS stops after I run the whole map. Wonder if it's just DX11 loading up textures/graphics?

I think you're on to something with this. Coupled with the cache errors OP was getting, I really think this has something to do with it.

Like all of you, I was getting weird FPS drops/stutters with the DX11 patch, went back to DX9 where the experience was a little better. But with an i5-2500k at 4.6-5 GHz and an R9 290 that's watercooled, I shouldn't be having FPS drops at all (was getting ~90 with Very High settings @ 1920x1200), so the stuttering has been irking me a bit.

Loaded up the testing grounds just now, same stuttering. However, running all the way around the map, looking in every direction, on the second "lap" the FPS was much more consistent. Still a couple hiccups here and there, but no drops to 20FPS like before. Very smooth. I'd say give it a try - since DX11 is a new rendering path, I suppose it makes sense to have to cache everything again on new maps.

Try running around each map a few times, making sure to look in every direction to "load" textures/shaders/etc. See what happens on the second lap.

Edited by MercJ, 06 March 2014 - 07:35 AM.

[El Rizzo]

Quote

since DX11 is a new rendering path, I suppose it makes sense to have to cache everything again on new maps.

It doesn't make sense ... you have to cache a map every time you load it, otherwise your Ram would just get filled up with useless data until it is full. Of course it runs more smoothly once all the textures etc. are loaded into the ram/vram but thats the same for dx9 and quite normal and happens every time you load into a new match.

[MercJ]

El Rizzo, on 06 March 2014 - 07:44 AM, said:

It doesn't make sense ... you have to cache a map every time you load it, otherwise your Ram would just get filled up with useless data until it is full. Of course it runs more smoothly once all the textures etc. are loaded into the ram/vram but thats the same for dx9 and quite normal and happens every time you load into a new match.

Are you having the severe stuttering issues too? If so, please test this out so it can be confirmed or tossed out. I haven't worked on this game, so I have no idea how they load maps or use textures, their implementation might be different?

[El Rizzo]

I only have stuttering right after the match starts, after that it runs smooth, i would say the first 10-20 seconds after the game has started have stuttering.

I am using the dx9 renderpath and the updated ultra high maxed detail user.cfg from Colonel Pada Vinson @1080p.

But referring to my previous post, it doesn't make sense from a technical point of view like i tried to explain.

Edited by El Rizzo, 06 March 2014 - 08:18 AM.

[Corvus Antaka]

Wandre, on 04 March 2014 - 02:44 PM, said:

I had a drop from 60 FPS to 30 FPS in the Mech Bay at High performance settings on 1920x1080 when I enabled DX11. I toned it back to Medium and it went back to 60. I have yet to test this in an actual match.

vsync on will cause this.

use DX9, it works just fine.

anyone bitching about dx11 is being silly, Dx9 works fine and nothing has changed unless you use a cfg setup.

dont use dx11 if it causes you problems you have to tinker or wait for updates. its not a big difference visually anyhow.

Edited by Colonel Pada Vinson, 06 March 2014 - 10:43 AM.

[cSand]

omegagun, on 06 March 2014 - 06:35 AM, said:

So it's broken and needs fixing or buy a 20 core CPU with 2 GTX Titans.

Set all your video card settings to "application controlled" (that's the AMD description, nVidia has the same option I'm not sure of the wording though). Especially don't force Anti-Aliasing settings, MWO doesn't seem to like that
Turn off MSAA if it's on.
I'm assuming you have checked all your video settings in game but if not do it now
When you change AA or DX settings in the game, restart the client. If you alter your detail settings I have found it's not a bad idea to clear your shaders folder as well.

El Rizzo, on 06 March 2014 - 07:44 AM, said:

It doesn't make sense ... you have to cache a map every time you load it, otherwise your Ram would just get filled up with useless data until it is full. Of course it runs more smoothly once all the textures etc. are loaded into the ram/vram but thats the same for dx9 and quite normal and happens every time you load into a new match.

There is a shaders folder that gets populated the first time you run the game from a fresh/repaired install and I have noticed that when I clear the shaders my first few matches have a little stuttering for the first 10-20s (presumably as this folder gets populated)

Edited by cSand, 06 March 2014 - 11:02 AM.

[VikingN1nja]

Colonel Pada Vinson, on 06 March 2014 - 10:42 AM, said:

vsync on will cause this.

use DX9, it works just fine.

anyone bitching about dx11 is being silly, Dx9 works fine and nothing has changed unless you use a cfg setup.

dont use dx11 if it causes you problems you have to tinker or wait for updates. its not a big difference visually anyhow.

Your worng man not everyone has same spec, some are doing better than others i have lost 10 fps in dx9 mode.

[Corvus Antaka]

omegagun, on 06 March 2014 - 11:01 AM, said:

Your worng man not everyone has same spec, some are doing better than others i have lost 10 fps in dx9 mode.

have you tried turning vsync off?

[VikingN1nja]

cSand, on 06 March 2014 - 10:59 AM, said:

Set all your video card settings to "application controlled" (that's the AMD description, nVidia has the same option I'm not sure of the wording though). Especially don't force Anti-Aliasing settings, MWO doesn't seem to like that
Turn off MSAA if it's on.
I'm assuming you have checked all your video settings in game but if not do it now
When you change AA or DX settings in the game, restart the client. If you alter your detail settings I have found it's not a bad idea to clear your shaders folder as well.



There is a shaders folder that gets populated the first time you run the game from a fresh/repaired install and I have noticed that when I clear the shaders my first few matches have a little stuttering for the first 10-20s (presumably as this folder gets populated)

Done it all.

[cSand]

omegagun, on 06 March 2014 - 11:07 AM, said:

Done it all.

Are your problems when running DX11?

I think you are right about the ghosting in DX9 causing the lower FPS. IF we can fix that you will probably be good to go (in DX9 at least)

Edited by cSand, 06 March 2014 - 11:09 AM.

[Corvus Antaka]

cSand, on 06 March 2014 - 11:08 AM, said:

Are your problems when running DX11?

i think hes only got dx9 problems. nothing has changed with dx9 except maybe a value or 2 in cfg settings. it's possible something like smoke is lagging him, but he needs to just cull graphics to low for now to see if that brings his fps problems up or theres a deeper problem.

you need to run the repair tool as well first.

[cSand]

Colonel Pada Vinson, on 06 March 2014 - 11:09 AM, said:

i think hes only got dx9 problems. nothing has changed with dx9 except maybe a value or 2 in cfg settings. it's possible something like smoke is lagging him, but he needs to just cull graphics to low for now to see if that brings his fps problems up or theres a deeper problem.

you need to run the repair tool as well first.

Indeed. Certain smokey parts (or those kinds of effects) drop my laptop down about 10-15 fps if I get really close to them. Set all sliders to low and other settings to "off", and turn them up/on one at a time until you see a performance degradation.

This may sound silly, but, you don't have motion blur on do you?

Edited by cSand, 06 March 2014 - 11:19 AM.

[VikingN1nja]

Colonel Pada Vinson, on 06 March 2014 - 11:04 AM, said:

have you tried turning vsync off?

I literally tried everything, deleted cfg's so repair would replace, new drivers, cleared cahce.

Consistent 20-25 fps games min whereas before it was 30-35 and smooth enough to play i am even seeing -20.

[cSand]

Is resolution set to your monitor's native res?
Try turning the post processing slider to low... just throwing out some things here from other games I have seen ghosting in.

[Jabilo]

My performance is in the toilet.

The game just stutters and drops in to the 40s all the time. However 40 fps does not tell the whole story - frame timings are so poor the game is unplayable.

Bear in mind that I am monitoring GPU and CPU core usage on EVGA Precision and I am getting stuttering (DX9 and DX11) despite no core or the GPU being at full load.

On the contrary, my GTX 770 can max 60 fps (v-sync) at 60% load on very high, yet I still experience frame rate drops.

It was so difficult to drive my spider today and fire my weapons accurately that I nearly put my keyboard through the window.

Games are supposed to be fun and when it becomes an exercise in frustration I quit. Will come back next patch and hope for the best.

Before anyone starts, as someone who has been building their own PCs for a decade, yes I have tried all the usual suspects.

*takes deep breath*

What I really want is someone from PGI to come on and say "yes it is usual for frames to dip in to the 40s even when you have power to spare. This is part of the engine and coding of the game and is usual and we are working to improve it".

As it is, this denial that there are optimisation problems with the game just frustrates me and makes me want to scream..

Edit - my spec

Win7
I5 2500k
GTX770
8 Gigs fast DDR3
Fast SATA 6 Gbit SSD
Latest drivers for everything (of course)

Tried:

System file check
Cleaned and reinstalled latest video drivers
Uninstall game, clear all remnants from registry etc. and full reinstall.
Multiple settings in game in both code paths.
Checked benchmarks, temperatures core and GPU usage as well as VRAM.
Memtest, Direct X Diagnostic etc.
No overclocks, no bloatware or crap on my machine.
Other games run beautifully (GTX770 eats Crysis 3 for breakfast without MSAA).

I'm done.

Edited by Jabilo, 06 March 2014 - 11:56 AM.

[VikingN1nja]

cSand, on 06 March 2014 - 11:24 AM, said:

Is resolution set to your monitor's native res?
Try turning the post processing slider to low... just throwing out some things here from other games I have seen ghosting in.

I am a certified technician I have covered all avenues there is a problem with what PGI have done here. All my settings are as they were before the patch.

Jabilo, on 06 March 2014 - 11:41 AM, said:

My performance is in the toilet.

The game just stutters and drops in to the 40s all the time. However 40 fps does not tell the whole story - frame timings are so poor the game is unplayable.

Bear in mind that I am monitoring GPU and core usage on EVGA Precision and I am getting stuttering (DX9 and DX11) despite no core or the GPU being at full load.

On the contrary, my GTX 770 can max 60 fps (v-sync) at 60% load on very high, yet I still experience frame rate drops.

It was so difficult to drive my spider today and fire my weapons accurately that I nearly put my keyboard through the window.

Games are supposed to be fun and when it becomes an exercise in frustration I quit. Will come back next patch and hope for the best.

Before anyone starts, as someone who has been building their own PCs for a decade, yes I have tried all the usual suspects.

*takes deep breath*

What I really want is someone from PGI to come on and say "yes it is usual for frames to dip in to the 40s even when you have power to spare. This is part of the engine and coding of the game and is usual and we are working to improve it".

As it is, this denial that there are optimisation problems with the game just frustrates me and makes me want to scream..

I feel ya dude not sure what they have done.

Edited by omegagun, 06 March 2014 - 11:50 AM.