179 replies to this topic

[Nightbird]

McGoat, on 11 June 2019 - 08:21 AM, said:

Just tried, no change.


Edit: Tested in live and it is good to go. Thanks vaad!

Are you sure? I tested the cfg with that setting, 3 RAC2s on river city (testing grounds) shooting across the water to the mountains, and some shells are exploding prematurely.

On the other hand, I used my existing config and added these 3 settings, 0 problems. Gonna add settings until I hit this problem.
e_ParticlesQuality=2
e_ParticlesLod = 0.75
e_ParticlesObjectCollisions=1


edit....
I was able to add everything except the Threads sections, so that section is causing the glitch.

Edited by Nightbird, 11 June 2019 - 07:05 PM.

[dario03]

Are there any settings specifically for Faction Play? With all this on the lower settings from the first post, and a couple of other things turned down I have it running pretty good in QP, a lot less pausing and only a bit of stuttering. But in FP I get a lot of stuttering for most of the match and some pausing still.

[Corbon Zackery]

You can spend hours messing with config. files if you want, or you can use these settings.

High-end i5 processor/ AMD 2gb to 8gb graphics card.
12 GB Ram
Samsung SSD drive

Effects: High
Object Details: High
Particles: Medium
Shading: Low
Shadows: Low
Texturing: High
Environment: High
Anti-Aliasing: Off

This will produce a 68 to 75 FPS with about a 40 to 55 ping. Looks nice and smooth with some tear you never notice because your shooting giant robots.

[Nesutizale]

While that is true there is still some room for improvement it seams. Something PGI should have done some time ago. I welcome MrVaads progress with the config files and hope he will improve it further.

[MrVaad]

Corbon Zackery, on 12 June 2019 - 06:27 AM, said:

You can spend hours messing with config. files if you want, or you can use these settings.

I know that many people won't use config files. That's why I have put a small guide explaining what the game settings do (if they just want to change ingame options).

Do you really think that kind of post help people ? After all these years, i think they would have found the good ingame settings (and you made quite a few errors)

Edited by MrVaad, 12 June 2019 - 04:18 PM.

[McGoat]

Nightbird, on 11 June 2019 - 06:23 PM, said:

Are you sure? I tested the cfg with that setting, 3 RAC2s on river city (testing grounds) shooting across the water to the mountains, and some shells are exploding prematurely.

On the other hand, I used my existing config and added these 3 settings, 0 problems. Gonna add settings until I hit this problem.
e_ParticlesQuality=2
e_ParticlesLod = 0.75
e_ParticlesObjectCollisions=1


edit....
I was able to add everything except the Threads sections, so that section is causing the glitch.

Testing grounds still showed the exploding rounds, live does not. Does this mean that the settings are not carried over? I don't know. I know there has historically been disparity between what happens in testing and live. I do know that the game loads faster :| haha.

[Nightbird]

McGoat, on 12 June 2019 - 08:16 AM, said:

Testing grounds still showed the exploding rounds, live does not. Does this mean that the settings are not carried over? I don't know. I know there has historically been disparity between what happens in testing and live. I do know that the game loads faster :| haha.

You can try in private lobby, hit me up if you need someone (ts)

[McGoat]

Nightbird, on 12 June 2019 - 08:18 AM, said:

You can try in private lobby, hit me up if you need someone (ts)

Yeap, that's what we did.

However, I had massive frame drops on Frozen City with it. Being as that is the only thing that has changed in my setup I can't imagine it being anything else.

[dario03]

Corbon Zackery, on 12 June 2019 - 06:27 AM, said:

You can spend hours messing with config. files if you want, or you can use these settings.

High-end i5 processor/ AMD 2gb to 8gb graphics card.
12 GB Ram
Samsung SSD drive

Effects: High
Object Details: High
Particles: Medium
Shading: Low
Shadows: Low
Texturing: High
Environment: High
Anti-Aliasing: Off

This will produce a 68 to 75 FPS with about a 40 to 55 ping. Looks nice and smooth with some tear you never notice because your shooting giant robots.

