TKGRAPHICSSETTINGS.MXML Not being Used

[jiberish001]

Ever since the Beyond update, my game no longer uses the TKGRAPHICSSETTINGS.MXML file. Changing it does nothing to ingame settings, and the ingame setting does nothing to change the file.

What default file is being used? Where can I find it? Or how can I make it use the TKGRAPHICSSETTINGS.MXML file?

[Astasia]

It is definitely being used, I was just messing around with it earlier. Make sure you are looking at the right version of the file and aren't for example looking at the one in an old install location you don't use anymore.

[ChromePlate]

some games have files in more then one location in windows, so perhaps you are looking at the wrong file?
But with this game who knows.

[jiberish001]

I think I figured it out.... I was not mistaken about the file (no other file of its kind exists), but I was mistaken about its usage.

This is my current settings...

<?xml version="1.0" encoding="utf-8"?>
<Data template="TkGraphicsSettings">
<Property name="Version" value="4" />
<Property name="FullScreen" value="false" />
<Property name="Borderless" value="true" />
<Property name="Monitor" value="0" />
<Property name="MonitorNames">
<Property name="MonitorNames_00" value="0|NVIDIA GeForce GTX 1080|Generic PnP Monitor" />
</Property>
<Property name="UseScreenResolution" value="false" />
<Property name="ResolutionWidth" value="2560" />
<Property name="ResolutionHeight" value="1440" />
<Property name="VsyncEx" value="Off" />
<Property name="GSync" value="true" />
<Property name="ShadowDetail" value="Low" />
<Property name="TextureDetail" value="High" />
<Property name="GenerationDetail" value="High" />
<Property name="ReflectionsQuality" value="Low" />
<Property name="AntiAliasingEx2" value="TAA" />
<Property name="MotionBlurQuality" value="Off" />
<Property name="MotionBlurStrength" value="0.000000" />
<Property name="AnisotropyLevel" value="4" />
<Property name="FoVOnFoot" value="100.000000" />
<Property name="FoVInShip" value="100.000000" />
<Property name="Brightness" value="50" />
<Property name="MaxframeRate" value="144" />
<Property name="NumHighThreads" value="4" />
<Property name="NumLowThreads" value="3" />
<Property name="TextureStreamingEx" value="Off" />
<Property name="TexturePageSizeKb" value="128" />
<Property name="ShowRequirementsWarnings" value="true" />
<Property name="RemoveBaseBuildingRestrictions" value="true" />
<Property name="BaseBuildingLimit" value="5000" />
<Property name="MouseClickSpeedMultiplier" value="0.000000" />
<Property name="AmbientOcclusion" value="Off" />
<Property name="UseHDR" value="false" />
<Property name="UseLightshafts" value="false" />
<Property name="TerrainQualityEx" value="High" />
<Property name="UseTerrainTextureCache" value="false" />
<Property name="UseArbSparseTexture" value="false" />
<Property name="EnableTessellation" value="True" />
<Property name="GraphicsDetail" value="TkGraphicsDetailPreset.xml">
<Property name="TextureQuality" value="TkGraphicsDetailTypes.xml">
<Property name="GraphicDetail" value="Ultra" />
</Property>
<Property name="AnimationQuality" value="TkGraphicsDetailTypes.xml">
<Property name="GraphicDetail" value="Ultra" />
</Property>
<Property name="ShadowQuality" value="TkGraphicsDetailTypes.xml" />
<Property name="PostProcessingEffects" value="TkGraphicsDetailTypes.xml">
<Property name="GraphicDetail" value="Ultra" />
</Property>
<Property name="VolumetricsQuality" value="TkGraphicsDetailTypes.xml" />
<Property name="TerrainTessellation" value="TkGraphicsDetailTypes.xml" />
<Property name="PlanetQuality" value="TkGraphicsDetailTypes.xml">
<Property name="GraphicDetail" value="Ultra" />
</Property>
<Property name="BaseQuality" value="TkGraphicsDetailTypes.xml">
<Property name="GraphicDetail" value="Ultra" />
</Property>
</Property>
<Property name="VignetteAndScanlines" value="false" />
<Property name="TextureStreamingVk" value="Off" />
<Property name="HDRMode" value="Off" />
<Property name="AdapterName" value="GeForce GTX 1080" />
<Property name="AdapterIndex" value="0" />
<Property name="NumGraphicsThreadsBeta" value="0" />
</Data>


