login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Help us translate Steam
though it only reset some settings (graphics, fov and shake on land changes in .ini)
I made a tool that you can run over your config files and patch the timestamps inside them to match whatever UE3 expects them to be based on its broken daylight saving code.
If you don't have a backup of your config, it's too late though.
https://github.com/ToxikkModdingTeam/ToxikkConfigTool/releases/tag/v1.0
Note: this daylight saving issue is unrelated to the config resets that happen when updates are released.
It's a bug in UE3 that causes timestamp calculations to be -1/0/+1 hours off depending on the current DST (summer or winter time), windows system setting to automatically adjust the clock to DST and whether the last write time of the Default *.ini files falls into DST.
UDK *.ini files contain a section named [IniVersion] with such timestamps and if they don't match what UE3 calculates during startup, it regenerates/overwrites the UDK *.ini files based on Default *.ini files
Caveat is, if additional settings are introduced in the update, you need to be mindful of them and integrate them into your settings or you might find the update behaving erratically.
Predathors tool is now integrated into the launcher and will repair the config files automatically.
So the DST fix is now live!
Theoretically you'd have to do a 3-way merge between old Default .ini, new Default .ini and the user's customized UDK .ini - and handle possible conflicts.
The problem is that TOXIKK doesn't have full control over this process. The update is done by the Steam client, the Default -> UDK .ini file generator is part of the UDK/UE3 .exe and executes before the TOXIKK game code can do anything. The game code can't tell if a setting is missing or if it intentionally has a value of 0 or an empty text.
I'm also mad about the config resets that come with updates, but I know there is no any easy fix for it. It's how Steam and UE3 work by default and any solution requires a significant amount of work.
Those are caused by a bug in UE3 and the fix patches the timestamps inside the UDK * ini files to match whatever the broken UE3 code expects.
Config resets after updates happen when developers had to add or modify game configuration settings. UE3 can't handle individual settings, it only deals with whole files. If a Default * ini file is newer than the timestamps inside the (user) customized UDK * ini file, the user's files will get overwritten with the Default file to make sure it includes all the settings that the devs need in there.
Also use https://docs.unrealengine.com/udk/Three/PackagesAndNetworking.html#Conformed%20Packages and updates will be trouble-free. No issues with outdated servers, version mismatch, broken replays etc.
Than make the updates more frequent without worrying about updating all the servers or players losing their settings. Just DON'T wait several weeks to push ready-to-ship changes as e.g. the skins promised to the most loyal customers... seems like they are being trolled for buying early access. :/ - Make "no ♥♥♥♥♥♥♥♥" great again. :D