fishies-text/field-guide/en-GB/reference/troubleshooting.md
2026-10-07 23:16:13 +03:00

2 KiB

Troubleshooting

What to try when the game won't load, sign-in gets stuck, sound is missing, or the desktop app misbehaves.

The game won't load

If the game won't get past its loading screen:

  • Reload the page; a slow or interrupted connection is the most common cause.
  • Make sure hardware acceleration is turned on in your browser's settings, and that no extension is blocking WebGL.

Sign-in problems

Sign-in can fail for reasons that have nothing to do with your account:

  • An app's built-in browser (opening a link from Instagram, TikTok or a similar app) often blocks the pop-up a sign-in needs; open the link in your device's normal browser instead.
  • If a provider says an account already exists, the game offers to link the two aquariums or sign in to the other one instead of losing either.

No sound

Fishies' sound effects are generated in the browser rather than downloaded as audio files, so missing sound is almost always the device's own volume or mute switch, or a browser tab muted from the tab bar.

Choppy performance

If the aquarium runs choppy:

  • Close other tabs and heavy background apps; the aquarium renders live and shares the GPU with everything else open.
  • On a laptop, check that the browser or the desktop app isn't running on a slow integrated GPU when a faster one is available.

Desktop app problems

For the desktop app specifically:

  • The app updates itself; if it seems stuck on an old version, quit and reopen it to let the update finish.
  • If it won't start at all, uninstall it from your operating system's usual apps list and reinstall from the game's download page, which always links the current build.

Still stuck

The Fishies Discord at discord.gg/fishies and Community, the game's own forum, both reach the team and other keepers.


In the game: https://fishies.lol/wiki/mechanics/troubleshooting · Fishies 0.8.3

This page is generated. Its text lives in locales/en-GB.json under wiki.topics.troubleshooting; correct it there.