21 replies to this topic

[Ilostmycactus]

It is absolutely miserable to use a ballistic mech with guns next to your cockpit. It is not good design to force the player to use heat vision just so they can see what they're shooting at because it changes the game contrast. Not to mention it's actually somewhat painful to constantly flash bright lights over and over.

These are far future, advanced machines. They should have polarized cockpit glass or whatever excuse you want to give. Punishing the player for even firing a weapon is insane. This isn't recoil or bloom or spread or ammo or leading the target. It's clicking the button period. You can't "work around it" or something with skill if you're using a rapid fire, multi uac setup, etc. It just happens.

If you want to keep enemy mechs blinding the opposing team, then fine. But please change this.

Edited by Ilostmycactus, 10 April 2024 - 12:17 AM.

[Meep Meep]

Create a user config and add only this line.

;----- 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.1

Experiment to get the level of reduction you want. But the above value works well to eliminate cockpit particle spam but still leave everything else.

[kalashnikity]

Here is the entire text of what I use, this made an increadable difference in both performance and video quality, thanks meep meep. I will try lowering that value, I ahve mine at 0.1 right now, and muzzle flash is not overly distracting, but i don't run RAC often.

I use notepad to create it, save it as "user.cfg" and place it in your "Mechwarrior Online" folder, other files located there will be "system.cfg" and tuning.cfg" (and some other stuff) so you know you have the right folder.

e_Dissolve=1
e_LodCompMaxSize=255
e_LodRatio=255
e_ObjQuality=4
e_ParticlesMaxDrawScreen = 0.1
e_ParticlesQuality=1
e_ParticlesObjectCollisions=1
e_ParticlesPreload=1
e_PreloadDecals=1
e_PreloadMaterials=1
e_StatObjPreload=1
e_TerrainLodRatio=0.5
e_TerrainTextureLodRatio=5
e_TerrainDetailMaterialsViewDistXY = 4096
e_TerrainDetailMaterialsViewDistZ = 4096
e_ViewDistMin=4096
gfx_inputevents_mouse_move_threshold=0.0166
gp_default_cockpit_light=1
i_mouse_smooth=1
r_BatchType=0
r_DepthOfField=0
r_GeomInstancingThreshold=2
r_SSAO=0
r_ShadersAsyncCompiling=3
r_ShadersAsyncMaxThreads=4
r_ShadersCompileAutoActivate=1
r_ShadersPreactivate=1
r_ShadersUseInstanceLookUpTable=1
r_SnowHalfRes=1
r_TexMaxAnisotropy=16
r_TexMinAnisotropy=16
r_Texture_Anisotropic_Level=16
r_TexturesWarmup=1
r_WaterCaustics=0
r_WaterReflectionsQuality=0
r_WaterTessellationHW=0
r_ssdo=0
r_sunshafts=0
sys_flash_curve_tess_error=10
sys_flash_edgeaa=0

[Meep Meep]

Thats my old config. New one works much better and has more options. Use ; to comment out sections you want to enable or disable. Only change is you have to do a bit more initial work to set it up each gaming session to get it to fully work. No issues its super easy. First is to open the tuning.cfg file and add in 'exec user.cfg' and that parts done. Second would be once in game before you drop into a match load up any test map twice and all settings should be fully enabled. You must do this every time you start the client again or if you change any settings and save. But normally its a one and done thing per session. Optionally you can go to users/~username~/saved games/mechwarrior online/shaders and delete the entire shaders folder to force the game to remake them. This can solve some odd stutter and fps issues.

;----- Max performance config.
;----- All settings to low if using N64 mode.
;----- All settings to low but textures at very high if not using N64 mode.
e_Dissolve=1
e_GI=0
e_LodCompMaxSize=255
e_LodRatio=255
e_ObjQuality=4
e_ParticlesQuality=2
e_ParticlesObjectCollisions=1
e_ParticlesPreload=1
e_PreloadDecals=1
e_PreloadMaterials=1
e_StatObjPreload=1
e_Shadows = 0
e_TerrainLodRatio=2
e_TerrainTextureLodRatio=4
e_ViewDistMin=4096

;----- 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.1

;----- Disable automatic targeting -----
gp_mech_disable_autotarget = 1


