372 replies to this topic

[Legend_]

Does anyone have or know of a list of cvars that can be used in the user.cfg without needing to add or modify files, especially commands that will clear up the game and make it look crisper and generally better?

[WheezerX]

Link is busted for CFG download

[Clint Steel]

Vodage, on 06 June 2014 - 02:11 PM, said:

I see a lot of CFG's posted with really pretty graphics. I'm looking for something more like this

Edit: video isn't embedding properly >< http://youtu.be/DreDIhnK-co


^Most pro QL players run settings like these. Granted, Quake is a different style of game, where neon green enemies have become tournament standard. So maybe PGI won't let me remove all textures from all surfaces through the CFG-- but can I at least get blob shadows? Howabout less of this blockbuster-esque overexaggeration of every particle effect? Foliage elimination would be nice, too. If I can shoot through it, I should be able to see through it

Has anyone put together a CFG for max visibility? ...the tournament players perhaps?

I wish that lower graphics settings let you see worse than the higher ones, rather than the opposite, so lame that its "better" to run with everything off and have the game look like crap. Something like having opaque smoke if you can't run regular smoke, not just get rid of it.

[Corvus Antaka]

I've updated the first post in this thread with my final user.cfg files for the game. [redacted]

Thanks,

Vinson

Edited by Egomane, 13 August 2014 - 05:30 AM.
removed instructions on how to get the file

[Egomane]

And I removed the link, as the file contains instructions to modify the game in a way not intended by the devs.

@Pada Vinson
Only modifications to the user.cfg itself are acceptable. You can link it and advertise it here, if you remove the parts that do not comform to this rule.

Edited by Egomane, 13 August 2014 - 01:14 PM.

[Corvus Antaka]

Alright then.

I've pulled the user.cfg file from our website. Obviously for the past 3 years it was acceptable to use these files, but it is no longer the case, so good luck out there guys. I only reposted this since the last 2 patches have brought FPS below 30 again, and some of you requested assistance. Sorry folks, but it looks like you'll have to hope PGI can fix these issues for you from now on.

[Corvus Antaka]

Egomane, on 13 August 2014 - 05:30 AM, said:

And I removed the link, as the file contains instructions to modify the game in a way not intended by the devs.

@Pada Vinson
Only modifications to the user.cfg itself are acceptable. You can link it and advertise it here, if you remove the parts that do not comform to this rule.

oh, someone from PGI visited my website and downloaded content from it?

thanks Egomane.

[Grey Ghost]

As to your config... I'm fairly certain the blanked out "CVarGroups_MWO" folder doesn't actually do anything, and hasn't for quite some time. Plus the film grain removal file included does nothing as well, and again hasn't for some time. There is now a user.cfg command to remove film grain instead.

All that's left is your actual user configs which I assume are alright to post.

[Colonel Tequila]

the content has been moderated?!

poor show, pada has done good justice to the community for the past 3 years..... tut tut....

I hope someone will continue to take up the mantle of 'fixing' mwo - each patch I have wild FPS changes - I refuse to buy a new graphics card!!

[Reno Blade]

Colonel Tequila, on 16 August 2014 - 11:16 PM, said:

the content has been moderated?!

poor show, pada has done good justice to the community for the past 3 years..... tut tut....

I hope someone will continue to take up the mantle of 'fixing' mwo - each patch I have wild FPS changes - I refuse to buy a new graphics card!!

Ego edited his post already on the 13th. User.cfg files are allowed.

[El Rizzo]

@Colonel Pada Vinson

Thank you so much for your cfgs ! It made the game a lot more enjoyable

@Everyone

