How to Fish Black Screen Fix: Startup and Co-op

Identify when the screen turns black

A black screen at startup and one that appears only while joining friends are different symptoms. Some guests report hearing the session while the screen stays black or the camera will not rotate. Record those details before changing settings.

Apply the lowest-risk checks first

Install the current update, close and restart Steam, confirm host and guests match versions, then recreate the lobby. Community reports say a host restart helped some sessions, not every session.

• Do not delete a save as an opening troubleshooting step.
• Do not download third-party repair tools for this symptom.
• Record whether the problem is startup-only or lobby-only.

Escalate with useful evidence

Patch 1.0.9 adds a short Steam connection check in the main menu. If the Steam Relay text turns red, follow the official Discord common-bugs guidance and include the version, host or guest role, and exact point where the screen changed.

Separate invite and lobby-cap problems

If the invite never opens a session and no black screen appears, record that as an invitation or connection failure. The store originally described one-to-four-player co-op, while patch 1.0.4 added lobbies of up to eight; every participant still needs the current build. Do not call an ordinary full lobby a display failure.

Diagnose the How to Fish black screen by timing

The phrase How to Fish black screen can describe more than one failure. Record whether the screen changes before the menu, during startup, while joining a friend, or after a lobby begins. A startup gray or black screen and a guest-only joining screen have different evidence. Official patch 1.0.4 described an attempt to fix both lobby and startup symptoms, but later community reports mean the note should not be read as a guarantee that every system was permanently resolved.

Write down the smallest sequence that reproduces the problem. Include current game version, Windows version, host or guest role, and the last normal screen. Ask whether the host enters successfully while guests remain blocked, whether audio continues behind a black display, or whether the camera appears locked after joining. Community posts describe those joining variants, but they do not establish one universal cause. This classification determines whether recreating a lobby is relevant and gives the official Discord common-bugs area useful evidence.

Apply safe black-screen fixes in order

Install the current How to Fish update, close the game, fully restart Steam, and confirm every player uses the same version. For a joining symptom, have the host close and recreate the lobby before guests reconnect. A later Steam discussion reported one case where restarting the host helped, but that remains a community workaround rather than a universal solution. Stop after each step and check whether the symptom changed so the result remains understandable.

Preserve save files and local evidence. Do not delete progress, run unknown repair software, download replacement executables, or disable security protections as an opening response. Those actions may create a second problem and make support diagnosis harder. If audio continues or controls respond behind the display issue, record that detail along with any locked-camera behavior. Use official instructions if the developer later publishes a more specific recovery procedure.

Check the Steam Relay status added in patch 1.0.9

Patch 1.0.9 added connection debugging for Steam Relay. If the in-game relay text is red, record the exact wording and treat the symptom as a connection or lobby problem rather than a missing quest step. Restart Steam completely, confirm the game is current for every player, and recreate the lobby once. Do not repeatedly change routers, firewall rules, saves, and game files at the same time because that removes the evidence needed to identify which check affected the result.

When the relay remains red, the official patch note directs players to the Discord common-bugs area. Report the current version, relay text, host or guest role, lobby size, and whether solo startup works. Include the result of one Steam restart and one recreated lobby. This information is more useful than a screenshot with no sequence. Keep account credentials, private network details, and unrelated files out of a public report.

Escalate a stuck black screen with useful evidence

Official Steam news mentions relay debugging and points players toward the developer-linked Discord for common bugs. When safe checks fail, report the current version, exact timing, host or guest role, number of players, and whether a full Steam restart or recreated lobby changed anything. Include a screenshot only if it shows the relevant state without exposing personal information. Do not post account credentials, private tokens, or unrelated system files.

Separate this technical symptom from a progression lock. If the game displays normally but the next island or boat does not unlock, return to the relevant hand-in guide. Recreating the lobby can help a joining problem, but it will not replace a missing boss reward. Clear boundaries keep the black-screen page focused on one long-tail technical question and prevent risky system advice from being mixed into ordinary quest troubleshooting.

Separate black screens from save and progression problems

A page that loads normally but refuses to unlock the boat or next island is not the same as a black screen. Return to the relevant boss reward, leech hand-in, or route guide and verify the objective. Likewise, equipment disappearing after a reload belongs in the Lost Items and Save Safety page. Reinstalling or recreating a lobby cannot restore a missing hand-in, and deleting a save is not a safe opening response to a display problem.

This boundary protects progress and keeps the long-tail answer useful. Use Black Screen for startup, display, joining, and Steam Relay symptoms. Use Lost Items for inventory or save evidence, and use the Walkthrough for objective order. Each page then solves one problem and passes the player to a closely related answer only when the symptom changes, preventing isolated pages without mixing unrelated fixes into one checklist.

Frequently asked questions