Tiny Glade Performance and Settings Fixes (Windows/Linux)

If Tiny Glade feels choppy, start with two basics: FPS (frames per second, or how many images you see each second) and stutter (tiny pauses between those frames). In a cozy builder like Tiny Glade, steady motion usually matters more than high peak FPS, so focus on smooth frame pacing first.

Before changing a bunch of settings, build a clean baseline and test one thing at a time:

Restart the game and close heavy apps (especially browser/Discord tabs) so more VRAM (video memory) is free for Tiny Glade.
Go to Settings -> Video -> Image. Start with the Balanced or Performance preset, then lower Resolution scale only if you still need more performance.
If frame pacing feels uneven, try V-Sync on and off (it syncs frames to your monitor). Tiny Glade also defaults to a 60 FPS cap, and lowering that cap can cut heat/noise on weaker systems.
Test in a busy diorama area (a scene with lots of placed pieces) so your results match real gameplay.

Windows quick fixes

Update GPU drivers directly from NVIDIA/AMD/Intel, then reboot.
If issues started after an update, verify game files in Steam. If crashes keep happening, reinstall to replace missing or damaged files.
If performance is still rough, use Tiny Glade's F6 feedback tool so your report includes benchmark/performance data.

Linux quick fixes

Tiny Glade has a native Linux build. If you can, use a standard Steam package, since the devs report more odd issues with Flatpak installs.
For AMD on Linux, the devs recommend RADV/Mesa.
Wayland is currently unsupported and can be glitchy in Tiny Glade, so use an X11 session when possible.
If Wayland still gives you trouble, try Proton (a compatibility layer). For Wayland cursor/color issues, running through Gamescope with --force-grab-cursor can help.

If stutter or low FPS is still there, write down exactly what you changed (preset, resolution scale, V-Sync, X11/Wayland). Then include your GPU, CPU, Windows/Linux version, distro (if Linux), and driver version when you ask for help. That usually gets you faster, more accurate troubleshooting.

← Prev