19 replies to this topic

[Alcom Isst]

The Screenshot:

Spoiler

The Settings:


The PC:


The Frame-rate:
45 frames/second

The Curiosity:
I must wonder: What is going on in the image above to make the game run at 45 frames/second? It doesn't look particularly snazzy. I've seen better looking games run at 60 on weaker rigs.

The screenshot is of a cherry picked angle and scenario, but as I tested my Dire Wolf I noticed that I was getting 45-55 FPS in many places and angles. This wasn't even in a game, this was in the testing grounds.

So what is MechWarrior Online doing in this screenshot and elsewhere to run like this? I'm quite curious.

[Flapdrol]

As you posted in an image from testing grounds it's probably the MSAA + high shaders and other fancy stuff that's killing performance.

In online matches with msaa off you're probably cpu limited.

[Alcom Isst]

Flapdrol, on 08 January 2015 - 03:18 AM, said:

As you posted in an image from testing grounds it's probably the MSAA + high shaders and other fancy stuff that's killing performance.

In online matches with msaa off you're probably cpu limited.

I'm not turning off MSAA. Jaggies are a sin to me, and I'll wreck devastation upon every other setting first before I turn that off.

[Navid A1]

Alcom Isst, on 08 January 2015 - 04:07 AM, said:

I'm not turning off MSAA. Jaggies are a sin to me, and I'll wreck devastation upon every other setting first before I turn that off.

It's the MSAA sadly.!

Turn it off... and forget about it. Run away from the "max out everything" syndrome.!

"I like the jaggies" <-- repeat every minute.

[IG 88]

-Ambient Occlusion: off or performance
-Anisotropic Filtering: controlled by app
-Antialiasing - Gamma Correction: off
-Antialiasing - Mode: controlled by app
-CUDA - GPUs: all
-Multi-display/Mixed-GPU Acceleration: Single Display
-Power Management Mode: quality
-Texture Filtering - Anisotropic: controlled by app
-Texture Filtering - Negative LOD: autorized
-Texture Filtering - Quality: quality
-Texture Filtering - Trilinear Optimization: on
-Threaded Optimization: Auto
-Triple Buffering: off
-Vertical Sync: controlled by app

cl_fov = 75
gp_option_ShowCockpitGlass=0
r_DepthOfField=0
r_HDRGrainAmount=0.0

resolution: native
windowed mode: window full-screen
direct x: 11
motion blur: off
damage glow : off
effect: low
object detail: high
particles: low
post processing: low
shading: high
shadows: low
texturing: high
environment: high
anti-aliasing: postaa

[Alcom Isst]

IG 88, on 08 January 2015 - 04:23 AM, said:

r_HDRGrainAmount=0.0

You say that, but it's never made the film grain go away. MSAA makes the film grain go away.

Edit:

Navid A1, on 08 January 2015 - 04:14 AM, said:

It's the MSAA sadly.!

Turn it off... and forget about it. Run away from the "max out everything" syndrome.!

"I like the jaggies" <-- repeat every minute.

Alright! Alright, I'll retract my hyperbole and turn the jaggies and film grain back on. I can probably shove sweetfx back into this thing with the downgrade to dx9.

Edited by Alcom Isst, 08 January 2015 - 04:56 AM.

[Flapdrol]

Maybe you can override msaa in the nvidia control panel to only use 2x msaa, I reckon it's at 4x, 2x MSAA+MFAA might be possible too.

Could nuke the other settings, my gtx670 gets roughly 50 to 60 fps with msaa, with most of the rest on low.

Edited by Flapdrol, 08 January 2015 - 05:40 AM.

[xWiredx]

Are you not aware that you can force AA in the Nvidia control panel on a per-application basis? Turn the AA off in-game and turn it on for the MWO client in the driver. I've already tested it and the performance hit isn't as dramatic. I posted my user.cfg changes in my performance tests thread. Try that, too. And one more thing: you might want to crank that CPU up 100-300MhZ.

[Alcom Isst]

Flapdrol, on 08 January 2015 - 05:38 AM, said:

Maybe you can override msaa in the nvidia control panel.

xWiredx, on 08 January 2015 - 05:44 AM, said:

Are you not aware that you can force AA in the Nvidia control panel on a per-application basis? Turn the AA off in-game and turn it on for the MWO client in the driver. I've already tested it and the performance hit isn't as dramatic.

I am aware, and I'd love to!
But the option to override AA for MWO isn't offered for some reason. Neither is MFAA for MWO.



I can use the global setting apparently, but the global setting is 8x and doesn't work in MWO as expected.
Am I doing something wrong?

Edited by Alcom Isst, 08 January 2015 - 06:08 AM.

[MechWarrior4172571]

Flapdrol, on 08 January 2015 - 03:18 AM, said:

As you posted in an image from testing grounds it's probably the MSAA + high shaders and other fancy stuff that's killing performance.

In online matches with msaa off you're probably cpu limited.

Really? For GTX 970? The GPU usage in MWO for this GPU with everything graphical maxed out is less than 50%--no way it is MSAA related. The guy can check that to be the case by going all visuals to low and "off" but I bet it's not going to make a difference as far as MSAA is related. Maybe particles or something can make a difference because it's CPU related. You can set x16 anti-aliasing in nVidia panel with this card and it wouldn't make a difference on the performance in this regard because it's just an overkill of a card.

Alcom Isst, on 08 January 2015 - 06:07 AM, said:

I am aware, and I'd love to!
But the option to override AA for MWO isn't offered for some reason. Neither is MFAA for MWO.



I can use the global setting apparently, but the global setting is 8x and doesn't work in MWO as expected.
Am I doing something wrong?

What driver # are you using? Is it updated?

