We ship native Linux builds for Tiny Glade, but because Linux is more of an ecosystem than a singular entity, various oddities can sometimes appear.
Our Linux builds are compiled on Ubuntu 18.04 LTS, and we try to use as few dependencies as possible.
If possible, use a standard Steam package; we've seen cases of Tiny Glade struggling with Flatpak- and Snap-based installations.
If you see an error like:
😱 Failed to initialize the Steam API: FailedGeneric("Failed to load module '/home/tom/.steam/sdk64/steamclient.so'")
It means that the Steam SDK can't find the Steam installation. In that case either consult the docs of your package manager, or try the Valve-supported Steam distribution.
In Steam, Tiny Glade is configured to run in the Sniper runtime. If this gives you any trouble, you can bypass it by running the executable directly from the game's folder.
For AMD, we recommend the RADV/mesa driver, as it tends to be the fastest and most stable.
If you see random flickering glitches and have an AMD graphics chip, try running the game with the environment variable RADV_DEBUG=nodcc
To do this in Steam, go to Tiny Glade's properties in your game library, and in the free-text field under Launch Options, enter:
RADV_DEBUG=nodcc %command%
If you launch Tiny Glade from a terminal instead, navigate to the game's files, and use:
RADV_DEBUG=nodcc ./tiny-glade
This tells the RADV graphics driver to disable Delta Color Compression (a hardware feature). If it helps, there's no harm in disabling DCC other than a marginal performance degradation.
We don't currently support Wayland, and it is sometimes glitchy. If you have the option, please use X11 instead. Otherwise Proton will probably work.
Some issues seen specifically on Wayland include:
You might be able to work around those issues by proxying Tiny Glade through Gamescope (likely already in your distro).
Use the following launch option for Tiny Glade in Steam:
gamescope -W 1920 -H 1080 -f --force-grab-cursor -- %command%
Replace 1920 and 1080 with your preferred resolution.
If using Gamescope, make sure to run it with --force-grab-cursor. Otherwise it sends absolute cursor events when it should be sending deltas.
A similar issue occurs with remote access apps - configuring them for relative mouse motion events should do the trick.
This appears to be a Steam bug on Wayland. Try an X session instead, or run Tiny Glade via Proton.