*IMPORTANT* REAL Stutter Fix (PIN THIS) (requested again)

[UNKN0WN]

COPY PASTED FROM A OLD THREAD.
https://steamcommunity.com/app/200510/discussions/0/846960628563773260

First off, I rarely post anything, but after reading about this in UE3 based games over and over again and having a unique knowledge of the unreal engine (I've playtested games based on all of them) I could sit idle no more.

Ok, so you have read countless drobes of stuff on how to fix stutter or hitching or frame lag or whatever you want to call it, and you really can't find something that "works" period. Search no more, you have found IT.

READ COMPLETELY

This guide will not feature technical explanations as to why the settings work. It is writ for the everyday gamer. It is important to note that the UE3 engine was designed with consoles in mind and needs to be optimized for PC use. YOU MUST INCLUDE ALL CHANGES. Do not attempt unless you have a decent knowledge of what you are doing(and how to undo it). This will not effect the ablilty to play online and does not fall outside the guidelines of VAC.

And yes you may have seen some of these settings and tried some of them but they MUST all be done together for this to work properly because many settings affect the timing of other settings since this is a streaming based engine. TRY IT this way 1st. plz. give it a chance.

This WILL NOT fix choppy bink video playback as that is plugin based and not engine based. That is a different animal altogether (its very poorly coded for multi-core cpus)

THIS FIX WORKS FOR ALL UE3 BASED GAMES.(well tested)

I need to take a moment to explain that this will fix the kind of stutter that you get even on med to high-end hardware commonly called load/frame hitching. This is where your getting great Frames Per Sec (as reported by fraps or afterburner) but it "looks" choppy. Poor performace (I.E. running a game at settings you know your HW can't run well) will not see a serious decrease in hitching, though it will still help a fair bit. You can really tell the difference if you run with vsync ON and compare BEFORE FIX/AFTER FIX smoothness. It is very, very obvious. Anyhow....

ALL GAMES MUST HAVE COMPLETED FIRST RUN. (1 startup then exit)

1st Goto \ users \ yournamehere \ documents \ my games \ gamename \ ...... \ config.
(Note: EA games sometimes use "EA Games" instead of My Games)
Make a Backup of the "engine" ini file just in case you need it.

2nd Open the "engine" ini file in notepad (or your text ed of choice) Find and change the following lines ( just use ctrl-f ) taking care to match the settings to your system where noted. Also some of these settings you may not have to change IF they already match what is given.

Here they are: (REMEMBER, READ CAREFULLY, MATCH EXACTLY)
"*"=setting
"bUseTextureStreaming=True" (these are default for most but not all UE3 games)
"bUseBackgroundLevelStreaming=True"
"MipFadeInSpeed0=0" (these even out mipmap loads and draw time)
"MipFadeOutSpeed0=0"
"MipFadeInSpeed1=0"
"MipFadeOutSpeed1=0"
"PhysXGpuHeapSize=64" (these balance physx calls even on cpu based physx titles)
"PhysXMeshCacheSize=16"
"bSmoothFrameRate=TRUE" (this really does need to be on, ignore what you've read)
"MinSmoothedFrameRate=30" (keep these right here. setting higher/lower does no good)
"MaxSmoothedFrameRate=400"
"bInitializeShadersOnDemand=True" (reduces overall shader batch call size)
"DisableATITextureFilterOptimizationChecks=False" (driver based opt is MUCH faster)
"UseMinimalNVIDIADriverShaderOptimization=False" (same here)
"PoolSize=256" or (vidmem/poolsize exmpl: 512/128, 1024/256, etc, DO NOT exceed 768)
"bAllowMultiThreadedShaderCompile=True" (should already be on by default)
"ThreadedShaderCompileThreshold=4" (formulate like this: # of cpu-cores (not threads) -2)
"OnlyStreamInTextures=True" (reduces overall texture batch call size)

Check for multiple instances of these settings within this file as some games have them listed twice and you must change both (I.E Xcom:Enemy Unkown)

Now save the file, then right click it, choose properties and then set it to "read-only".
Launch your game, choose reset to defaults under that games graphics settings, then set them up how you want. These settings get saved to your profile file for that game and use the engine ini as a base. They are not saved to the ini file therefore it wont matter that it is read-only. However there are a few rare exceptions (SEE NOTE BELOW)

THAT'S IT.

All other settings in the file should be left at there defaults
(Yes, even "SizeOfPermanentObjectPool". FYI This can hurt performance if set different from defaults because it can actually increase frame call time if set incorrectly)

All changes asume that you have steam cloud sync on. If not, changes you make may be overwritten if you turn on cloudsync after the fact and may need to be re-done.

(SPECIAL NOTE) Some UE based game like BatmanAA or AC need to be configured how you want it 1st THEN do the fix minus the reset defaults part. You will also need to modify the "userengine" ini file in the same folder as the one above to match any relevent settings.

If you have done everything correctly YOU WILL NOTICE IT. Unlike other "fixes" the performance of this one will be VERY obvious, Especially for ATI/AMD owners. In fact the title screen loading for Dishonored is a dead giveaway (which is why I put this in here)

[Cesare]

This is tweaking the engine = tuning down the graphics, you can't fix a real problem like this with an old tweak

[sheep from hell]

Originally posted by Cesare:

This is tweaking the engine = tuning down the graphics, you can't fix a real problem like this with an old tweak

to be fair, it works without a visible downgrade......not like the official patch. some of the tweaks are even not a downgrade and just more optimized settings

[Urah]

This works

Period.

[UNKN0WN]

happy to be of service :)

[Urah]

Originally posted by UNKN0WN:

happy to be of service :)

More than that!

You turned a game about to be uninstalled into a pure joy.

[drake_hound]

steam cloud sync on how can this improve the game performance lol
When playing offline you suffer the least amount of lag and hassle !

Cause no info to be sent or recieved.
Sorry by default my steam cloud is off always.

[JacKV64]

Sorry for the necrobump but i really need to know something.

In the "ThreadedShaderCompileThreshold=X" let's say my FX6300 has 3 real cores and then we apply the "-2" so the result should be "ThreadedShaderCompileThreshold=1" right?

I'm not entirely sure, can someone help me?

[Dragon32]

Originally posted by JacK V16:

Sorry for the necrobump but i really need to know something.

In the "ThreadedShaderCompileThreshold=X" let's say my FX6300 has 3 real cores and then we apply the "-2" so the result should be "ThreadedShaderCompileThreshold=1" right?

I'm not entirely sure, can someone help me?

Yes, and 1 is the default value. Another guide says to set that value to the number of cores your CPU has, so 3 in your case.

[Urah]

Originally posted by JacK V16:

Sorry for the necrobump but i really need to know something.

In the "ThreadedShaderCompileThreshold=X" let's say my FX6300 has 3 real cores and then we apply the "-2" so the result should be "ThreadedShaderCompileThreshold=1" right?

I'm not entirely sure, can someone help me?

I had crashes by not putting it right. I have an Intel Core Duo and I put a higher value than 1.
Now with 1 applied the game barely crashes.

[SenMithrarin85]

One thing not mentioned here, is setting "fogvolumes" to false. It helps A LOT.

It seems the fog of war uses volumetric rendering and it really hit the performance hard on some maps.

[JacKV64]

Really thanks everyone. Now the game for the most part is buttersmoth, only stutters a bit on the ranger (it's just loading the level).

This should be pinned and i encourage everyone to try it.

[Mr. Nice]

Originally posted by SenMithrarin85:

One thing not mentioned here, is setting "fogvolumes" to false. It helps A LOT.

It seems the fog of war uses volumetric rendering and it really hit the performance hard on some maps.

Well to be fair, the tweaks mentioned in the opening are standard UE3 engine tweaks with zero quality imact (it's all just texture streaming, cache sizes and threading tweaks). fogvolumes is xcom specific, and does impact PQ.

[Urah]

Originally posted by JacK V16:

Really thanks everyone. Now the game for the most part is buttersmoth, only stutters a bit on the ranger (it's just loading the level).

This should be pinned and i encourage everyone to try it.

Yes this should be sticked.
Nice that game runs better ;)

[Armored Baron]

Can't find "OnlyStreamInTextures=" in KF2's engine file, using Notepad++.

However it's there in RO2's engine file, which is weird.

[DeBlue]

My Alternative Mod Launcher for XCom 2 refuses to start the game because it can't get acsess to this very ini file. If I take away Read-Only I fear that all the changes would reset...