I have all that stuff or better, with lower settings, still get slowdowns. Config file helped, and gives more options than just the ingame menu.

[Nightbird]

McGoat, on 12 June 2019 - 08:24 AM, said:

Yeap, that's what we did.

However, I had massive frame drops on Frozen City with it. Being as that is the only thing that has changed in my setup I can't imagine it being anything else.

Last thing is, you're using the threading section of the cfg?

Could be AMD versus Intel difference then... still, a bit strange

[McGoat]

Nightbird, on 12 June 2019 - 08:34 AM, said:

Last thing is, you're using the threading section of the cfg?

Could be AMD versus Intel difference then... still, a bit strange

I changed nothing but what was suggested by vlaad, so yeap!

I've never had a problem with that before and it'd have to be some strange referencing for it to happen in my intel chip vs an amd, but stranger things have happened.

[MrVaad]

Ok i have the bug with a 6 AC2 king crab !

The solution for now:

• Set e_ParticlesLod=1 (not 100% sure about this one)
  
• Lower p_num_threads to 3/2/1

p_num_threads is the number of additonal threads for physics.
The bug concerns bullets collisions with the terrain.

Edited by MrVaad, 12 June 2019 - 03:10 PM.

[Nightbird]

MrVaad, on 12 June 2019 - 01:53 PM, said:

Ok i have the bug with a 6 AC2 king crab !

The solution for now:

• Set e_ParticlesLod=1(not 100% sure about this one)
  
• Lower p_num_threads to 3/2/1

p_num_threads is the number of additonal threads for physics.
This is really strange, the bug is about bullets collisions with the terrain.

I didn't need to change e_particleslod, does this give a performance boost?

[MrVaad]

At 0.75, It should help performance, but in MWO, i can't see the impact on my system.

It reduces the number of particles per emitter (it's a multiplier).
But as one of MWO's problem is using many particle emitters with 1 particle each ...

Edited by MrVaad, 12 June 2019 - 03:07 PM.

[Nightbird]

Wait, after playing a few matches, this config is for increase visuals isn't it? lol. Not for increasing FPS

[MrVaad]

Nightbird, on 12 June 2019 - 06:33 PM, said:

Wait, after playing a few matches, this config is for increase visuals isn't it? lol. Not for increasing FPS

It's for increasing/fixing visuals and improving fps (when it doesn't lower the visuals)
I try to go not too far on the graphics. That's why i put instructions to people looking for better fps or better graphics.

On the particleLod, I though i had removed this line, it was an experiment and doesn't seem to do much.

Particles are probably the worst performance problem of MWO.
You can't see the full impact in CPU or GPU usage. And the ingame settings only remove effects (even on low, there's still some problematic effects).

Edited by MrVaad, 13 June 2019 - 01:03 AM.

[Nightbird]

I did have a problem with the particles in this config, the smoke from FP generators was just billowing out and covered a lot more of the map. Since you can't see through it with any of the view modes, I had to change it back.

[MrVaad]

Nightbird, on 13 June 2019 - 05:11 AM, said:

I did have a problem with the particles in this config, the smoke from FP generators was just billowing out and covered a lot more of the map. Since you can't see through it with any of the view modes, I had to change it back.

Must be e_ParticlesObjectCollisions=1
1 is collisions with static objects, 2 is collisions with static and dynamic objects

I think i'll put it back to 2 (MWO default) for everyone.

Edited by MrVaad, 13 June 2019 - 01:59 PM.

[McGoat]

MrVaad, on 12 June 2019 - 01:53 PM, said:

Ok i have the bug with a 6 AC2 king crab !

The solution for now:

• Set e_ParticlesLod=1 (not 100% sure about this one)
  
• Lower p_num_threads to 3/2/1

p_num_threads is the number of additonal threads for physics.
The bug concerns bullets collisions with the terrain.

What do you mean by this? Do you input exactly 3/2/1 so the line commands
p_num_threads=3/2/1? :|

[Nightbird]

3 or 2 or 1

Any suggestions on settings to further reduce particle effects? Once mechs start smoking late match, my fps really tanks by half or more.