For a few Patches now I am experiencing green smoke in Heatvision again, either when I use a clean install of the game without any cfg modifications, or with my usual cfg (Reno Blade's personal cfg from page 17) and r_FogShadows = set to 0 or simply disabled with a semicolon doesn't remove the green smoke.
So my question is, has anyone else had this problem occuring again and does anyone know how to get rid of it, because on some maps like frozen city I usually play 80% in Heatvision and now it is impossible to do so and seriously affects my gameplay on such maps.

I am running in Dx9 Mode with everything at max Settings except PostAA, which is disabled since the cfg enables its own AA and this is what my current cfg looks like:

Spoiler

cl_fov = 79 (Default is 75)
gp_option_ShowCockpitGlass = 0
r_HDRGrainAmount = 0.0
r_DepthOfField = 0
sys_spec_Quality=4
sys_spec_GameEffects = 4
sys_spec_ObjectDetail = 4
sys_spec_Particles = 4
sys_spec_PostProcessing = 1
sys_spec_Shading = 4
sys_spec_Sound = 4
sys_spec_Shadows = 4
sys_spec_Texture = 4
sys_spec_Environment = 4
r_ColorGrading = 0
r_GlowAnamorphicFlares = 1
r_HDRBloomMul = 0.5
r_HDRBlueShift = 0
r_HDRBrightLevel = 0.85
r_HDRBrightOffset = 5
r_HDRBrightThreshold = 6
r_HDREyeAdaptionCache = 0
r_HDRGrainAmount = 0
r_HDRLevel = 3
r_HDROffset = 10
r_HDRRendering = 1
r_UseEdgeAA = 1
;MotionBlur Fun
r_MotionBlur = 0
;r_MotionBlurMaxViewDist = 100
;r_MotionBlurShutterSpeed = 0.00001
g_dofset_maxscale = 1
g_radialBlur = 1
r_UsePOM = 1
r_PostProcessHUD3DCache = 0
r_RainMaxViewDist_Deferred = 100
r_Sunshafts = 1
r_Flares = 1
q_Renderer = 3
q_ShaderFX = 3
q_ShaderGeneral = 3
q_ShaderGlass = 3
q_ShaderHDR = 3
q_ShaderIce = 3
q_ShaderMetal = 3
q_ShaderPostProcess = 2
q_ShaderShadow = 3
q_ShaderSky = 3
q_ShaderTerrain = 3
q_ShaderVegetation = 3
e_Shadows = 1
e_GsmCache = 0
e_GsmLodsNum = 4
e_GsmRange = 3
e_ParticlesShadows = 0
e_ShadowsCastViewDistRatio = 1
e_ShadowsMaxTexRes = 1024
e_ShadowsOnAlphaBlend = 0
e_ShadowsResScale = 4.0
r_ShadowBlur = 3
r_ShadowJittering = 2.5
r_ShadowsPCFiltering = 1
r_ShadowsUseClipVolume = 1
;r_FogShadows = 1
;bugged;r_ShadowsMaskResolution = 1
s_MPEGDecoders = 32
s_Obstruction = 1
s_ObstructionAccuracy = 1
s_ObstructionUpdate = 0.1
s_SoundMoodsDSP = 1
s_VariationLimiter = 1
e_WaterOceanFFT = 1
e_WaterTessellationAmount = 10
e_WaterTessellationAmountX = 85
e_WaterTessellationAmountY = 85
e_WaterTessellationSwathWidth = 10
r_WaterCaustics = 1
r_WaterReflections = 1
r_WaterReflectionsQuality = 5
r_WaterReflectionsMinVisiblePixelsUpdate = 0.05
r_WaterTessellationHW = 1
r_WaterUpdateDistance = 0.2
r_WaterUpdateFactor = 0.05
e_DynamicLightsMaxEntityLights = 32
e_GI = 1
e_GIAmount = 0.5
e_GINumCascades = 3
e_GIMaxDistance = 100
e_SkyType = 1
e_SkyUpdateRate = 1
e_TerrainAo = 1
e_TerrainNormalMap = 1
e_VegetationUseTerrainColor = 1
r_DetailDistance = 20
r_DetailTextures = 1
r_ssdo = 2
r_SSDOAmount = 0.9
r_SSDOAmbientAmount = 1.5
r_SSAO = 0
r_SSAOQuality = 3
r_SSAODownscale = 0
r_refraction = 1
r_SSReflections = 3
r_Beams = 3
r_BeamsDistFactor = 0.01
r_BeamsMaxSlices = 300
e_Clouds = 1
r_CloudsUpdateAlways = 1
r_Reflections = 1
e_GsmRangeStep = 4
e_GsmCastFromTerrain = 1
r_ChromaticAberration = 1.5
i_lighteffects = 1
g_ragdollMinTime = 15
g_ragdollUnseenTime = 3
g_ragdollDistance = 40
e_ObjQuality = 4
e_DecalsAllowGameDecals = 1
e_DecalsLifeTimeScale = 2
e_DecalsOverlapping = 1
e_Dissolve = 2
e_LodRatio = 40
e_Lods = 1
e_LodMin = 0
e_MaxViewDistSpecLerp = 1
e_OcclusionCullingViewDistRatio = 1
e_ProcVegetation = 1
e_streamCgf = 0
e_VegetationBending = 1
e_VegetationMinSize = 0
e_VegetationSpritesDistanceCustomRatioMin = 1
e_VegetationSpritesDistanceRatio = 1.5
e_ViewDistMin = 10
e_ViewDistRatio = 100
e_ViewDistRatioCustom = 100
e_ViewDistRatioDetail = 100
e_ViewDistRatioLights = 100
e_ViewDistRatioVegetation = 100
e_TerrainDetailMaterialsViewDistXY = 2048
e_TerrainDetailMaterialsViewDistZ = 256
e_TerrainOcclusionCullingMaxDist = 200
ca_AttachmentCullingRation = 300
ca_DrawFaceAttachments = 1
ca_useDecals = 1
es_DebrisLifetimeScale = 1
i_rejecteffects = 1
e_Tessellation = 1
e_DecalsForceDeferred = 1
r_DrawNearZRange = 0.08
e_ParticlesQuality = 4
e_ParticlesLights = 1
e_ParticlesMaxScreenFill = 160
e_ParticlesMinDrawPixels = 1
e_ParticlesMotionBlur = 1
e_ParticlesObjectCollisions = 2
r_UseParticlesHalfRes = 0
r_UseSoftParticles = 2
r_UseParticlesRefraction = 1
g_breakage_particles_limit = 160
g_joint_breaking = 1
g_tree_cut_reuse_dist = 0
e_CullVegActivation = 50
e_FoliageWindActivationDist = 25
e_PhysFoliage = 2
e_PhysOceanCell = 0.5
p_gravity_z = -36.3
p_joint_damage_accum = 2
p_joint_damage_accum_threshold = 0.2
p_max_MC_iters = 6000
p_max_object_splashes = 3
p_max_substeps_large_group = 5
p_num_bodies_large_group = 100
p_splash_dist0 = 7
p_splash_dist1 = 30
p_splash_force0 = 10
p_splash_force1 = 100
p_splash_vel0 = 4.5
p_splash_vel1 = 10
v_vehicle_quality = 4
es_MaxPhysDist = 200
es_MaxPhysDistInvisible = 25
r_DynTexAtlasCloudsMaxSize = 32
r_DynTexAtlasSpritesMaxSize = 32
r_DynTexMaxSize = 80
r_EnvCMResolution = 2
r_EnvTexResolution = 3
r_EnvTexUpdateInterval = 0.001
r_ImposterRatio = 1
r_TexSkyResolution = 0
r_TexAtlasSize = 2048
r_TexMinAnisotropy = 8
r_TexBumpResolution = 0
r_TexResolution = 0
r_TexturesStreaming = 0
r_VegetationSpritesTexRes = 64
e_TerrainTextureLodRatio = 1
e_CoverageBufferReproj = 1
e_TerrainTextureStreamingPoolItemsNum = 256

Edited by El Rizzo, 19 August 2014 - 12:29 PM.

[Reno Blade]

Hey El Rizzo,

I use DX11 without problems. But I checked DX9 (without config) and if you set the details for Shadows to Very High it turns green. High/med is normal.

I went into the game and tried with different cfg line disabled/changed, but it did not help.
Then I just loaded another RC night and switched the Shadow slider in the adv. settings to High and it was gone.

I guess this option now overrides the config, or the config line with r_FogShadows = 0 no longer is valid.

[El Rizzo]

Hey Reno Blade,

just tested your solution and it works with shadows set to high ! so first of all thanks for the very quick response and a working solution

Regarding Directx 11, I would love to switch to Dx11, but the last time I tested it, I had lower fps than with Dx9 so I switched back and now I am waiting until PGI finally makes Dx11 viable, or has the performance improved already and PGI simply didn't mention it in one of the patchlogs ? (or I didn't read it )

