Troubleshooting

• Wrong folder depth. The game needs Mods\LateGamePerformance\version-1.1\manifest.json. A doubled LateGamePerformance\LateGamePerformance folder is the usual mistake. See the folder layout.
• Wrong Mods folder. It must be the folder your other mods are in, normally Documents\Timberborn\Mods.
• Old game. The mod needs Timberborn 1.1.2.4 or newer.
• Fully quit and restart the game after copying files.

Late Game Performance needs Harmony (2.4.1 or newer) and Mod Settings, both from the Steam Workshop. Subscribe to Harmony and Mod Settings, enable them in the Mods menu, and restart.

• Make sure you're reading the right session. The log is overwritten each launch, and the previous one is Player-prev.log.
• Check the mod list near the top of the log. If Late Game Performance isn't there, it wasn't enabled, or you didn't restart after enabling it.
• If it's listed but the loading. line is missing, look further down for an error loading the mod, and report it with the log.

1. Use the latest release. Version 0.4.3 crashes the game while loading, so replace it.
2. Still crashing on 0.4.31? Try the game once with only Harmony, Mod Settings and this mod enabled.
3. Report it with Player.log.

Something the feature needs is missing or changed in the game, usually after a game update. The feature didn't start, and this computer runs the game's own code for that part. The lines just above say which part failed.

• HaulCache or YielderSearch OFF: only the speed-up is lost. Both give the game's own results, so the simulation is the same.
• RouteMaps or TerrainSearch OFF on one computer: in multiplayer, that computer can pick a different route from the others. Check that every player has the same game and mod version, then compare everyone's startup line.
• Either way, report it with the log, so it can be fixed for that game version.

The feature hit an unexpected error and switched itself off for the rest of the session. The game's own code runs instead, and a dialog says so.

1. Single player: play on. Nothing is lost but speed.
2. Multiplayer: every player quits and restarts the game before playing on together. The feature is back after a restart.
3. Report it with the whole line, including the error text after it. In multiplayer, include everyone's log.

• It targets large colonies. A small one has little repeated work to remove.
• Check the Timing: line (what it shows). If everything else takes most of the main thread's time, that is mostly rendering and Unity itself, which this mod can't speed up. A frame-rate cap then gives the simulation more of each second.
• Freezes of most of a second, about once a minute? Tick Incremental garbage collection, restart, and check the startup line says GC: incremental=True.

• You haven't ticked it. Tick Incremental garbage collection in the mod's settings (how).
• You ticked it but haven't restarted. It takes effect the next time the game starts.
• The file couldn't be written. The log has a line starting GC: could not change or GC: … was not found. Close the game and add the line gc-max-time-slice=3 to Timberborn_Data\boot.config in the game's install folder by hand.
• A game update or Steam's file check restored the original file. If the box is ticked, the mod adds the line again at the next start and logs Putting it back. Restart once more.

It says incremental collection is off and offers Turn it on or Not now. It asks only once. To turn it on later, tick Incremental garbage collection in the mod's settings (how).

Your LateGamePerformance.cfg is from an older version and has one of the keys HaulCache, HaulCacheFlushEveryTicks, RouteMaps or YielderSearch. It is ignored and harmless: those features are always on, the same for everyone. You can delete the line.

• The verify settings (the Verify … boxes and the …Verify keys) run the game's own code as well, so they are slower than no mod. Untick the boxes, or set the keys back to false.
• RecordTimings = true makes the game run a little slower. Set it back to false after a profiling session.
• The Diagnostics timers box (Diagnostics = true) adds a little overhead. Untick it after collecting numbers.

• Every player must run the same version of the mod and the same game version. Nothing else has to match (why).
• Each player's Simulation features: line should read the same. If one says OFF, see above.
• If games go out of step (a desync), keep every player's Player.log and report it with each player's mod list. Say whether it also happens without this mod.