27 replies to this topic

[Meep Meep]

With some free time on my hands I decided to dig up my config project and rebuild it from the ground up using the cryengine documents to figure out what would be relevant to use. After a few days of edits and client reboots to test all the permutations and performance curves I came up with this.


;----- Maximum Pretties. All Game Settings To Very High For Ultra+ -----
;----- Performance Pretties. All Game Settings To Low With Textures To Very High For Ultra Performance -----
;----- Pure Performance. All Game Settings To Low With N64 Mode Enabled -----
;----- Mix n Match Pretties. Experiment With Different Settings To Find Your Preferred Level Of Performance Vs Visual Bling -----


r_Batching=1
r_BatchType=2
r_GeomInstancing=1
r_GeomInstancingThreshold=2
e_GI=1
e_ParticlesGI=1
e_Lods=0
e_TerrainLodRatio=0.5
e_TerrainTextureLodRatio=1
r_HDRBrightlevel=1.2
r_HDRBloomRatio=1.5
e_ViewDistMin=4096
r_DetailDistance=4096
e_ParticlesLightsViewDistRatio=1024
r_TexMaxAnisotropy=16
r_TexMinAnisotropy=16
r_Texture_Anisotropic_Level=16
r_TexAtlasSize=2048
r_Supersample=3
e_ParticlesForceSoftParticles=1
e_DynamicLightsMaxCount=256
e_ParticlesMaxScreenFill=1024
r_ColorGrading=1
r_ChromaticAberration=1


;----- Optional Pretties(SSAO is a performance hog) -----
r_DepthOfField=0
r_MotionBlur=0
r_SSAO=0

;----- Shadow quality range is 0=off 4=very high -----
e_Shadows=4
e_ShadowsMaxTexRes=2048
;e_ShadowsCastViewDistRatio=0.5


;----- Particle quality range is 1=low 4=very high -----
e_ParticlesQuality=4

;----- Removes particles larger than X%(0.1 is 10%) so cockpit hits don't blind you. Set to 0.001 to effectively remove all particles. -----
;e_ParticlesMaxDrawScreen=0.3

;----- Disable Automatic Targeting -----
gp_mech_disable_autotarget=1

;----- Smooths Mouse Actions In Mechlab -----
gfx_inputevents_mouse_move_threshold=0.0166
sys_flash_curve_tess_error = 2
sys_flash_newstencilclear = 0

;----- FPS Marker -----
;gp_mech_showfps=1

;----- Cockpit Light -----
;gp_default_cockpit_light=0

;----- Remove Vegetation -----
;e_VegetationMinSize=200000

;----- N64 Mode Off -------- remove or add semicolon to enable or disable each section
e_TerrainDetailMaterialsViewDistXY=4096
e_TerrainDetailMaterialsViewDistZ=4096

;----- N64 Mode On ---------
;e_TerrainDetailMaterialsViewDistXY=0.01
;e_TerrainDetailMaterialsViewDistZ=0.01
;r_TexturesStreaming=1
;r_TexturesStreamPoolSize=0.001

;----- Mouse Sensitivity ------
;cl_sensitivity=0.09
;i_mouse_accel=0
;i_mouse_accel_max=0



Now there should be virtually no texture or geometry pop in and it still gives a general performance boost. Particles, lighting and general effects have been increased in both intensity and view distance.

The easiest way to compare the images is to open each in a new tab then switch between them.

Luthien Very High Settings.

Spoiler

Luthien Very High Settings With Config.

Spoiler

Canyon Network Very High Settings.

Spoiler

Canyon Network Very High Settings With Config.

Spoiler

Edited by Meep Meep, 27 January 2025 - 11:50 PM.

[Meep Meep]

Guess there is an image limit..

Alpine Peaks Very High Settings.

Spoiler

Alpine Peaks Very High Settings With Config.

Spoiler

[Saved By The Bell]

I tried HTM-27W with uacs and acs. The flashing near cockpit was terrible. I had to switch to ac20 or lbx10. Is your config unable to deal with it? Config noob here.

