58 replies to this topic

[StalaggtIKE]

@DeerSpotter: Great! You can also add spoiler tags around the code tags to clean up your post. Like so:

Spoiler

***********************************************
***********************************************
UPDATE*** this will work for every patch
***********************************************
***********************************************
Go To:
C:\Games\Piranha Games\MechWarrior Online\
copy and paste contents in there yes to all
***********************************************
***********************************************Auto way to do things (optional):
1. copy and paste "auto.bat" to C:\Games\Piranha Games\MechWarrior Online\bin32
2. run as "administrator"
3. done.after every patch must do:
1. Go to C:\Games\Piranha Games\MechWarrior Online\bin32
2. Delete CryRenderD3D10.dll
3. Run the "auto.bat"credits go to: SgtAstro for helping me create the .bat file.
***********************************************
***********************************************Manual way to do things (Recommended):
goto:
C:\Games\Piranha Games\MechWarrior Online\bin32
1. rename CryRenderD3D11.dll to CryRenderD3D10.dll
2. rename CryRenderD3D9.dll to CryRenderD3D11.dllIf modifing after patch delete CryRenderD3D10.dll and restart above.
as a reminder after every update delete CryRenderD3D10.dll & rename CryRenderD3D11.dll to CryRenderD3D10.dll and CryRenderD3D9.dll to CryRenderD3D11.dll***********************************************
***********************************************
Most important .cfg valuesr_driver="DX10"
r_Driver = dx10
r_ShadersDX10 = 1
***********************************************
***********************************************

Edited by StalaggtIKE, 09 April 2013 - 09:55 AM.

[Ferio74]

http://joxi.ru/YpFkUdg5CbBlWznqpZY
so what should i do now?
update - this problem was fixed.
New problem - game is closing, when the fight start

Edited by Ferio74, 09 April 2013 - 02:17 PM.

[DeerSpotter]

Ferio74, on 09 April 2013 - 02:08 PM, said:

http://joxi.ru/YpFkUdg5CbBlWznqpZY
so what should i do now?
update - this problem was fixed.
New problem - game is closing, when the fight start

if you cant start your client you didnt follow the instructions fully. i'll double check the code again.

[Ferio74]

DeerSpotter, on 09 April 2013 - 02:30 PM, said:

if you cant start your client you didnt follow the instructions fully. i'll double check the code again.

Maybe! Check PM please!!!

[DeerSpotter]

I cleaned up the code for easier install. i admit i was hasty putting this up and i am sorry for that. it should be easier to do this now.

Ferio74, on 09 April 2013 - 02:35 PM, said:

Maybe! Check PM please!!!

Got it!

Edited by DeerSpotter, 09 April 2013 - 04:17 PM.

[DeerSpotter]

Egomane, on 09 April 2013 - 12:49 AM, said:

Could you add a little more detail to your OP?

I quote...

i just did... lol

[wayoout]

In truth I looked up the registers you are playing with and really don't get what you are doing. Why turn something on then off the next line. Why use the budget commands without first turning on budgeting? Why turn on stuff for SLI and then set the max fps to 30. None of what you are doing makes much sense.

Plus the renaming thing really doesn't work. Don't belive me? Rename the DX9 file extension something other then dll then copy the DX11 file, paste it and rename that to your DX10. It will now load the actual DX11 stuff which doesn't work right. It will look nice for some maps but it will tear and sound will not be supported on most maps. So nice idea but not really helpful.

If you want to play with the settings in user.cfg here is a reference:

http://freesdk.cryde...CRYAUTOGEN/Home

Here is some other stuff for the engine:

http://www.tweakguid.../Crysis_10.html

Now how much of this actually will work with the game...who knows PGI will not tell us what it is using and what it is not.

Edited by wayoout, 09 April 2013 - 04:44 PM.

[nonplusultra]

DeerSpotter, on 08 April 2013 - 05:10 PM, said:

i will work on this and revisit it again. But again this works for some and not everyone. This would work better if you had a dual core jk

What do u mean? I have a dual core.

[Egomane]

DeerSpotter, on 09 April 2013 - 04:16 PM, said:

i just did... lol

What I meant is... what are you changes and commands doing. Not everyone knows those by heart.
Explain your steps in detail, so everyone knows what this step is supposed to do.

[DeerSpotter]

wayoout, on 09 April 2013 - 04:43 PM, said:

In truth I looked up the registers you are playing with and really don't get what you are doing. Why turn something on then off the next line. Why use the budget commands without first turning on budgeting? Why turn on stuff for SLI and then set the max fps to 30. None of what you are doing makes much sense.

Plus the renaming thing really doesn't work. Don't belive me? Rename the DX9 file extension something other then dll then copy the DX11 file, paste it and rename that to your DX10. It will now load the actual DX11 stuff which doesn't work right. It will look nice for some maps but it will tear and sound will not be supported on most maps. So nice idea but not really helpful.