I do believe there is some compatibility issue with the new ingame graphic options, which are represented by the bottom half of this settings file. Some of them seem to be missing values in the file even when set ingame, and in that case I believe the older settings above are used. The others seem to overwrite the older above settings, such that if you change the above settings just in the file, they are just replaced by the newer ones below that have values, which you've set ingame. Some of the older above settings also seem to be non-responsive, such as the old setting that allowed you to change the hold duration of the confirmation button, effectively making it an instant click. I believe the new ingame option for this has broken the older setting that is still in the file. At least; even when I have it set to 0.00000 duration it does not act as such, and instead uses the game's default duration.

I think they did a half-ass job of just bandaging the old settings with the newer graphic options, and they don't play way together in some cases.

[jiberish001]

AhHA! I was on to something. I was messing around for FPS optimization, and when looking through the settings file I lost sight of the newer Anisotropy level setting. I swore that I had seen an older AND a newer version of the setting in the file, but when I was attempting to change it from level 4 to 8 I could not find the newer setting on the bottom. So I set the older Anisotropy level above to 8, went into my game, and noticed that it was still on 4. So I changed it to 8 ingame, then exited and checked the file. Sure enough the newer Anisotropy level reappeared on the bottom, between <Property name="GraphicDetail" and <Property name="VignetteAndScanlines".