gfx_inputevents_mouse_move_threshold=0.0166
gp_mech_showfps=1
gp_default_cockpit_light = 0
g_battleDust_enable = 0

r_BatchType=0
r_DepthOfField=0
r_GeomInstancingThreshold=2
r_Reflections = 0
r_ShadersAsyncCompiling=3
r_ShadersAsyncMaxThreads=4
r_ShadersCompileAutoActivate=1
r_ShadersPreactivate=1
r_ShadersUseInstanceLookUpTable=1
r_SnowHalfRes=1
r_SSRO = 0
r_TexMaxAnisotropy=16
r_TexMinAnisotropy=16
r_Texture_Anisotropic_Level=16
r_TexturesWarmup=1
r_WaterCaustics=0
r_WaterReflectionsQuality=0
r_WaterTessellationHW=0
r_LSAO = 0
r_OpticsQuality = 0
r_MotionBlur = 0
r_SSAO=0
r_ssdo=0
r_sunshafts=0
r_Glow = 0

sys_flash_curve_tess_error=10
sys_flash_edgeaa=0

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

;----- N64 mode on ---------
e_TerrainDetailMaterialsViewDistXY = 1
e_TerrainDetailMaterialsViewDistZ = 1
r_TexturesStreaming = 1
r_TexturesStreamPoolSize = .001


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


;----- Remove Water -----
e_WaterTessellationAmount = 0
e_WaterTessellationAmountX = 0
e_WaterTessellationAmountY = 0


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

Edited by Meep Meep, 13 April 2024 - 02:11 AM.

[w0qj]

Exactly what mech/weapon config is OP (Ilostmycactus) complaining about?

MWO did indeed town down the muzzle flash especially for RAC2/AC2/LAC2 !
Recently (Feb 2024) patch toned down the RAC2/RAC5 muzzle flash.
https://mwomercs.com...-20february2024
https://mwomercs.com...auldron-changes

Just revisited my SHD-2H(S) with 3x ballistic weapons at cockpit level...
MWO did indeed town down the muzzle flash especially for RAC2/AC2/LAC2 !

Previously it was painful to play this above mech (playing MWO in a room with low ambient light).
3 years ago, I've stopped playing this fun mech specifically because my eyes hurted from these constant RAC2/AC2 flashes.

Today just tested this on same mech/weapon setup, and can confirm that
MWO did indeed town down the muzzle flash especially for RAC2/AC2/LAC2 !

Edited by w0qj, 13 April 2024 - 02:45 AM.

[An6ryMan69]

There used to literally be an option toggle to turn of your own muzzle flash, which was great.

It never should have been removed and should come back - it was there once and so it can't really be a resource issue to re-install.

[Gasboy]

w0qj, on 13 April 2024 - 02:40 AM, said:

Exactly what mech/weapon config is OP (Ilostmycactus) complaining about?

MWO did indeed town down the muzzle flash especially for RAC2/AC2/LAC2 !
Recently (Feb 2024) patch toned down the RAC2/RAC5 muzzle flash.
https://mwomercs.com...-20february2024
https://mwomercs.com...auldron-changes

Just revisited my SHD-2H(S) with 3x ballistic weapons at cockpit level...
MWO did indeed town down the muzzle flash especially for RAC2/AC2/LAC2 !

Previously it was painful to play this above mech (playing MWO in a room with low ambient light).
3 years ago, I've stopped playing this fun mech specifically because my eyes hurted from these constant RAC2/AC2 flashes.

Today just tested this on same mech/weapon setup, and can confirm that
MWO did indeed town down the muzzle flash especially for RAC2/AC2/LAC2 !

Haha, I never stopped playing my Shadow Hawks despite the bright flashes from the left shoulder. I think the flashes from red team fire have always been far more painful and irritating.

[Duke Falcon]

Ahoy!

I want to ask how\what may I need to edit and put into a user.cfg to have better texts?
Since the last patch some text became more sharp but visible only partially (in domination the three indicators for example or the little crown shows the leader of a team)...
I do not use or used a user.cfg so far but no matter what I set within the game settings the texts and some elements act as I described (I play windowed mode not fullscreen). I not set differently in my Win7 either what may caused those symptoms (and as I said it happens since the last patch)...

