Hull Rupture Lag at Lvl 40: Wave 40 Slowdown Explained

When people search for Hull Rupture lag at lvl 40 they mean wave 40, not character level. There are no levels in this game — the ship has a wave counter, and somewhere past forty the run starts crawling while your hardware sits half idle.

The cause is not your graphics card. The developer has said outright that the slowdowns after wave 40 come from Endless Mode scaling, and that they missed the mark with its balance.

First, lvl 40 means wave 40

Hull Rupture has no levelling system. What it has is a twenty-wave Classic Mode and an Endless Mode that continues past it, so a player who says "lvl 40" is describing how far the counter has gone, not how strong the ship is.

That distinction matters, because the twenty-wave target and the forty-wave experience are different modes with different tuning. Classic ends at twenty. Anything past that is Endless, and Endless is the part with the scaling problem.

What the developer actually said

The statement came with the demo patch on 25 September, and it is unusually direct: they did not expect so many players to get that far, and they had missed the balance of Endless Mode again.

The same post explained the plan for release. Endless would become a separate mode with its own settings, so it could be balanced and optimised on its own rather than as an extension of Classic.

That is a design fix, not a performance patch. Splitting the mode gives them somewhere to tune the scaling; it does not by itself guarantee that wave forty-five runs smoothly.

Three different problems behind the word "lag"

The developer sorts performance complaints into three buckets, and they do not share a cause or a fix.

The first is bugs that cause frame drops. These get found and fixed gradually, and they tend to announce themselves at a specific action — a breach, a purchase, placing a module.

The second is the slowdown past wave 40, which the developer attributes to Endless Mode scaling rather than to rendering. This is the one people mean when they search for lvl 40.

The third is general performance before wave 40, which the developer keeps separate from the other two rather than folded into them. If your frame rate is poor from wave three, you are not in the wave-40 bucket at all.

Why it gets worse the longer a run goes

Nothing in this game pauses. Production keeps running during combat, workers keep moving, and aliens keep pathing through a layout you built, so every minute past wave 40 adds entities to several systems at once.

More modules means more power draw and more production to simulate. More workers means more assignments. More defenders and more attackers means more projectiles, and projectiles are usually where a tower defence frame budget goes.

None of that requires a memory leak or a bad driver to explain. It is the ordinary cost of a run that has grown, multiplied by a mode whose scaling was, by the developer's own account, mistuned.

Is it your PC?

The minimum specification is genuinely low: Windows 10 21H1 or newer, an i7-8700 or Ryzen 1600, 8 GB of RAM, a GTX 670 or HD 7970, DirectX 11 and 2 GB of storage. macOS needs Big Sur 11 or newer, Linux needs Ubuntu 22.04 or newer, and both want the same 8 GB.

If your machine clears that comfortably and the drop appears exactly when the counter passes forty, the timing is pointing at the run rather than at the hardware. If instead you get stutter from the first waves, or in menus, that is the bug bucket and worth reporting.

What actually helps

Treat any settings checklist promising a smooth late Endless as a guess. The slowdown is attributed to mode scaling, so no combination of shadow quality and driver versions is addressing the thing that changed.

What you can do is remove the avoidable load. A ship with fewer redundant modules and fewer idle workers has less to simulate, which is the same advice as building efficiently for its own sake rather than as a workaround.

Graphics settings sit on the other side of that line. Lowering shadows or resolution changes what gets drawn, while the cost you have run into comes from how much the game has to update — modules, workers, projectiles. Turning everything to low is a reasonable thing to try, but it is not the lever this particular problem responds to.

Reporting is worth the two minutes. The useful report names the wave, the mode, what the ship was doing at the time and which build you are on — the difference between "laggy at 40" and "drops to single digits when the third breach opens at wave 43" is the difference between a report they can use and one they cannot.

Crashes, not just slowdowns

Some players report worse than stutter. One demo review describes runs crashing around wave 36 or 37 when the layout was inefficient, and still getting heavy slowdown past forty when it was not.

Treat that as a place to look rather than a rule, since one run crashing is not the same as every run crashing. If your runs die at a repeatable wave rather than degrading gradually, note the wave and the ship state — a repeatable crash is far more useful to the developer than a general complaint about performance.

The same logic applies to the ship itself. A layout that keeps every corridor short and every module busy is doing less work per second than one with long empty routes and half the workforce idle at the airlock, so a crash that only happens on your biggest ship is telling you which of the two you built.

What this means for your next run

Expect Classic, the twenty waves the game is built around, to behave. Expect Endless to be the mode where the ship outgrows the simulation, at least until the separate tuning has had a patch or two behind it.

If you are chasing the late waves for their own sake, the first twenty waves is the part that decides whether you get there with a ship worth continuing, and the systems reference explains which modules are costing you the most simulation for the least output.