It would seem that this new graphics options band aid only kicks in when the older settings are set to certain levels, and when they are not set to those levels the file is altered to show a blank place where that newer setting would be. Now I'm left wondering what all those other blank property values would be if they were set right in the older options, and whether or not I'm missing out not knowing. :(

[Astasia]

Often games wont define something in a config file if it's on the default setting, as there's no reason to set a value to something that's not being changed. If you are worried about old settings and new settings possibly being duplicated or bloating the file, just delete the file and the game will probably create a new one with only the values it's supposed to have.

[General Woundwort]

I'm seeing changed between Next and Beyond but I'm unsure if they actually go in TKGRAPHICSETTINGS. Anyway, here's a list of what I've got. It's not comprehensive.


Old, no longer used

AntiAliasingEx2
Frame Rate
GSync
GenerationDetail
MotionBlurQuality
ReflectionsQuality
ShadowDetail
TerrainQuality,
TerrainDetail
UseLightshafts

New, presumably used

AnimationQuality
AnisotropyLevel
AntiAliasing
BaseQuality
MaxFrameRate
MinGPUMode
PlanetQuality
PostProcessingEffects
ReflectionsMultiplier
ShadowQuality
TerrainTessellation
TextureQuality
VignetteAndScanlines
VolumetricsQuality


Note that these were entered by hand so the spelling might be off. Also a bunch of the new settings are held under a node named GraphicsDetail, so pay attention there.

MouseClickSpeedMultiplier still looks like it's 'there'. Maybe it's not being used? I dunno.

[^^o^^ BatCat]

Originally posted by jiberish001:

<Property name="FullScreen" value="false" />
<Property name="Borderless" value="true" />

Fail.. reverse these two for performance boost.

....or you have something else going on, not mentioned.

[jiberish001]

Originally posted by ^^o^^ BatCat:

Originally posted by jiberish001:

<Property name="FullScreen" value="false" />
<Property name="Borderless" value="true" />

Fail.. reverse these two for performance boost.

....or you have something else going on, not mentioned.

That boost is not universally guaranteed. It helps for some, but not for everyone. In my case there is no difference between playing fullscreen or playing borderless.

[jiberish001]

The mouse click speed setting is still working it seems, but now it cannot be made instant. Only near instant. Probably having to do with the new setting taking over that role. I've tried both the new and the old way of instant confirmation, but neither of them work to REALLY make all confirmations instant. Only some select few things are instant. For mostly everything else you still have to wait the default duration, no matter what your settings. :( I will need to find a mod or cheat to fix such a simple QoL issue.

Changing these old settings in the file still works for me...
My Frame rate setting still works
My GSync setting still works
My Motion blur setting still works

The other graphical old settings only work when the ingame (or newer settings are set low enough for the older ones to 'kick in'

[OZFugazi]

hi

when you updated to beyond, the "new" tkgraphics were merged with the old tkgraphics. in other words, the older pre beyond tkgraphics was not completely deleted then replaced with the new.

there are values that the game no longer uses in the values you listed. (gsync, texture page file, ect)

simply completely delete the tkgraphics file and have the game re build it. make a copy of it of course before you do. this will rebuild the current beyond tkgraphics file and then all you have to do is edit what applies from your old (pre beyond) settings.. either through in game or hard edit.


all the best.

[jiberish001]

New file was created with no unwanted affects. Thankfully none of the old removed settings were unique or needed. This was dumb. How does such a massive update go about simply merging an important file rather than replacing the file? =/

[^^o^^ BatCat]

Originally posted by jiberish001:

Originally posted by ^^o^^ BatCat:

Fail.. reverse these two for performance boost.

....or you have something else going on, not mentioned.

That boost is not universally guaranteed. It helps for some, but not for everyone. In my case there is no difference between playing fullscreen or playing borderless.

It is guaranteed, just small on serious top end systems.
But then you do have something else going on.

[Chronverge]

I've also tinkered around with the file and noticed that if you should edit the file manually, it will carry over to the game, but any further changes applied then in-game take no effect.

Another thing I noticed were the in-game FXAA levels. They seem very low. Possibly only as low as 2x or so. At 1080p TAA+FXAA is very blurry. But with only TAA in-game and FXAA x8 (app enhanced) through Nvidia control panel, visuals are now exremely crisp. And the horrid FXAA blur is also gone for some reason.

Best seems to only edit the in-game GFX values to your liking, then make further changes to the file afterwards. Like tweaking FOV or high/low thread values. Though I have not seem much improvement with the latter, as I'm currently trying to improve terrain loading speed.

I have a 6c/12t CPU @ 4Ghz
GTX 1080

By default my game set this to:
<Property name="NumHighThreads" value="3" />
<Property name="NumLowThreads" value="6" />

I upped this to 4/8 and even 5/10 but saw no improvement in terrain generation. Same for 6/6. No difference what so ever. Grass and such still load in maybe 2-3 seconds. Especially if I am using the jetpack to get around faster.

Maybe someone else has some better insight?

[^^o^^ BatCat]

Originally posted by Chronverge:

I've also tinkered around with the file and noticed that if you should edit the file manually, it will carry over to the game, but any further changes applied then in-game take no effect.

Another thing I noticed were the in-game FXAA levels. They seem very low. Possibly only as low as 2x or so. At 1080p TAA+FXAA is very blurry. But with only TAA in-game and FXAA x8 (app enhanced) through Nvidia control panel, visuals are now exremely crisp. And the horrid FXAA blur is also gone for some reason.

Best seems to only edit the in-game GFX values to your liking, then make further changes to the file afterwards. Like tweaking FOV or high/low thread values. Though I have not seem much improvement with the latter, as I'm currently trying to improve terrain loading speed.

I have a 6c/12t CPU @ 4Ghz
GTX 1080

By default my game set this to:
<Property name="NumHighThreads" value="3" />
<Property name="NumLowThreads" value="6" />

I upped this to 4/8 and even 5/10 but saw no improvement in terrain generation. Same for 6/6. No difference what so ever. Grass and such still load in maybe 2-3 seconds. Especially if I am using the jetpack to get around faster.

Maybe someone else has some better insight?

Very good..

I fear its the procedural nature of the world and contents. The huge amount of calculations across everything is what is holds even the most powerful of systems back. Lots of tricks are used to short cut and cache alot of it.
You can see some of that if your screen is not scaled to 16:9, outside of this, critters move but are not animated, etc.

OpenCL would be of some use, but we have no control over that.

You not mention try'n 12/0....

[Chronverge]

Oh no, I'm pretty sure that will crash the game and at this stage I'm just glad the game runs so well for me.