Fish Lab Performance Tips Guide

Fish Lab’s hook is audiovisual: music-synced collection inside a lab that can drown the screen in GPU-simulated fish. When frame time spikes, your “misses” are often physics of hitching — not a sudden loss of skill. This guide covers swarm performance expectations, historical Intel UHD warnings, what the full game claimed to improve, Steam Cloud sanity checks, and how to report issues on Discord without vague rage posts. Pair hardware fit with System Requirements and timing feel with Controls & Input Guide.

How the swarm taxes your GPU

Unlike asset-heavy RPGs, Fish Lab’s cost scales with how many agents and shader effects are alive. Early sessions look cheap. Mid densification is where laptops wheeze. Late Endless fantasy — marketing talk around enormous on-screen counts — is a stress test, not a universal promise.

itch.io demo-era community comments called out frame drops once roughly ~3000 fish packed the screen on some machines. The developer replied that a fix was already in a local full-game build and invited testers via Discord. Treat that history as context: performance work was acknowledged before the September 2026 release, but your mileage still depends on GPU class, thermals, and background load.

Video guide

Intel UHD and unsupported-feeling GPUs

Older community guidance around the project stated that cards besides Intel UHD should work fine — a polite way to say UHD was trouble. Steam’s minimum line points at Iris Xe / Vega 11 / GTX 1050 2 GB class hardware. If you are on UHD:

• Expect hitching earlier in density curves
• Do not chase maximum spectacle settings
• Prefer shorter Sandbox peeks over hour-long Endless marathons
• Consider that refund-window testing should happen at your mid-game density, not the trailer’s climax

Read the requirements page before blaming the soundtrack.

Full-game posture versus demo hitching

The full release markets deeper systems — 200+ upgrades, grants, tools/power, Sandbox / Endless / Zen — and a polished swarm fantasy. Developer commentary during demo feedback suggested performance fixes were landing in the complete build. That is encouraging, not a warranty. After you install:

1. Play until density rises past the demo’s comfort zone
2. Watch frame pacing during heavy tool use and large schools
3. Note whether hitching is constant or thermal (gets worse after 15 minutes)
4. Check Updates / Steam News after patches before assuming you are stuck forever

Practical FPS triage (do these in order)

1. Close heavy background apps — browsers with dozens of tabs, other game launchers, video editors
2. Update GPU drivers — vendor packages beat year-old OEM defaults for shader-heavy titles
3. Cap or limit overlays — Discord, Steam, NVIDIA/AMD overlays can cost frame time
4. Watch thermals — elevate laptops, avoid soft surfaces, check if clocks are throttling
5. Lower capture load — local recording + streaming while Endless is a second game
6. Verify Steam files after crashes or partial updates
7. Reboot once after driver installs before declaring failure

If rhythm feels unfair, stabilize FPS before rewriting your hover technique in How to Collect Fish.

Mode-aware expectations

Mode	Performance note
Main short path	Usually the gentlest introduction
Sandbox	You can create dense messes on purpose — test carefully
Endless	Primary marathon stress test
Zen / screensaver	Presentation-first; still GPU-bound if the scene is busy

Details on mode intent live in Game Modes. Zen as a Windows screensaver is ambience; do not treat it as proof your Endless settings are fine.

Steam Cloud and “my performance broke after switching PCs”

Steam Cloud syncs progress — not your desktop’s GPU. If you collect on a strong tower and continue on a UHD laptop, the save is fine and the silicon is not. After switching machines:

• Allow cloud sync to finish before comparing densities
• Expect to play more conservatively on the weaker device
• Do not interpret lower FPS as a corrupted lab

How to report issues on Discord (useful reports)

Join the stonecodes Discord via the invite shared on the wiki overview (discord.com/invite/wpMPASWg7F). Good reports include:

• OS + CPU + GPU + RAM + driver version
• Steam build / approximate session length before hitching
• Mode (main / Sandbox / Endless / Zen)
• Rough fish density when FPS tanked
• Whether overlays or capture were active
• Screenshot or short clip if possible
• What you already tried (drivers, verify files, closed Chrome)

Avoid “unplayable???” with no specs — solo indie triage needs data. Also watch Steam News so you do not re-report a fixed patch; start at the Updates Hub and Launch 2026 notes.

Performance versus progression confusion

Sometimes the lab feels “slow” because processing lags collection or tool power is diluted, not because FPS died. Cross-check:

• Tips and Tricks for counter/tank confusion
• Power Allocation for weak-feeling tools
• Upgrades Priority for economy stalls

If the cursor stutters visually, it is performance. If the cursor is smooth but income stalls, it is systems.

Recording and sharing dense swarms

Creators love late swarms. If you record:

• Use a hardware encoder when available
• Lower in-game density targets while capturing 1080p60 overlays
• Prefer a second pass of pure play without OBS if you are diagnosing a hitch

The embedded video on this page is useful for seeing how crowded the fantasy can look — your GPU may need humility relative to edited footage.

Quick reference card

• GPU swarm sim ≠ light CPU idle game at climax
• ~3k fish already stressed some demo-era PCs
• Intel UHD historically discouraged
• Full game claimed fixes — still verify on your box
• Drivers, overlays, thermals, then Discord with specs
• Cloud sync ≠ free FPS on weak iGPUs

Keep the beat fair. A smooth 50–60 FPS hover session beats a slideshow chasing trailer counts. When patches land, retest density with the same checklist and update your mental map via Updates.