[Reno Blade]

You are welcome.

I upgraded my GTX 560Ti (2GB) to a GTX 770 OC (4GB) and my fps is now up in the 60s (vsync off = 100fps) with lowest dips to 40, where I had usually 45 with dips to 20 fps.

I am still not using MSAA or TXAA (only PostAA) as these can bring fps down to 48fps in the testing grounds and I don't want to run into game with less than 30fps anymore.
I don't even notice any difference anyway

Edited by Reno Blade, 19 August 2014 - 01:33 PM.

[El Rizzo]

Well, the improved Fps make sense from upgrading your GPU but I just tested Dx11 again on my GTX 780 and the overall GPU Load is higher to achieve the same FPS I get using Dx9, for example:

Using Dx9 and a driver set Fps Limit of 58 (less Tearing than 60, at least it feels like less to me ), my GPU usually runs at 889Mhz and about 40-60% load on River City, using the Testing Grounds.

Using the same scenario and map location with Dx11, the card runs at full Clockrate of 1163Mhz and about 50-60% load thus demanding more GPU Power than Dx9 although both times I had the same constant 58 Fps.

So you might try Dx9 and find your Fps going up and dropping less into the 40s The simplest way to test this is to use Msi Afterburner's OSD to monitor your GPU load and clockrate while ingame, thats at least how I did it and don't worry, you don't need a MSI card to use the software, it runs with pretty much any card of any vendor, mine for example is from Gigabyte.

