Start with the documented performance fixes

If a huge battle or the final level slows down, check whether your game includes version 1.1.0. The developer documented improvements to very large battles and the battle interface, plus a fix for the final level slowing down and consuming increasing memory as the fight continued. For a Here Comes the Horde performance lag fix, those game-specific changes are a better starting point than settings advice written for another horde game.

The official 1.1.0 performance and bug-fix notes identify several distinct changes:

Symptom or areaDocumented change
Very large battlesPerformance improvements
Interface during battlesInterface performance improvements
Final level becoming slower over timeFix for slowdown and increasing memory use as the battle lasts
Game failing to start on some older graphics cardsA separate startup fix

These are the developer's reported fixes, not a benchmark measured for this guide. They do not establish a particular frame rate or guarantee that every machine's remaining lag has the same cause.

Enable the official performance log

Version 1.1.0 added a troubleshooting log enabled with this launch option:

--performance-log

Use the option exactly as written when you need to gather information about a remaining performance problem. The announcement presents it as a diagnostic tool, not an option that automatically boosts frame rate.

For useful notes alongside a reproduction, record which level you played, whether slowdown grew over the duration of the battle, and whether the interface or the whole fight felt affected. Note your installed version as well. Those observations help describe whether your experience resembles the documented final-level issue or a different symptom.

The announcement does not give a log-file path, describe every field in its output, or provide a guaranteed diagnosis from the flag alone. This guide therefore does not invent a folder to search or claim that enabling logging resolves the underlying problem.

Separate performance symptoms from other fixes

The same update fixed a talent tree disappearing after being dragged off-screen, saving on Linux with Proton, and an error when moving the game window to another monitor. Those are separate reported bugs. A saving problem or missing talent tree does not by itself demonstrate the cause of a low frame rate.

The notes also mention a corpse cap, but the printed number is ambiguous. There is no reason to turn that into an invented graphics-setting value or an instruction to edit a configuration file. No such edit is established by the collected official material.

This guide covers the official fixes and diagnostic option available in the material collected on November 19, 2026. It supplies neither a tested graphics preset nor universal driver, registry, mod, or hardware changes. If slowdown persists, preserve the version and reproduction details rather than assuming the patch announcement has diagnosed your individual system.

FAQ

Did the developer fix the final level slowing down?

Version 1.1.0 specifically reports a fix for the last level slowing down and using more memory the longer the battle lasts. That is the documented issue; it is not a guarantee against every later performance problem.

Does --performance-log improve FPS?

The developer describes it as a troubleshooting log option. The announcement does not claim an FPS increase from enabling it.

Where is the performance log saved?

The collected announcement does not specify its location. This guide does not provide an unverified path or promise a particular filename.