Edited by Saved By The Bell, 24 January 2025 - 10:52 PM.

[Meep Meep]

Saved By The Bell, on 24 January 2025 - 10:52 PM, said:

I tried HTM-27W with uacs and acs. The flashing near cockpit was terrible. I had to switch to ac20 or lbx10. Is your config unable to deal with it? Config noob here.

Dynamic hdr light flashing or particle flashing from the muzzle flash smoke?

If the former then you can put a ; in front of these two lines to dial it back a bit or lower the ratio with 1.0 being the default. The higher over 1.0 the more intense and less intense under 1.0.

r_HDRBrightlevel=1.2
r_HDRBloomRatio=1.5


If the latter then take the ; off of this line.

e_ParticlesMaxDrawScreen=0.3

I've commented out the 'controversial' stuff by default but you only have to remove the ; to enable it.

If you want to know what the various lines do then copy them and add it after 'cryengine 3 cvar' in a search. Brave AI typically returns a good summary.


I should also mention you have to load any test map twice before your first drop of a given session to fully load the config. You only have to do this after starting up the client or if you change something in the settings screen and save.

Edited by Meep Meep, 24 January 2025 - 11:44 PM.

[TELEFORCE]

Thanks for sharing this. I can't tell the difference between the comparison images

[Duke Falcon]

What is "N64 mode" exactly?
Automatic targeting means to get paperdoll if point\target a mech with the reticule?

Quote

I should also mention you have to load any test map twice before your first drop of a given session to fully load the config. You only have to do this after starting up the client or if you change something in the settings screen and save

Is that necessary? I mean if I use your config settings and just drop into FP it won't work?

[Meep Meep]

TELEFORCE, on 25 January 2025 - 05:27 AM, said:

Thanks for sharing this. I can't tell the difference between the comparison images

Open each one in their own tab then flip between them.

Duke Falcon, on 25 January 2025 - 07:51 AM, said:

What is "N64 mode" exactly?
Automatic targeting means to get paperdoll if point\target a mech with the reticule?

N64 mode is where texture resolution is dropped to basically 8 bit levels and it can greatly help with performance on lower end systems.

Automatic targeting is exactly that. If you point at a mech and fire its automatically targeted.

Turning it off allows the use of the target system to track a high priority target almost like gps since anytime they get spotted it pops up on your compass. Funnily I've been accused of hax over this in game a few times. "How do you know where I am all the time??"

Quote

Is that necessary? I mean if I use your config settings and just drop into FP it won't work?

Yes. Its a quirk of using a config in the game. You only have to do it after you first boot up the client for a game session. Once you load a test map twice you are good to go till you exit the client again.

Edited by Meep Meep, 25 January 2025 - 09:22 AM.

[Duke Falcon]

Quote

Yes. Its a quirk of using a config in the game. You only have to do it after you first boot up the client for a game session. Once you load a test map twice you are good to go till you exit the client again.

Ouch...
For some reason testing grounds loads slooooow like a stunned slug...

Hmmm...

Could you write me a config what take the most of the game? The most beautyfull sight the CryEngine under MWO could provide?

[Saved By The Bell]

All maps and testing loading slow after patch, its not config.

[Saved By The Bell]

I was trying before to mode cfg and wasnt able to do it.

I cant found user.cfg anywhere on my PC.

And if I try to install, I get this:

https://ibb.co/YbyHx3X

Edited by Saved By The Bell, 26 January 2025 - 01:49 AM.

[Drenzul]

Saved By The Bell, on 26 January 2025 - 01:49 AM, said:

I was trying before to mode cfg and wasnt able to do it.

I cant found user.cfg anywhere on my PC.

And if I try to install, I get this:

https://ibb.co/YbyHx3X

Your MWO settings are in a admin only folder. Rightclick on MWO config and select 'run as admin'

[Saved By The Bell]

Thanks, Drenzul!

[Saved By The Bell]

In my case, training grounds run much faster with new config, I ll check tomorrow in games.

So about flashing:

Meep Meep, on 24 January 2025 - 11:39 PM, said:

