9 replies to this topic

[Nikguy]

OK guys,

I know I'm setting myself up for a response such as "try searching the forums before starting a thread!" But believe me I have, and tried most of the fixes. I'm starting this topic more as an area to discuss the reason for the Framerate drops that I, and others have been getting frustrated with for a couple (?) Years now.

My system is as follows:

Intel I5 4690k oc to 4.6ghz
Nvidia GTX 1070 founders edition stock clock (8gb vram)
24 GB ddr3 ram at 1600
850w EVGA power supply
Solid-state drive

My question is: why does my fps drop below 25 Everytime someone fires lrms or Everytime a drop ship sets my mech down? Am I the only one?

Trued with v-sync on, off, adaptive, and "fast". And various other fixes. Is the game just that poorly optimized? Or am I missing some fundamental thing?
Thanks everyone for the responses!

[Omaha]

What are your ingame settings?

Try maybe changing, effects, and particles, to a lower setting.

For myself with a way under powered rig. I've noticed that missles have some crazy smoke trails, and other crazy effects that really hurt me, in FPS. Even with everything turned down. I noticed crazy drops in performance when ppl use lrms.

So I guess you can say LRMS, are also a different kind of weapon, In this re guard. beside just being a long range missle. It's like a DDOS at the cpu/gpu. If you aint got the the right equipment.

Srms also have the same type of thing happening. But due to the nature of the short lived range it's not as noticable until u see them em mass firing.

Oh almost forgot have you tried changing texture filter quality under nvidia control panel advance 3d settings?

Edited by Omaha, 05 January 2017 - 12:45 PM.

[General Solo]

particles are a FPS killer

turn it down some and test again

Dropship and lerms use particles

[Nikguy]

Particles huh? So I'm guessing that the engine/game decides to offload that work to the CPU instead of the GPU?. I'll give it a shot after work and let anyone who is following this thread know how it goes.

[Natred]

I'm curious how sounds are implemented if that has any effect on overall average fps.

[Barkem Squirrel]

Same thing here. Those drop ships are fps hogs. The only way i noticed was watching them leave on polar highlands and puff, better frame rates and not warping around in various directions.

[Michal R]

Read this and use:
http://mwomercs.com/...2-force-32-bit/
http://mwomercs.com/...14#entry5423114

And for stability my FPS this is good:
https://reshade.me/

It's legall for MWO. And game looks better.

[Mainhunter]

I have only probs with the new maps. Just played Forrest and dropped in some occasions down to 35 FPS, no one was shooting. I run a similar Rig with a 2500k @4.4 and a oc 1070.

I witnessed this in other multi player games when you look in the direction of the majority of enemy's, even if you cant see them. That's likely a CPU thing, but please, with only 12 opponents on the map, that's a bit weak.

And how unprofessional is it to have different demanding maps in a cycle? Do they think people will switch their graphic settings between maps?

[Nikguy]

My thoughts exactly!

[Statik]

Michal R, on 06 January 2017 - 02:23 PM, said:

Read this and use:
http://mwomercs.com/...2-force-32-bit/
http://mwomercs.com/...14#entry5423114

And for stability my FPS this is good:
https://reshade.me/

It's legall for MWO. And game looks better.

Hey Michal, need your help. I tried using the reshader that you suggested and I must have done something wrong. MWO won't load properly now. When downloading the reshader I selected MWOClient.exe in the 32bit folder (I assumed this was correct since that was the .exe I was using) Selected Direct 10+ and it installed all the reshader folder (I left everything selected to install) Loaded up the game, Shift-F2 to load the shader program, and followed the instructions. Saved and tried logging in, but the game now just goes to a Black Screen with my MWO cursor and that's it. Any idea how I can undo this to I can play? I tried deleting the re-shader folder in the 32 bit folder but that didn't work.

EDIT: Nevermind, ran the repair tool and it fixed the shaders back to default. Good to go.

Edited by Statik, 19 January 2017 - 06:16 PM.