[Grey Ghost]

Colonel Pada Vinson, on 18 January 2013 - 11:53 AM, said:

Since egomane and PGI killed this topic, I'm calling it quits. Good luck out there.

This was quite the overreaction. In any case, farewell and good luck to you Colonel Pada Vinson. My interactions with you in the Closed Beta were incredibly helpful, and instrumental to my enjoyment of the game in those early days.

*Query for Thread*
I downloaded the configs before the link was removed. I could just post the content of the user.cfg's here, if they are something that is wanted.

[El Rizzo]

@Grey Ghost
That would be nice, I would like to see what he changed and how it affects the game.

[Modo44]

Grey Ghost, on 21 August 2014 - 11:42 PM, said:

This was quite the overreaction.

Actually, no, it is not. It is not the first time PGI ****** with him for trying to unlock some performance/prettiness in MWO.

[Egomane]

Grey Ghost, on 21 August 2014 - 11:42 PM, said:

*Query for Thread*
I downloaded the configs before the link was removed. I could just post the content of the user.cfg's here, if they are something that is wanted.

Please fell free to do so.

Just make sure that there really isn't anything in there, besides the user.cfg files and explainations. There were some .xml file modifications explained in the textfiles, as well as some additional file to be added to the game client in there. All those need to be thrown out, as they are rule violations.

Modo44, on 22 August 2014 - 10:13 AM, said:

Actually, no, it is not. It is not the first time PGI ****** with him for trying to unlock some performance/prettiness in MWO.

The rules on modifications to the game files are clear and known for a long time. I do not know why he, or you as far as it matters, is so shocked that they are enforced on the forums. I find his reaction kind of sad, as even without the parts, that are in violation to the rules, his work would have been extremly helpfull.

[Modo44]

I am shocked by closing off -- hard -- an entire modding path that could help PGI and players alike, not by rule enforcement itself.

Edited by Modo44, 22 August 2014 - 10:33 AM.