Dynamic hdr light flashing or particle flashing from the muzzle flash smoke?

If the former then you can put a ; in front of these two lines to dial it back a bit or lower the ratio with 1.0 being the default. The higher over 1.0 the more intense and less intense under 1.0.

r_HDRBrightlevel=1.2
r_HDRBloomRatio=1.5


If the latter then take the ; off of this line.

e_ParticlesMaxDrawScreen=0.3

I've commented out the 'controversial' stuff by default but you only have to remove the ; to enable it.

If you want to know what the various lines do then copy them and add it after 'cryengine 3 cvar' in a search. Brave AI typically returns a good summary.


I should also mention you have to load any test map twice before your first drop of a given session to fully load the config. You only have to do this after starting up the client or if you change something in the settings screen and save.

I can add these lines in config file by myself? Didn`t see this parameters in MWO config.

Edited by Saved By The Bell, 26 January 2025 - 11:25 AM.

[Meep Meep]

Saved By The Bell, on 26 January 2025 - 12:10 AM, said:

All maps and testing loading slow after patch, its not config.

Game ran like dogcrap after the patch for me too so I ran the mwo repair tool. Fixed it for me.

Duke Falcon, on 26 January 2025 - 12:08 AM, said:

Could you write me a config what take the most of the game? The most beautyfull sight the CryEngine under MWO could provide?

Saved By The Bell, on 26 January 2025 - 11:25 AM, said:

In my case, training grounds run much faster with new config, I ll check tomorrow in games.

So about flashing:



I can add these lines in config file by myself? Didn`t see this parameters in MWO config.

Don't use the config tool it doesn't have the variables I have in my config. The config I listed is stand alone and should be copy pasted into a clean user.cfg file as is. You can comment ( ; ) settings on or off or change the values yourself.

Ok lets start from scratch then. Run the mwo repair tool to ensure you have a blank slate and the shader cache is wiped.

Then drop these two files into the mechwarrior online base directory.(extract after downloading)

https://limewire.com...ugIdodjzPqezBWQ

Start the client and set everything to very high with your choice of AA. After making any other changes you want in the settings and saving restart the client to ensure everything was loaded correctly. Sorry but mwo is finicky with very high settings not taking full effect till you restart.

Once back in the game immediately load any test map twice and you are done for the entire session. You will only have to load the test maps twice again if you change anything in settings and save or exit and restart the client.

Due to the shader cache getting wiped you will experience a bit of stutter when running around maps for the first time as the game rebuilds them but its only at the very start.

Edited by Meep Meep, 26 January 2025 - 01:45 PM.

[Drenzul]

Just FYI - There might have a conflicting setting somewhere.

I tried the copy/paste method, I'm a software dev so pretty sure I did it right
I made sure to only add new settings and update the existing settings, so no config item was repeated.

Game loaded fine but loads of terrain features were flickering constantly.

Using the file you uploaded instead worked absolutely fine.

[Meep Meep]

Weird cause the post with the config is exactly the same as what's in the file.

I've have had the flashing vegetation before and deleting the shader cache fixed it.

[Drenzul]

Meep Meep, on 26 January 2025 - 10:10 PM, said:

Weird cause the post with the config is exactly the same as what's in the file.

I've have had the flashing vegetation before and deleting the shader cache fixed it.

I did it the changes on top of my existing file. Hence I think one of your settings might cause an issue
with some possible settings on a config file built my MWConfig for example. If your config doesn't
have the conflicting setting it, it probably wouldn't emerge the issue.

Wasn't just the vegetation flashing, was basically all the scenery on all maps. Clearing shader cache didn't help.

[Meep Meep]

Oh I see. Yeah this is meant to be a stand alone config and not merged with an existing one. Can you post your config so I can take a look? There might be some settings you prefer that can be safely merged.

[Drenzul]

I only saved the pre-merge one I'm afraid. Overwrote it with your fresh config when it didn't work.
Its just a standard one made with MWConfig with all settings at highest.

Looked like it was trying to render the same thing two different ways. Looks much better with your config

[Meep Meep]

Cool. Glad you enjoy it.