85 replies to this topic

[Wildstreak]

OK, I need some things cleared up. It is mentioned in the OP how to make a SYSTEM.CFG file and a SYSTEMOVERRIDE.CFG file. Confusing point is the second, when MWO runs, replaces the first so why do both?
Why do they have different line entries if SYSTEMOVERRIDE is used instead of SYSTEM? Shouldn't the entries in SYSTEM be in SYSTEMOVERRIDE?

Right now, I only set up USER.CFG with the following lines:

i_joystick_deadzone = 0.0005
sys_MaxFPS = 30
r_MultiThreaded = 1
r_MultiThreaded = 2
r_MultiGPU = 1
r_MultiGPU = 2
sys_budget_videomem = 512
sys_budget_sysmem = 2048
sys_physics_CPU = 0
sys_physics_CPU = -1
sys_streaming_cpu = 1
sys_streaming_cpu = 0
sys_streaming_cpu = -1
sys_spec_Physics = 0
sys_spec_Physics = -1
r_driver="DX9"
r_Driver = dx9
d3d9_TripleBuffering = 0

These are the ones that do not show causing errors in Omicron. The first is the only joystick line I have found that is needed and works, it improves the response of the right stick on my HOTAS from the slow as molasses movement it had by default.

The rest, I used to get between ~10-14 FPS, now so far I seem to have ~20 give or take a couple but as you see in the next paragraph, I am not sure if these settings and / or my nVidia Control Panel changes did it. Only tested on one map so far, the new HPG Manifold, I will have to see if this continues on other maps.

I also did a bit of fiddling with certain nVidia Control Panel settings, once it bumped up FPS to the same level ~20 but after another change or two, it dropped again.

I have not changed any of the DirectX related files around this time, I don't find any for DX10 anyway.

[Lord Letto]

Hi, I Have a AMD FX4100 (Quad Core) and a EVGA GTX 560TI 2GB, What I done to User.cfg is set FOV to 75 and Limit Framerate to 30 and the DX10 Part, in system.cfg, I changed DX9 to DX10, in systemoverride.cfg I copy and pasted what you said to copy and paste. Problem is that I either get a Failed to initialize game or a screwed up Client Screen that I can't see. when it's the Failed to initialize game it's the CryRenderD3D9.dll and CryRenderD3D10.dll (Renamed CryRenderD3D11.dll cause there was no CryRenderD3D10), with screwed up Client Screen it's both of the above with CryRenderD3D11.dll (So all 3)

Example of screwed up client screen:




Reason why I wanted to try it is my FPS Goes from the 40-50 down to the teen-20 Range with a average in the 30 range, I wanted to test it to see if the FPS would be more stable and how it would look as I missed the DX11 Public Test.

so I guess it's DX9 for now.

Edited by Lord Letto, 20 December 2013 - 05:05 PM.

[shellashock]

Lord Letto, on 20 December 2013 - 05:01 PM, said:

Reason why I wanted to try it is my FPS Goes from the 40-50 down to the teen-20 Range with a average in the 30 range, I wanted to test it to see if the FPS would be more stable and how it would look as I missed the DX11 Public Test.

so I guess it's DX9 for now.

Looks like someone picked the wrong picture. Either that, or your client turns invisible when you take a printscreen.

[Flying Judgement]

shellashock, on 20 December 2013 - 06:40 PM, said:

Looks like someone picked the wrong picture. Either that, or your client turns invisible when you take a printscreen.

its there in the middle XD

is any one knows how to change the AC or engine sound values ?

[shellashock]

Lord Letto, on 20 December 2013 - 05:01 PM, said:

Hi, I Have a AMD FX4100 (Quad Core) and a EVGA GTX 560TI 2GB, What I done to User.cfg is set FOV to 75 and Limit Framerate to 30 and the DX10 Part, in system.cfg, I changed DX9 to DX10, in systemoverride.cfg I copy and pasted what you said to copy and paste. Problem is that I either get a Failed to initialize game or a screwed up Client Screen that I can't see. when it's the Failed to initialize game it's the CryRenderD3D9.dll and CryRenderD3D10.dll (Renamed CryRenderD3D11.dll cause there was no CryRenderD3D10), with screwed up Client Screen it's both of the above with CryRenderD3D11.dll (So all 3)

Reason why I wanted to try it is my FPS Goes from the 40-50 down to the teen-20 Range with a average in the 30 range, I wanted to test it to see if the FPS would be more stable and how it would look as I missed the DX11 Public Test.

