Back to 60fps — the 30fps cap was too noticeable
The knob stays (TUNE.fps in the T panel) for anyone who wants to trade smoothness for battery; the pile cache and GC fixes keep their savings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
70882d2dd4
commit
2e5af224b8
1 file changed
+1
-1
@@ -39,7 +39,7 @@ export const TUNE = {
|
||||
hordeRate: 2.5, // zombies spawned per second during a horde
|
||||
mgRate: 6, // machine-gun pellets fired per second during a horde
|
||||
mgPickupLen: 8, // s the machine-gun tin (4th delivery) auto-fires outside hordes
|
||||
fps: 30, // frame cap — pixel art reads fine at 30 and it halves battery/heat; set 60 to compare
|
||||
fps: 60, // frame cap — 30 halves battery/heat but Oliver felt it; smoothness wins (0 = uncapped)
|
||||
runnerSpeed: 3.2, // runner ('f') speed multiplier over the shamble
|
||||
runnerVMax: 4.2, // hard runner speed cap — the late-game ramp must stay humanly reactable
|
||||
bruteHp: 2, // splat-quality hits (or pellets) a brute ('g') soaks before it dies
|
||||
|
||||
Reference in new issue
Block a user