If you want to play with the settings in user.cfg here is a reference:

http://freesdk.cryde...CRYAUTOGEN/Home

Here is some other stuff for the engine:

http://www.tweakguid.../Crysis_10.html

Now how much of this actually will work with the game...who knows PGI will not tell us what it is using and what it is not.

because i was unsure of the commands when i first tried them.

I would rather have some commands turned off, but if it cant be i made sure the commands before that will at least be set to low.

I hope that clarifies the confusion. This "fix" doesnt focus onto the user.cfg as much as the dx11 to dx10. You probably enjoy trolling here because your computer gets like 90fps already. Get your old laptop out and try this and see the amazement.

Like i already said, if you run this game in dx11 only it screws everything up. (referring to what you said) I understand what you mean: getting rid of the dx9 and using 2 dx11's but one renamed to 10.

Thank you for the helpful tips for the user.cfg's i already had those resources but i was't aware of turning on budgeting i'll look into that. again this isn't a permanent fix and i don't understand why it works, but if i don't use it, i can't play the game. It's simple as that.

Edited by DeerSpotter, 10 April 2013 - 02:20 PM.

[Manny Rhyde]

i tried the fix but my folder didnt have an auto.bat file, when i tried to start the game, i had alot of textures missing, i might have to reinstall the game completely =/

[mr bear]

Followed the instructions as per OP.
FPS rate went up from 9 to 12. A slight improvement but still way lower than pre-April's patch. Thanks for the help in doing up the commands though.

[DeerSpotter]

manny082, on 11 April 2013 - 08:40 AM, said:

i tried the fix but my folder didnt have an auto.bat file, when i tried to start the game, i had alot of textures missing, i might have to reinstall the game completely =/

manny you have to rename the .dll files oh and the auto.bat file you create yourself. Guys please follow the instructions to the bone. I know it was easier with the files there but i'm not allowed to post download links.

[Featherwood]

Confirmed. Workaround works for me. 15+ fights without various glitches, had lot of them (no HUD, no map, reversed minimap, textures glitches and so on) before tweaking.
Kudos to topicstarter.

Edit: IMO, topic should be moved to workarounds sub-forum, that fix is most actual for PATCH 1.2.209.

Edit2: BTW, I'm using my own useg.cfg version, th eone from this tutorial has too many errors, I just swapped DirectX libraries as OP suggested - and that was sufficient to fix the glitches. Hint: don't forget to clean cache folder in user profile, it may cause textures glitches after libs change.

Here is copy of mine:

Spoiler

;--- DirectX libraries selection
r_Driver = dx10
r_ShadersDX10 = 1

;--- Tripple Buffering disabled -- required for DX10 tweak? I'm not sure.
d3d11_TripleBuffering = 0
d3d10_TripleBuffering = 0
d3d9_TripleBuffering = 0

;--- FPS control
sys_MaxFPS = 35

;--- Force MultiTread support -- default is to auto-detect (r_MultiThreaded = 2)
r_MultiThreaded = 1

;--- MultiGPU suport
;r_MultiGPU = 1
;r_MultiGPU = 2

;--- System Specifications
sys_budget_videomem = 1024
sys_budget_sysmem = 4096

;--- Physics
;--- CPU used for physics "-1"=No CORES "0"=CORE1, "1"=CORE2, "2"=CORE3, "3"=CORE4
sys_physics_CPU = 3
;p_gravity_z = -36.3
p_gravity_z = -50
g_joint_breaking = 1
p_joint_damage_accum = 2
p_joint_damage_accum_threshold = 0.2
g_breakage_particles_limit = 180

;--- Special Effects -- pre-defined top-level effects
sys_spec_GameEffects = 4
sys_spec_ObjectDetail = 4
sys_spec_Particles = 4
sys_spec_PostProcessing = 4
sys_spec_Shading = 4
sys_spec_Shadows = 4
sys_spec_Texture = 4
sys_spec_Environment = 4

;--- Zoom
;--- [Default: 0.2] Transition time in seconds between zoom levels
gp_mech_view_zoom_transitiontime = 0.05

;--- HUD hit effects
r_HUDHitEffect = 3

;--- Feild Of View distance -- MWO has 70 by default
cl_fov = 71

;--- Controller sensivity
i_mouse_smooth = 0
i_mouse_accel=0
cl_sensitivity = 0.8
cl_sensitivityController = 0.1
i_mouse_accel_max = 0

;--- Brightness
r_Brightness = 0.55

;--- Night Vision tuning
r_NightVisionBrightLevel = 0.8
r_NightVisionCamMovNoiseAmount = 0.2
r_NightVisionCamMovNoiseBlendSpeed = 5
r_NightVisionAmbientMul = 6
r_NightVisionFinalMul = 3
r_NightVisionSonarLifetime = 2
r_NightVisionSonarMultiplier = 0.2
r_NightVisionSonarRadius = 64
r_NightVisionViewDist = 2500

