Home / Performance / Wave 40
The query says level 40. The studio said wave 40.
Hull Rupture lag at wave 40
People search for lag at level 40. The studio's 25 Sep 2026 note talks about slowdowns after wave 40, and it blamed Endless balance, not a numbered character level.
That note is from the demo period. Endless became its own mode at launch so it could be balanced and optimized on its own. I have not found a public 1.0 test that repeats the wave 40 drop.
Known and unknown
| Point | Status | Sources |
|---|---|---|
| Slowdowns after wave 40 | Studio statement, 25 Sep 2026 | 1 source · Steam |
| Cause they named | Endless balance, not a promise about every frame | 1 source · Steam |
| A settings toggle that adds a stated FPS number | Not published | 1 source |
| Same hitch on the 1.0 Endless mode | Not shown in a public test | 1 source |
What to check first
Confirm the build is v1.0.13 or newer, then confirm you are in Endless rather than Classic. Classic ends at wave 20 plus a boss, so a wave 40 complaint is an Endless complaint.
Separate a low frame rate from a hitch. The 25 Sep note split bugs that stutter, the post-wave-40 slowdown, and general performance before wave 40, where they declined to promise a fix.
Steam threads titled around performance and launch failures do not list a graphics setting that restores a measured frame rate. I am not going to invent one.
FAQ
Does every full-game run hitch at wave 40?
No public test says that. Another wiki says it does not claim every release build stalls at wave 40, and it has no controlled benchmark.
Did v1.0.13 fix it?
v1.0.13 lists artifact upgrade text, smaller bugs, and at least one soft-lock. It does not list a wave 40 performance line.
Why does the search say level 40?
The measured query is 'lag at lvl 40'. The in-game word in the studio post is wave.
Sources
Checked 2026-11-07.