[Meep Meep]

New config with more options and further refinements.


;----- Max performance config.
;----- All settings to low if using N64 mode.
;----- All settings to very high if not using N64 mode for maximum pretties but still get performance boost.
;----- All settings to low and textures to very high without N64 mode to keep a good look to the game but get a higher performance boost.
;----- Must load any test map twice to fully load config after starting client or saving any setting.

;----- Performance -----
r_Batching=0
r_BatchType=0
r_GeomInstancing=1
r_GeomInstancingThreshold=2
e_Lods=0
e_ObjQuality=4
e_DynamicLightsMaxCount = 32

;----- Lower value to reduce or remove all particles at all ranges
e_ParticlesLod = 0.25


;----- 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.08

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

;----- Shadow quality range is 0=off 4=very high -----
e_Shadows=4

e_TerrainLodRatio=1
e_TerrainTextureLodRatio=4

;----- Subtract 1024 in increments to lower the view range of certain non collision objects. ergo; no garbage in the garbage pile on canyon if set to a very low number past 1024
e_ViewDistMin=3072


;----- 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 Dust Effects -----
g_BattleDust_enable=0

;----- Effects Toggles. 1=on 0=off -----
e_Dissolve=1
e_GI=1
e_Tessellation=1
e_ParticlesObjectCollisions=0
e_ParticlesShadows=0
e_ParticlesMotionBlur=0
r_ParticlesTessellation=0
r_ColorGrading=0
r_ChromaticAberration=0
r_Coronas=0
r_DepthOfField=0
r_Flares=0
r_Beams=0
r_FogShadows=0
r_FogShadowsWater=0
r_Reflections=0
r_SSReflections=0
r_SnowHalfRes=0
r_SSRO=0
r_WaterCaustics=0
r_WaterReflectionsQuality=0
r_WaterTessellationHW=0
r_LSAO=0
r_MotionBlurQuality=0
r_MotionBlurThreshold=0
r_UsePOM=1
r_SilhouettePOM=1
r_OpticsQuality=0
r_MotionBlur=0
r_SSAO=0
r_SSDO=0
r_SunShafts=0
r_Glow=0
g_RadialBlur=0

;----- AF Levels -----
r_TexMaxAnisotropy=16
r_TexMinAnisotropy=16
r_Texture_Anisotropic_Level=16

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

;----- N64 Mode On ---------
;e_TerrainDetailMaterialsViewDistXY = 0.1
;e_TerrainDetailMaterialsViewDistZ = 0.1
;r_TexturesStreaming = 1
;r_TexturesStreamPoolSize = .001

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

;----- Remove Water -----
e_WaterTessellationAmount = 0
e_WaterTessellationAmountX = 0
e_WaterTessellationAmountY = 0

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

[kalashnikity]

settings that remove water seem a bit unfair (in limited cases) because in a handful of places the stealth/ecm flea is almost 100% submerged.

[w0qj]

Muzzle flashes have already been toned down in Feb'2024 patch.
https://mwomercs.com...auldron-changes
https://mwomercs.com...-20february2024

I for one can confirm that this has been improved.
I piloted SHD-2H both before and after this Feb'2024 patch, and muzzle flashes near cockpit is noticably better!

[Meep Meep]

kalashnikity, on 24 November 2024 - 05:48 PM, said:

settings that remove water seem a bit unfair (in limited cases) because in a handful of places the stealth/ecm flea is almost 100% submerged.

Maybe, but this is legal and if one gets to use it everyone gets to use it or at least have the option. Thats why geeram released it to begin with to even the playing field. It is however banned for comp though I'm unsure how they police it.

[martian]

kalashnikity, on 24 November 2024 - 05:48 PM, said:

settings that remove water seem a bit unfair (in limited cases) because in a handful of places the stealth/ecm flea is almost 100% submerged.

PGI has no problem with the MWO players having some "unfair advantage":

"Beyond its intended purpose, it is also possible that changes to the user.cfg may sometimes be able provide an unfair or otherwise prohibited advantage to a player outside the spirit or scope of what the user.cfg file is intended to be used for.
We reserve the right to remove any functionality from the user.cfg as we see fit.

