Can you modify Config files, and would it be considered cheating?

[SnoW]

Hi,
I've stopped playing Depth recently as the performance of the game has gone steadily down hill.... i'm getting really choppy frame rates and stutter... it's more of a nuisance to play than the good ol game i remember. (it used to not have the performance/optimization issues as bad)

So, i stumbled across a post about a different game on the Unreal3 game engine.
The author suggested some config adjustments that turned XCOM2 from a slideshow of pain into a buttery smooth, well performing game.
He/She stated that the fix would work on pretty much all games on the unreal3 engine.

Firstly i'd like to double check Depth is indeed on the Unreal3 engine?
Has anyone tried modding the config files with any success?

The changes to the config (which work for most U3 games) are as follows:
________________________________________________________________
"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)

The instructions were to change the engine.ini using a text editor then save it and tick 'read only' in preferences.

It'd be amazing if it worked for Depth,

[Mr. n]

0. I have absolutely no idea if this would warrant a ban or breaks Steam TOS or EULA. Wait for a developer to tell you if this breaks Depth's TOS/EULA and in the meantime you might want to peruse the Steam ones.
1. It kinda is modifying files, but not in a nefarious way... unless it turns off textures and leaves them on for sharks or something similarily advantageous.
2. Usually editing .ini's so the game can run smoother is not called cheating. In many games this has become a sport by itself ("Let's see who can make the game look even worse, but pump out more FPS").
3. "MaxSmoothedFrameRate=400" - this looks like a joke, IF you are going through with it and modifying the files, set it at your monitor's refresh frequency +5 at maximum. If your computer cannot do this many fps, consider putting it on lower - experiment how much can you get with the other settings and then set it at +5 from max what you can get, so that game won't cut you frames if it could give you more.

[Seraph]

VAC is dangerous when it comes to any client modification/third-party software having ANY effect on the game, so I wouldn't risk it. The devs could tell you more, but they probably don't know the details of how VAC works and Valve can change how/what it looks for at any time they want.

I think some people got VAC'd for using some tweak or program to add post processing to games.

But I've personally tweaked .inis while modding Bethesda games or in games where the actual options menu wouldn't save resolution and so on, so it SHOULD be safe. But don't take my word for it, because VAC has surprised some people already.

[wirs]

It's 100% safe. You can only get a VAC ban if you edit or modify game core files but not for editing config files.

[SnoW]

Alright, i may give it a go.. i'll let you know if i see good improvement.
The particular config i've listed above is supposed to be more about optimization for PCs over Consoles then straight up nerfing the graphics.
I hope it works as Depth is in a poor state for me performance wise at the moment.

[Mr. n]

I don't think VAC can reliably ban people for modification of non-executable files. People woudl get banned for configuration issues (many other games use VAC and custom configs with weird things inside are used every day for HL2 and CS), HDD errors, etc.

The methods of adding post processing I know used code injection - this is not a thing you want to do (because it's used for cheating as well and nobody's going to check what exactly you were doing, a ban is cheaper).

If you feel like experimenting, what I would suggest is to make a new account, buy the game on a sale and smurf it. Do not risk your main account, ever.

[Ray G.]

Try sending e-mail to [e-mail]

[Mr. n]

Digitalconfectioners themselves won't know how VAC works for certain. While they may tell you that this doesn't breach their ToS/EULA, VAC is still a mystery, made this way for security-via-obscurity (most security via obscurity systems are this way because "cheaters would do 'borderline' cheats, just under the ban threshold" - which I find garbage. Making the variables hidden doesn't make it more secure.).

[DefectiveByDesign]

One of the biggest UE3 tweaks is using dx10 and OpenAL for sound. DX9 doesn't support crossfire on AMD, and OpenAL gives you much better positional audio. Of course, both options are non-functional in Depth.

If anyone figures out some good config tweaks that work, please post them, but the best ones have been disabled by the devs, and it doesn't sound like they are interested in making the game better by supporting better options.

[Serius_Sim]

I was wondering the same thing. I use a tweaked config file on Tribes Ascend for super low graphics, it drasticaly improves visibility (example below), and Depth is based on the same engine.

http://steamcommunity.com/sharedfiles/filedetails/?id=1179992262

[Mr. n]

How did it go, Snow man?

[Landon Keyser]

Play windowed. Turn off gore. Did the trick for me as far as running better.

[Willis the Illest]

Originally posted by Kane Reynolds:

Play windowed. Turn off gore. Did the trick for me as far as running better.

Also turning off all surrounding wildlife helps.

[DefectiveByDesign]

textures high, shadows and light medium, light shaft off, silhouetee medium, blur distortion ambient 1&2 off, world medium. Good enough for 1440p 70-100-ish fps. You don't have to compromise detail for performance, just the unnecessary junk is good enough.

Vsync also disable, or use adaptive, because every frame below refresh drops total fps to half. 59 fps = 30 fps when vsync is on.

[Mr. n]

You mean 70-100-ish FPS @ 1440p for your machine. If memory serves correctly, Snow man did say somewhere that he's playing on a low-end machine.

Also, blur distortion is unnecessary, degrades the performance and does give a disadvantage, I suggest keeping it off in every game.

One more thing - I found out the hard way that if you disable Silhouette high quality shaders then seals' silhouettes become practically invisible. You might want to keep this checkbox filled (it's different than "silhouette quality" - this one can be set to anything).

[SnoW]

Heheh yeah high quality silhouettes are essential. Unless you need a need a nerf ;)

Sorry, I'm not going to be able to test out my plan.
I've had a few changes in my life lately and had to sell my gpu to afford furniture in my new yard.

I also found out upon taking my comp to the shop that my Windows was corrupted. Which might explain my poor performance lately.
--

I'll be taking 6 months to a year out o gaming, so it's been a lot of fun. Wish you all well. Snow.