MFAA is blanked out for the MWO in the latest driver--that is confirmed.

Edited by Jesus DIED for me, 08 January 2015 - 06:58 AM.

[Alcom Isst]

Jesus DIED for me, on 08 January 2015 - 06:57 AM, said:

What driver # are you using? Is it updated?

MFAA is blanked out for the MWO in the latest driver--that is confirmed.

GeForce Game Ready Driver Version: 347.09. It's as updated as I can make it.

[xWiredx]

The global setting should be "override application setting" and then you don't have to force a specific AA on the global side. Save, and then you can go back into the MWO profile and select 8x for AA and transparency AA.

Or you can use something like the nvidia inspector program or whatever its called and set things in the profile that way. (my dog made sure I didnt sleep well, so... yeah).

[Lord Letto]

http://mwomercs.com/...s-explanations/

Quoted by Goose:

Quote

Off the top of my head;

• Textures are about RAM on your card; If you see a fps issue with textures, you need to set the user.cfg string for VRAM, and if it's stll a problem get a new card; Medium seems to take up about 800MB
  
• Post Processing at very high loses it's bang-for-buck: Leave it at meerly high
  
• Shading in MWO is called Quality in any other CryEngine game, and seems to speak striclty about GPU load, at about 10 percentage points a pop on a GTX 680: turning this down is how you upon up budget for effects like Ambant Occulation, which, IIRC, are in
  
• Environment in MWO is the combonation of Water, Volumictic Effects, and CryEngine Shading: This slider is one of the CPU Sesitve, but it's bang-for-buck is a point of debate (moves the CPU little, zero reduction in image quality/ immersion as you turn it down)
  
• Shadows pounds the CPU greatly: Never set higher then medium
  
• Paricals is Pure Evil to a CPU: never set higher then medium
  
• Object Detail eats RAM on the card, uses CPU cycles via an unspecified thread, and is really important to how the game looks, and thus is the setting you will work to keep higher

I'll fix this post somethime after I have a pot of coffee or so …





Look: Threads in Hardware where I post is pretty much what you are looking for; head to my profile, search for content there, and keep an eye out for the thread title.

in a nut shell, this is what i'd change to see if it makes a diffrence:
Particles: Drop from High to Medium
Shadows: Drop from Very High to Medium
Post Processing: Low to High

Try it out and let us know if it's better or worse

[Alcom Isst]

Lord Letto, on 08 January 2015 - 09:23 AM, said:

http://mwomercs.com/...s-explanations/

Quoted by Goose:


in a nut shell, this is what i'd change to see if it makes a diffrence:
Particles: Drop from High to Medium
Shadows: Drop from Very High to Medium
Post Processing: Low to High

Try it out and let us know if it's better or worse

With MWO's native MSAA on, I had to turn most things down to low to achieve 60fps everywhere in Forest Colony Snow Testing Grounds. Without MSAA, I was able to turn everything back up again and get 90-140fps.

Turning post-processing up or down had little effect.

xWiredx, on 08 January 2015 - 07:19 AM, said:

The global setting should be "override application setting" and then you don't have to force a specific AA on the global side. Save, and then you can go back into the MWO profile and select 8x for AA and transparency AA.

Or you can use something like the nvidia inspector program or whatever its called and set things in the profile that way. (my dog made sure I didnt sleep well, so... yeah).

Nvidia Control Panel continues to not cooperate.
Nvidia Inspector looks adorable. Lemme try it.

I did this:


Ended up with this as a result:


And yet the Inner Sphere is still made of pixel stairs and grain.

Edited by Alcom Isst, 08 January 2015 - 12:22 PM.

[MechWarrior4172571]

Alcom Isst, on 08 January 2015 - 12:10 PM, said:

With MWO's native MSAA on, I had to turn most things down to low to achieve 60fps everywhere in Forest Colony Snow Testing Grounds. Without MSAA, I was able to turn everything back up again and get 90-140fps.

And yet the Inner Sphere is still made of pixel stairs and grain.

Interesting @ your MSAA tests.

As far as lack of proper AA in MWO, I noticed that too, that no matter what settings in NVidia panel are that are set as, the jaggies are still there, so I can confirm your observation.

[Goose]

xWiredx, on 08 January 2015 - 07:19 AM, said:

Or you can use something like the nvidia inspector program or whatever its called and set things in the profile that way.

That's the one:

[Smokeyjedi]

Goose, on 08 January 2015 - 01:44 PM, said:

That's the one:

In comes Goose FTW

[Tarl Cabot]

Goose is using mwoclient.exe (game) whereas the others appear to be using mechwarrioronline.exe (patcher). Also make sure to use the correct mwoclient.exe in the correct folder (64bit vs 32bit engine). The handshaking between patcher and game may not be working correctly.

[Goose]

Annnnd Tarl wins the thread, for being the first to point out that little detail …

[Alcom Isst]

Goose, on 09 January 2015 - 11:03 AM, said:

Annnnd Tarl wins the thread, for being the first to point out that little detail …

I wish.

Tarl Cabot, on 09 January 2015 - 09:36 AM, said:

Goose is using mwoclient.exe (game) whereas the others appear to be using mechwarrioronline.exe (patcher). Also make sure to use the correct mwoclient.exe in the correct folder (64bit vs 32bit engine). The handshaking between patcher and game may not be working correctly.

The changes made through NVIDIA Inspector effect both mechwarrioronline.exe and mwoclient.exe. NVIDIA Control Panel and Inspector applies the same settings to mechwarrioronline.exe, mwoclient.exe (32bit), and mwoclient.exe (64bit).



I tried both 32 and 64 bit anyways. No AA for either.

Edited by Alcom Isst, 10 January 2015 - 01:15 AM.