Generally, if it has been determined that a player has modified their user.cfg in such a way to gain an unfair or otherwise prohibited advantage outside the spirit or scope of what the user.cfg file is intended to be used for, they will not be subject to serious moderation actions for such behavior."

Meep Meep, on 25 November 2024 - 10:46 PM, said:

Maybe, but this is legal and if one gets to use it everyone gets to use it or at least have the option. Thats why geeram released it to begin with to even the playing field. It is however banned for comp though I'm unsure how they police it.

In theory, yes. In theory, everyone "at least has the option".

Bu my guess is that the majority of MWO players, who do not visit the forums and do not find one or two specific threads, do not even know that they could configure the user.cfg file and they would not know how to do it even if they would know about that possibility.

And of course, it is quite possible that such players do not know that other MWO players play the game with such edited user.cfg file.

[Meep Meep]

My counter would be that the majority of mwo players are in t3~5 and never or very rarely encounter the types of players who both seek out this type of config and have the skill to leverage its advantages.

[w0qj]

Many thanks for your cfg sharing!

Oh, and congrats on your nice shiny new badge too!

Meep Meep, on 26 November 2024 - 12:23 PM, said:

My counter would be that the majority of mwo players are in t3~5 and never or very rarely encounter the types of players who both seek out this type of config and have the skill to leverage its advantages.

[martian]

Meep Meep, on 26 November 2024 - 12:23 PM, said:

My counter would be that the majority of mwo players are in t3~5 and never or very rarely encounter the types of players who both seek out this type of config and have the skill to leverage its advantages.

First, the matchmaker routinely mixes players T1, T2 and T3 players (and sometimes includes T4 and T5s as well). Ditto for mixing T3, T4s and T5s with some higher Tiered players thrown in.

Second, if somebody removes vegetation or water from the map, he simply sees enemy players who think that they are well hidden in that foliage or water. No specialy "skill to leverage its advantages" is needed.

[Meep Meep]

Try it. The vegetation removal can be done by setting environment to low with the in game settings. What this allows is to have the vegetation removal but still have a high overall environment detail. The only real difference it made was on the old forest colony where it would remove ALL vegetation and old bog lily pads and those maps were removed/fixed. Water removal is about the only 'hax' and as stated above it only really effects fle trying to hide in the deep spots and there are not many of those only in a handful of maps.

[kalashnikity]

martian, on 26 November 2024 - 09:18 AM, said:

PGI has no problem with the MWO players having some "unfair advantage":

"Beyond its intended purpose, it is also possible that changes to the user.cfg may sometimes be able provide an unfair or otherwise prohibited advantage to a player outside the spirit or scope of what the user.cfg file is intended to be used for.
We reserve the right to remove any functionality from the user.cfg as we see fit.

Generally, if it has been determined that a player has modified their user.cfg in such a way to gain an unfair or otherwise prohibited advantage outside the spirit or scope of what the user.cfg file is intended to be used for, they will not be subject to serious moderation actions for such behavior."

In theory, yes. In theory, everyone "at least has the option".

Bu my guess is that the majority of MWO players, who do not visit the forums and do not find one or two specific threads, do not even know that they could configure the user.cfg file and they would not know how to do it even if they would know about that possibility.

And of course, it is quite possible that such players do not know that other MWO players play the game with such edited user.cfg file.

FWIW I I think played for almost a year before I realized there was a skill tree.

[martian]

kalashnikity, on 29 November 2024 - 12:00 PM, said:

FWIW I I think played for almost a year before I realized there was a skill tree.

Let us just say that you played MWO in the hard mode.

[kalashnikity]

I decided to test out "e_ParticlesMaxDrawScreen = 0.001"

I could not see PPCs until they were about 900m away from myself on testing ground.

And I suspect it is actually "from the person who fired them", BECASUE on a previous match today I could not see where the PPC was coming from.

So of course I started testing, and the higher the number the closer I can see the PPCs (And their trail), at 0.025 the ppc and trail became visible at about 150 m.

At 0.01 (ppc and trail) became visible at about 300m

ymmv

Edited by kalashnikity, 06 December 2024 - 12:59 PM.