so I guess it's DX9 for now.

Ok, let's try that again. First off, use the repair tool to completely wipe any traces of tampering with names or values.

Then follow through with Deerspotter's steps.
Only thing you should modify is anything that he tells you to change to dx10, change it to dx11. This includes the cryengine.dll and the r_shaders = 1 section. Maybe that will help?

[Leafia Barrett]

DeerSpotter, on 04 October 2013 - 06:09 PM, said:

;----------------------------------------------------------------------------
sys_physics_CPU = 0
sys_physics_CPU = -1
;CPU used for physics "-1"=No CORES "0"=CORE1, "1"=CORE2, "2"=CORE3, "3"=CORE4
;----------------------------------------------------------------------------
 
;----------------------------------------------------------------------------
;----testing i want no physics on cpu but as much as possible on gpu.--------
;----------------------------------------------------------------------------
sys_streaming_cpu = 1
sys_streaming_cpu = 0
sys_streaming_cpu = -1
sys_streaming_gpu = 1
sys_streaming_gpu = 2
sys_physics_GPU = 1
sys_physics_GPU = 2
gpu_Particle_Physics = 1
gpu_Particle_Physics = 2
sys_spec_Physics = 0
sys_spec_Physics = -1
sys_spec_Water = 0
sys_spec_Water = -1

Can someone help me do the exact opposite of this? I want as much of the strain off of my GPU as possible. My CPU is plenty powerful, but my GPU is pathetic.

[shellashock]

I would appreciate this as well. I am definitely bottle-necked by my integrated HD Graphics 2000, even with MW:O's current extremely high CPU dependence.

From that .cfg, the best i can think of is simply taking all the things that have "gpu" attached to it and changing it to "cpu". Deerspotter is trying to find out how to disable or reduce shaders that are taxing but progress is slow right now. Look around the forums in the mean time and there should be a thread that is for user cfgs; which features an ultra high and ultra low performance user. cfg.

[DeerSpotter]

Merchant, on 19 December 2013 - 04:14 PM, said:

OK, I need some things cleared up. It is mentioned in the OP how to make a SYSTEM.CFG file and a SYSTEMOVERRIDE.CFG file. Confusing point is the second, when MWO runs, replaces the first so why do both?
Why do they have different line entries if SYSTEMOVERRIDE is used instead of SYSTEM? Shouldn't the entries in SYSTEM be in SYSTEMOVERRIDE?

Right now, I only set up USER.CFG with the following lines:

i_joystick_deadzone = 0.0005
sys_MaxFPS = 30
r_MultiThreaded = 1
r_MultiThreaded = 2
r_MultiGPU = 1
r_MultiGPU = 2
sys_budget_videomem = 512
sys_budget_sysmem = 2048
sys_physics_CPU = 0
sys_physics_CPU = -1
sys_streaming_cpu = 1
sys_streaming_cpu = 0
sys_streaming_cpu = -1
sys_spec_Physics = 0
sys_spec_Physics = -1
r_driver="DX9"
r_Driver = dx9
d3d9_TripleBuffering = 0

These are the ones that do not show causing errors in Omicron. The first is the only joystick line I have found that is needed and works, it improves the response of the right stick on my HOTAS from the slow as molasses movement it had by default.

The rest, I used to get between ~10-14 FPS, now so far I seem to have ~20 give or take a couple but as you see in the next paragraph, I am not sure if these settings and / or my nVidia Control Panel changes did it. Only tested on one map so far, the new HPG Manifold, I will have to see if this continues on other maps.

I also did a bit of fiddling with certain nVidia Control Panel settings, once it bumped up FPS to the same level ~20 but after another change or two, it dropped again.

I have not changed any of the DirectX related files around this time, I don't find any for DX10 anyway.

it really works with the the DX10, otherwise you are just not doing anything useful. AS i mentioned in the forums. I do both just so you will know it works. I know PGI tried disabling this in the past by including the systemoverride.cfg when i told everyone to write in system.cfg.

I have found the shaders that are causing the problems and i have to go through and mess with .pak files to remove them, this is something im afraid of releasing because it could cause a ban by modifying the files.

and also a stupid workaround because pgi then will block the workaround. I will try to disable shaders through .cfg so it could be universal.

Ive seen in some .cfg files floating around here shaders values at = 0 if you guys in the meantime find them and try them that would be kool.

[MetalBacon]

Did this, went from 10-15 fps to 20-50 with 30 on average, 20 when there are like 12 spiders on screen going pewpew. Good job DeerSpotter