;--- Anti-Aliasing
;--- MSAA fix for ATI - toggle as needed. FSAA can work with injector.
r_PostMSAA = 1
r_PostProcessEffects = 0
r_FSAA = 0

;--- Shaders quality (1-4), MWO has 2 by default
;--- q_Quality defines entire array, tune partucular options if interested
q_Quality = 4
;q_Renderer = 3
;q_ShaderFX = 3
;q_ShaderGeneral = 3
;q_ShaderGlass = 3
;q_ShaderHDR = 3
;q_ShaderIce = 3
;q_ShaderMetal = 3
;q_ShaderPostProcess = 3
;q_ShaderShadow = 3
;q_ShaderSky = 3
;q_ShaderTerrain = 3
;q_ShaderVegetation = 3
;q_ShaderWater = 3

;--- Particles
e_ParticlesQuality = 4
e_ParticlesThread = 1
e_ParticlesLights = 1
e_ParticlesMaxScreenFill = 128
e_ParticlesMinDrawPixels = 1
e_ParticlesMotionBlur = 0
e_ParticlesObjectCollisions = 1
r_UseParticlesHalfRes = 0
r_UseSoftParticles = 1

;--- Light effects
i_lighteffects = 1
i_iceeffects = 1

;--- various funny trash
v_vehicle_quality = 4

Edited by Featherwood, 13 April 2013 - 08:56 AM.

[Tarl Cabot]

The workaround, afaik, renames a couple of the MWO dll files then forces MWO to run in DX10 mode (MWO does not prevent it, though with this workarond, it likely means it does prevent it from using DX11, maybe). DX11, iirc, is backward compatible with DX10. This workaround likely will not work on XP machines since DX9c is the highest directx it can run.

So, if this workaround does what I believe it does, making it run with DX10 modules/commands, the more of the workload is passed onto the CPU, OR the game is not runniing, graphically, everything it should be, reducing the overall workload. And for those already with low FPS, they may not really notice what is or is not missing.

Or I could be completely wrong, almost completely wrong, or drunk..../shrugs.

[Banditman]

This set of lines in 1. User.cfg looks wrong to me:

r_driver="DX10"
r_Driver = dx10
r_ShadersDX10 = 1d3d11_TripleBuffering = 0
d3d10_TripleBuffering = 0
d3d9_TripleBuffering = 0

I believe it should be:

r_driver="DX10"
r_Driver = dx10
r_ShadersDX10 = 1
d3d11_TripleBuffering = 0
d3d10_TripleBuffering = 0
d3d9_TripleBuffering = 0
I'm also not 100% sure about those quotation marks around DX10 in the r_driver line.

[DeerSpotter]

Banditman, on 12 April 2013 - 10:56 PM, said:

This set of lines in 1. User.cfg looks wrong to me:

r_driver="DX10"
r_Driver = dx10
r_ShadersDX10 = 1d3d11_TripleBuffering = 0
d3d10_TripleBuffering = 0
d3d9_TripleBuffering = 0

I believe it should be:

r_driver="DX10"
r_Driver = dx10
r_ShadersDX10 = 1
d3d11_TripleBuffering = 0
d3d10_TripleBuffering = 0
d3d9_TripleBuffering = 0
I'm also not 100% sure about those quotation marks around DX10 in the r_driver line.

thank you for fixing that...

I'll edit it. I don't know why but when i copied from txt to here it ruined it...scrambled it. I used quotes just in case.

Edited by DeerSpotter, 13 April 2013 - 08:34 AM.

[DeerSpotter]

Tarl Cabot, on 12 April 2013 - 10:22 AM, said:

The workaround, afaik, renames a couple of the MWO dll files then forces MWO to run in DX10 mode (MWO does not prevent it, though with this workarond, it likely means it does prevent it from using DX11, maybe). DX11, iirc, is backward compatible with DX10. This workaround likely will not work on XP machines since DX9c is the highest directx it can run.

So, if this workaround does what I believe it does, making it run with DX10 modules/commands, the more of the workload is passed onto the CPU, OR the game is not runniing, graphically, everything it should be, reducing the overall workload. And for those already with low FPS, they may not really notice what is or is not missing.

Or I could be completely wrong, almost completely wrong, or drunk..../shrugs.

haha so hard to understand...i'm not going to pretend i'm smart and all that, all i'm trying to do is get the game to run on my comp. properly. then i realised everybody is in the same boat as me so thats why i'm helping out. I have figured out other ways to speed up the game, but they are not yet stable for a public release or even bother support about it.

Edited by DeerSpotter, 13 April 2013 - 02:27 PM.

[warp103]

So a ez way to fix a bit of the issue but it cannot be dl. Oh and force triple buffer can help too. ! can not give you the link sorry some crazy rules

Edited by warp103, 13 April 2013 - 03:42 PM.