9 replies to this topic

[Exilyth]

Hi.

There used to be a large thread about this, but I cannot find it anymore.

Does anyone know what graphics options can be tweaked via the user.ini to squeeze out a few more FPS?

I'd be especially interested in turning off water reflections.

[Tarl Cabot]

One thread a player and Narcbait was working things out.

https://mwomercs.com...rrain-textures/

[NARC BAIT]

this is probably the thread your meaning, https://mwomercs.com...urrent-usercfg/ ... but, there really is no one size fits all .... more is completely relevant to what you currently get, which you didnt happen to mention ....

[Exilyth]

Especially the fully commented example user.ini is very helpfull.

Thank you.


I'll play around with values and see If I can squeeze out a few more frames.

[Napoleon_Blownapart]

these are old user.cfg posts
https://mwomercs.com...sys-spec-files/
https://mwomercs.com...-usercfg-guide/

[Exilyth]

NARC BAIT, on 29 March 2018 - 09:11 PM, said:

this is probably the thread your meaning, https://mwomercs.com...urrent-usercfg/ ... but, there really is no one size fits all .... more is completely relevant to what you currently get, which you didnt happen to mention ....

Using the config out of that thread is already giving me better FPS and better graphics (was using low settings before).

What do the gp_hud_[category]_update vars do?

Anyway - I'm sitting at 15-20 FPS most of the time, dipping lower when there's heavy fighting. With the config, I'm getting around 20-25.

OS Version: Microsoft Windows 7 Home Premium
System RAM: 8178 MB
CPU Name: AMD A6-3600 APU with Radeon™ HD Graphics
CPU Speeds: 2100
Physical CPUs: 1
Virtual CPUs: 4
Video Card Description: AMD Radeon HD 6450
VRAM: 1024 MB
Primary Display Resolution: 1680x1050

Quote

gp_mech_disable_autotarget = 1 -- 1) do not auto target mech under crosshair

This is usefull for any ECM/stealth equipped scout.
Damn, doesn't seem to stick.

Edited by Exilyth, 31 March 2018 - 03:58 PM.

[NARC BAIT]

Exilyth, on 31 March 2018 - 01:56 PM, said:

Damn, doesn't seem to stick.

it should, I rely on it daily, quite often I leave one guy targeted until the rain stops, and shoot someone else, on more recent iterations I ended up putting comments to their own line, because there was a few places that didnt do so weil with them being on the same line, probably especially if the 'tabs' end up being copied as 'spaces' ...

the lines that start with gp_hud affect how often the flash HUD elements for those systems are updated ... they work as a frame counter, as in, wait X frames until update X, they do not stop how often the unseen system does updates though, so their effectiveness is small overall ... the system that does the map, might update with 'not so new' information a few hundred times a second, depending on how many players are in your field of view, but only 'draw' an update every third frame ... by which time, hundreds of bits of information have changed, and it gets jumpy .... even if you go into third person view, where it doesnt update the map, it still gives the penalty ...

[Exilyth]

I see - will put comments on different lines and see if I can get it to stick then.

Thank you.


Edit:
In notepad++, replaced "(space)--" with "\n--" on the file below the 'header', then edit -> blank operations -> remove trailing spaces.

Now testing...
Meh, I can get more values to stick now, but disable autotargetting is not one of them.
Also < 10 FPS on Grim Plexus. Fine on all other maps.

Tweaked some more, back to 10-15 FPS on Grim now, fine on all others.

Edited by Exilyth, 01 April 2018 - 03:30 PM.

[NARC BAIT]

Exilyth, on 01 April 2018 - 09:49 AM, said:

In notepad++, replaced "(space)--" with "\n--" on the file below the 'header', then edit -> blank operations -> remove trailing spaces.

ummm .... open the file with normal notepad, and see what it looks like ... you may have needed to replace "(space)--" with "\r\n--"

[Exilyth]

Notepad++ normalizes line endings automatically afaik - went and converted all line endings back and forth to be sure.
Now testing again.

Got one, two more FPS now, no more problems on Grim.

When I target one mech and shoot another, the first one stays targeted.
But when I don't have a target locked and shoot a mech, I'm still autotargeting the mech I'm firing at.

Edit:
Which values stick seems to also depend on what map was used to load into testing grounds at the start.

Edited by Exilyth, 04 April 2018 - 02:25 PM.