47 replies to this topic

[DeathlyEyes]

http://mwomercs.com/...ost__p__3371858

Basically every other "core" in an fx processor is just an integer unit. It doesn't have an FPU unit which MWO heavily uses. Any FPU calculations executed on the second core likely take longer because they have to be resent to the first core to be handled. You can use task manager and set affinity to every other core, 0,2,4,6. Other issues have to deal with scaleform and I have been working on some tweaks to deal with that. This is what I managed to do to my user.cfg

Spoiler

gp_option_ShowCockpitGlass=0
r_DepthOfField=0
r_HDRGrainAmount=0
sys_flash_address_space = 536870912
gfx_ampserver = 1
gfx_loadtimethread =1
sys_flash_allow_reset_mesh_cache = 1
ca_KeepModels = 1
r_TexturesStreamingOnlyVideo =1
gfx_loadtimethread = 1
gfx_inputevents_triggerrepeat = .016
r_MultiThreaded = 1
sys_MaxFPS = 60

[Sorpin]

This thread is awesome! I got 10 more frames

[Kh0rn]

I noticed disabling the hud shift+f11 gained me a wopping 20 more frames they were right the hud is fps hungry.

[DeathlyEyes]

Kh0rn, on 17 May 2014 - 03:08 AM, said:

I noticed disabling the hud shift+f11 gained me a wopping 20 more frames they were right the hud is fps hungry.

Yes I can't tell if the hud issues are because actionscript calls are dependent on network i/o or if they are just just that cpu resource intensive. The hud is a flash layer on top of the game that depends on actionscript calls. So if the actionscript calls are waiting on getting heat values for instance from the server then then a frame won't be drawn. I suspect gfx_inputevents_triggerrepeat = .016 helps alleviate this by allowing the game to reuse old scaleform calls.

[Kh0rn]

thanks a bunch I will add this Iv just come too a conclusion that if this is the only game giving me issues in terms of FPS its not my machine its just this game. I hope further optimization will carry on in patches too come any way thanks for the help.

[Golrar]

Thanks for the info SLDF, fixed my fps drops in Frozen City day with the fog. Now I never drop below 50 fps.

[Goose]

SLDF DeathlyEyes, on 17 May 2014 - 06:31 AM, said:

I can't tell if the hud issues are because actionscript calls are dependent on network i/o or if they are just just that cpu resource intensive. The hud is a flash layer on top of the game that depends on actionscript calls. So if the actionscript calls are waiting on getting heat values for instance from the server then then a frame won't be drawn. I suspect gfx_inputevents_triggerrepeat = .016 helps alleviate this by allowing the game to reuse old scaleform calls.

… Shift-F11 changes my unlimited fps by ~3, with- or without this set of strings, and can't tell which CPU core has a load change, ether …

[Bullseye69]

[color=#959595]When things are moving and shooting back at you, the game gets badly bottlenecked by GHz on the last CPU core, where "ca_thread0Affinity" and "r_WaterUpdateThread" both reside.[/color]

[color=#959595]This is [/color]bad[color=#959595], as the game seems to rely on thread0 and not use thread1 much, so having waterupdate on the same core gums up the works.[/color]

So if us the reason why don't they recode so the waterupdate uses the different thread.
Just wondering will give the new config file a try next time I on.


Runnning a old athlon 2 640 3.1ghz quad it exactly 300 mhz off the recommend speed for there recommend amd s[ecs game run like crap and it really pissing me off . Could us any boost i can get.

Thanks Goose.