29 replies to this topic

[Mawai]

No One Lives Forever, on 20 July 2016 - 09:28 AM, said:

This is not about performance for the most part..but my CPU is i7 2600k@4.5 Ghz. Thought about upgrading, but i don't see much point in it, most newer CPU's aren't that much faster.

The thing is that MWO is usually more CPU bound that GPU bound. That is why your 980 isn't showing huge performance gains over the previous cards. MWO has some heavy multi-thread CPU usage which works best when each thread has their own CPU. Sometimes Intel hyperthreading or AMDs module usage on FX cores can cause performance issues when two of the MWO threads end up running on one module or one physical core each of which represents two virtual processors.

Sometimes MWO performance can be improved by turning off hyperthreading for Intel CPUs or by forcing processes to one/module on AMD FX processors.

[Tarl Cabot]

No One Lives Forever, on 21 July 2016 - 01:18 AM, said:

I've got everything on max with MSAA, DX11, x64, VSync ON. Game is running at 60 FPS most of the time, but sometimes it dips to about 40 FPS, especially on new Viridian Bog. I guess, I'll have to tone some settings down..

As noted, I am not using any Anti-aliasing settings, it is off. Do you have Vsync on or off?

Doh...never mind, Vsync is enabled, so that is capping your FPS to 60. I found it better to put a FPS cap in the user.cfg file (or use the GPU control panel) than to have Vsync enabled.

Edited by Tarl Cabot, 23 July 2016 - 07:55 AM.

[No One Lives Forever]

Tarl Cabot, on 23 July 2016 - 07:52 AM, said:

As noted, I am not using any Anti-aliasing settings, it is off. Do you have Vsync on or off?

Doh...never mind, Vsync is enabled, so that is capping your FPS to 60. I found it better to put a FPS cap in the user.cfg file (or use the GPU control panel) than to have Vsync enabled.

Thanks, i'll try capping FPS to 60.

[Tarl Cabot]

No One Lives Forever, on 23 July 2016 - 07:59 AM, said:

Thanks, i'll try capping FPS to 60.

Turn off Vsync and run a few games first to see what your high/low are, then create and put a user.cfg in your MWO folder, the following line below in it, or create a profile in your GPU control panel to keep the FPS cap to just this game.

sys_MaxFPS = 75

You can try a higher mark than 60 then go from there.

Edited by Tarl Cabot, 23 July 2016 - 08:07 AM.

[No One Lives Forever]

Tarl Cabot, on 23 July 2016 - 08:07 AM, said:

Turn off Vsync and run a few games first to see what your high/low are, then create and put a user.cfg in your MWO folder, the following line below in it, or create a profile in your GPU control panel to keep the FPS cap to just this game.

sys_MaxFPS = 75

You can try a higher mark than 60 then go from there.

Well, i ran few testing ground tests. With VSync OFF and MSAA it runs ~ 65-75 FPS with some dips sometimes to 40 FPS.
With VSync OFF and FXAA it runs ~ 150-170 FPS, but looks a bit worse. Maybe i should stick with FXAA then?

But with VSync OFF i get some micro-stuttering. I guess then it's FPS cap at 60 or VSync ON, because monitor refresh rate is 60.

Edited by No One Lives Forever, 23 July 2016 - 08:58 AM.

[Peter2k]

Karl Berg, on 12 June 2014 - 09:18 PM, said:

Hey Imperius!

...

The draw calls made into D3D are very CPU intensive. A good chunk of that is due to the lego-like nature of the mechs; being formed out of dozens of individual components rather than a single character that can be rendered with a single draw call, like in most other games. It's also compounded by the particle system, the terrain system, and the older Scaleform 3 integrated into the engine...

Because of this, you're definitely going to want a very strong CPU...
Because we're so CPU limited...

Lots of draw calls
Slowing down in dx11/9

New API's like vulcan and dx12 could help with that
So new engine could help a lot in performance

But
DX12 and vulcan shift a lot more coding work onto the developer
For instance under dx12 a dev can mix AMD and Nvidia for dual graphics cards
But the dev has to develop for that

From PGI's history I can't see any way that would work well, except if they hire a lot more coding people

[jaxjace]

Ive been here almost 5 years now, dont expect much.

[No One Lives Forever]

Peter2k, on 23 July 2016 - 09:43 AM, said:

Lots of draw calls
Slowing down in dx11/9

New API's like vulcan and dx12 could help with that
So new engine could help a lot in performance

But
DX12 and vulcan shift a lot more coding work onto the developer
For instance under dx12 a dev can mix AMD and Nvidia for dual graphics cards
But the dev has to develop for that

From PGI's history I can't see any way that would work well, except if they hire a lot more coding people

Thanks for the insight. I dont see that happening either, tbh, one can only hope.
On the other hand, maybe its time for me to upgrade CPU.

Edited by No One Lives Forever, 23 July 2016 - 10:09 AM.

[Imperius]

Future of the game is "Your feedback is not needed! We know what we are doing! If you could do it better than do it!" And then insert <Would you like to buy a mech pack song> sadly even if one of your top supporters asked for a MechPack you could deliver you decided pride or OCD was more important than keeping that customer happy from a small request.

These forums are getting sad... Would you like to buy a mech pack should have been posted first page....

[S 0 L E N Y A]

Future is very grim.
PGI has a strong track record of both ignoring the community and making poor decisions.

The fact that as of late PGI is attempting to become more responsive to the community is unfortunately disturbing. It signifies that the game is in poor shape (player population is taking a swan dive) and that PGI is in emergency "oh s#!+ mode.