Info

Water You Doing Troubleshooting Launch Issues

The physics are supposed to be chaotic. These problems are not. Here is what the studio already patched — and what to try today.

Last updated:

Troubleshooting & Known Issues

Water You Doing? launched on Steam on August 26, 2026 to a rough first impression. As of the next day, user reviews sat at Mostly Negative — 37 percent positive out of 74 ratings. That is not a secret, and this wiki will not pretend the voyage is smooth. Many complaints match bugs the studio already fought during the June demo: client rubberbanding on a fully physics-driven boat, harpoons that yank the hull into the sky, saves that write to the wrong slot, and water that will not leave the bilge.

This page is a practical list. It is not a promise that every issue is gone in 1.0. The demo received seven numbered hotfixes plus Patches 06.09G and 06.09H. DiSolve said those fixes, plus more polish, went into the paid release, and they disabled the demo because it no longer matched the product. If you are still seeing a listed bug, verify your build, then report it with hardware, player count, and host-versus-client.

For patch chronology see Updates. For whether the game is worth buying in this climate see Reviews.

First checks before you blame physics

  1. Let Steam update. Right-click the game, open Properties, and confirm you are not on an old beta branch.
  2. Decide who hosts. The boat is the centre of the simulation. Clients felt rubberbanding and phantom corrections throughout the demo. Hosting on the machine with the best CPU and a wired connection is still the least painful option.
  3. Start with Medium graphics. Hotfix 1 made Medium the default because High was eating CPU on fish, particles, and boat lights. If you raised settings after install, drop them before you call the game unplayable.
  4. Use Push to Talk. It is the default voice mode after a crash risk when switching from Open Mic. Set levels with the voice-chat volume bar added in Patch 06.09H.
  5. Know the difference between chaos and a bug. A slap, a flying bucket, or a ragdoll overboard is the fantasy. A boat that teleports five metres every second for clients is a netcode problem.

Boat rubberbanding and client movement

This was the studio’s biggest multiplayer focus going into Patch 06.09H. Clients saw the hull snap, slide, or fight their inputs because the boat is fully physics-driven. Standing on deck while the host steers made it worse. The patch improved replication, item dropping on a moving deck, and how items save in multiplayer.

If it still happens in 1.0:

  • Have the host re-host rather than migrating mid-voyage.
  • Stop stacking scrap in a pile that wedges the hull. Demo Hotfix 4 shrank scrap collision and fixed dropped items pinning the boat.
  • Do not stand in a client-only “correction jitter” and keep firing harpoons. Wait for the boat to settle, then work.
  • If the boat thinks it is on land, listen for the land alarm (Hotfix 5/6). Get back into water before you repair.

Harpoons that fling the boat

Community posts from the demo described pulling the boat with stacked harpoons until it launched “into space” or sideways into a fatal collision. Hotfix 1 specifically fixed harpoons being violently launched on retract, tightened constraints, and reduced excessive constraint distance. Hotfix 5 added a gradual ramp-up to pull force. Hotfix 6 added Rapid and Slow pull modes so you can stop treating every tug like a rocket.

Practical rules from Harpoons:

  • Prefer Slow Mode when the line is attached to the world and the hull is already moving.
  • Do not chain retracts the instant the previous pull finishes.
  • If the boat starts to climb, cut the pull rather than adding a second module.
  • Clients had extra harpoon desync; if only non-hosts see ghost lines, rejoin.

Saving, checkpoints, and lost items

Hotfix 1 fixed every save slot writing to the same file and added unique 152×152 thumbnails. Hotfix 3 fixed delete-save and load failures, and wallets or rods losing contents when stored in multiplayer. Patch 06.09H improved item saving and dropping, and fixed pause after some checkpoint loads.

If a checkpoint feels cursed:

  • Do not stash a loaded wallet or a baited rod in a slot, then immediately reload.
  • After a wreck, wait through the extended reload delay instead of mashing continue (Hotfix 3).
  • The revive toilet needs a real Golden Fish — Hotfix 4 fixed it accepting a revive without one.

Water, buckets, and “I cannot bail”

Hotfix 1 fixed clients who could not pour water out, buckets that refused to work at very low water, and repair meshes that rotated wrong or fell through the floor. Hotfix 3 stopped the flooding VFX when the boat was not actually flooding, and sped up the bucket animation.

If the bilge will not empty, switch who is holding the bucket, step fully inside the volume, and confirm the engine-off emergency lights are not hiding a hole you have not patched. Repair collision bugs made “fixed” planks vanish; look with the camera, not only the health UI. Hotfix 7 also clamped boat-health UI so a wild number does not fool you.

Fishing, selling, and money doubling

Demo patches fixed client fishing animations, bait stuck on the line, rods equipped from inventory not hiding, money not displaying after a sale, and fish still sellable while hooked. Hotfix 4 let you sell without parking fish in one tiny square, added more rods on the map and one on the boat, then reduced sell prices. Patch 06.09H fixed money being added twice for clients.

If a client suddenly has double coins, assume a replication bug, not a feature. Relog. If fish will not sell, take them off the rod first.

Performance and darkness

Hotfix 1 cut CPU on fish animation, characters, particles, overlaps, and GPU boat lights. Hotfix 2 added more CPU wins and brightened nights. Hotfix 3 stopped thunderstorms from going pitch black and improved underwater colour. If your GTX 950M-class machine hitchs in four-player sessions, stay on Medium, reduce crowds of fish on screen, and avoid stacking particle-heavy wrecks.

How to report a remaining bug

Use the Steam discussion hub or the studio Discord. Include whether you were host or client, player count, approximate ping, a clip of the hull or harpoon, and the exact action (gate payment, checkpoint load, retract). The developer email on the store page is [email protected]. Launch notes said they would watch discussions, Discord, and reviews from day one.

This game will always look broken for a second when four people slap each other on a physics boat. Use this page for the second kind of broken — the kind that ends a run before the joke does.

FAQ

Frequently Asked Questions

Quick answers to the most common questions.

Is the game still as buggy as the demo videos?

The June demo had a long hotfix streak. Those fixes were supposed to land in the August 26 release, and the demo was turned off because it was outdated. Launch reviews on day two were still Mostly Negative, so treat 1.0 as improved, not finished.

Should clients or the host steer?

The host’s machine is the source of truth for the physics boat. Let the host steer if clients rubberband. Patch 06.09H reduced visible corrections but did not repeal latency.

My harpoon yeets the boat. Is that intended?

Stacked pulls can still get violent — that is the toy. Instant space launches on retract were called out and patched in demo Hotfix 1. Use Slow Mode and stop adding lines when the hull leaves the water.

Where do I send a save-breaking bug?

Steam discussions or Discord with host/client, player count, and steps. Mention checkpoint load, wallets in storage, and version. Email [email protected] if you need a direct line.