Also, strangely enough, playing in fullscreen window mode adds about 10 frames on average.

[Fa11en_Universe]

Ребята, фризит... ПИЗДЕЦ!!! Шо делать!? ОТВЕЧАЙТЕ БЫСТРО
По теме:
Guys, i made all the solution to fix freezing in game, but all are usless.
I've got 560Ti nvidia, 4gb ram, Xeon X3330 2.66ghz
I've got 40-60 fps, but sometimes game freezing like hell. help me

[hamster1979]

I had freezes (2 core Intel G2130). First of all i ran Repare MWO tool, it fix some config bugs. But i still had freezes. After this I applied this manual on my game and have already 4 days without freezes. Great work, man. Spasibo!

Edited by hamster1979, 01 February 2014 - 09:07 AM.

[DeerSpotter]

bump.

[That Dawg]

DeerSpotter, on 13 February 2014 - 09:13 PM, said:

bump.

tried it, wolfdale e8400 3.4 core duo, gtx 580 and all the mechs vanished. enemy mechs, friendly mechs.
there was a ghostish silhouette sort of, but first map I dropped into Manifold, was a serious disadvantage.
frames were the same before adding all your stuff, just the mechs went textureless, like happens on that one winter city map on rare occasions.

Edited by ThatDawg, 20 February 2014 - 04:06 AM.

[Shamous13]

Igchy, on 25 February 2014 - 05:56 AM, said:

For 32 bit users, there is a workaround but it may have adverse effects so b careful to leave the original line and add the line as indicated in this steps..

Windows support a switch option in BOOT.INI called the /3GB switch, which adjusts the way memory is allocated between the user and the operating system. By default, the split is fifty-fifty -- up to two gigabytes for the user and two for the operating system. The /3GB switch option sets those limits at three gigs maximum for the user and one gig for the operating system.

As the name implies, /3GB was originally meant to be used in systems that have 3 GB or more of RAM -- something that is no longer quite as rare as it used to be! However, even if you don't have 3 GB or more of memory, you can still use the /3GB switch successfully if you are running memory-hungry desktop applications. Photoshop, for instance, is infamous for staking out as much RAM as it can. With /3GB enabled, there's that much more memory that the application can use.

To add the /3GB switch as a separate boot option:

1-In My Computer | Properties | Advanced | Startup and Recovery, click Settings.






2-Click the Edit button under System Startup to edit the BOOT.INI file.


3-Find the current boot entry, which typically looks like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


4-Copy the line on step 3, from your own BOOT.INI not from this post, and paste it at the end of the BOOT.INI file as a second entry, and change the description and add the /3GB flag, something like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB Switch" /fastdetect /3GB
This lets you choose between a conventional boot entry and the /3GB boot entry. If something goes wrong when you use /3GB, you can always boot back into the original configuration.

5-Save and close BOOT.INI.

6-Click OK to close the Startup and Recovery panel.

7-Click Settings again, and in the "Default operating systems:" dropdown, choose the newly created boot entry with the /3GB switch.

8-Click OK to close everything. Reboot into the new profile.


This works for me Credit :
Fantastic Ergo

[shellashock]

DX11 is officially live! Took em long enough, but that's besides the point. It still has optimization to go, so don't hold your breath for a big performance boost.

[Whatzituyah]

shellashock, on 04 March 2014 - 11:52 AM, said:

DX11 is officially live! Took em long enough, but that's besides the point. It still has optimization to go, so don't hold your breath for a big performance boost.

Yeah its like there was barely any performance boost.

[Vincent V. Kerensky]

Seems this fix does not work anymore then. Tried applying it after a full reinstall but I do not get into the Mech Bay even.

[Vervuel]

Hmmm this looks interesting, but before I go playing with the files, I have a Asus g73, i7-720Q 1.6gHz, 12.0 GB (thanks to some extra laying around), 64 bit, Win 7, HD 5870 mobile. stay at around 25 FPS in match, dips to 15 with flamers/mg's/missiles. Have all setting to th elowest of course. Will these workarounds do much for me?

[shellashock]

Looks like this patch fixed the fps stuttering. Still trying to determine whether or not DX11 gives me an fps boost or not. Out of 30 test matches, I think the winner is still DX9.

[That Dawg]

We drop with around 6 different guys, NONE have reported any increase with dx11, the opposite is true, NONE are running it after too many glitches, problems, crashes.
pity, my rig is geared for dx11