Launch-week issue tracking

SAND Known Issues Guide

SAND: Raiders of Sophie is in Early Access, so the safest way to read bug reports is to separate three things: old launch-week outages, issues the developers have already marked as fixed, and problems that are still listed as current official watch items. This page exists for that triage job, not for rumor chasing.

As of this Jul 1, 2026 content pass, the newest durable official signals come from Steam announcements on June 24, 2026 and June 26, 2026, plus the current tinyBuild support knowledge base. When those sources disagree, trust the newer dated Steam announcement for fix status and use the support article for symptom-based workarounds.

What Changed During Launch Week

The most important freshness split is this: on June 24, the official Steam "Mission Update" warned players to avoid Voyage Mode because servers could live too long, hit a memory crash, throw a network disconnect, and then leave players stuck on a reconnecting screen. Two days later, Steam Update #1 reported a larger fix batch and moved the official conversation from "avoid Voyage" to a shorter list of remaining high-priority issues.

That means older community videos about endless reconnects are useful only as symptom discovery. For current planning, first check whether your problem matches the June 26 remaining-issues list, then decide whether you are dealing with a live service problem, a local setup problem, or an issue that already has a published workaround.

Stuck on Loading or Reconnecting Screen

This is the symptom with the strongest public search noise right now, and it is also one of the few issues the official support flow addresses directly. The current support article says players who appear stuck loading forever should first make sure they are on the same region and character pairing they used before, because character progress is region-bound. The same support guidance also surfaces an English-language client workaround for some loading-flow problems.

Put that together with the June 24 Steam post and the practical move is simple: if the game is trying to reconnect you to a dead Voyage server, stop forcing the same reconnect loop. Back out, confirm the correct region, try the support-side language workaround if needed, and use a cheap test session after service conditions stabilize instead of jumping straight back into a valuable route. If the symptom persists after the official workaround steps, treat it like a live issue and monitor server status and patch tracker before risking rare loot.

Issues Still Worth Watching

Solo queue mismatchSteam Update #1 still listed solo players being matched into larger crews as an active issue, so solo route advice should stay conservative and fresh.
Ladder problemsThe remaining-issues list still mentioned teleporting on ladders and getting stuck near the top, which matters in ship and tower routes.
High-latency display bugsOfficial notes still mention badly displayed players and Tramplers under unstable connection conditions, so do not confuse netcode desync with a balance problem.
Collision launchesUpdate #1 still warned that Trampler collisions can throw players off, which makes crowded crew maneuvers and panic boarding riskier.

What Steam Update #1 Explicitly Marked as Fixed

The June 26 changelog matters because it retired several launch-week complaints that still show up in old discussions. That official fix batch included the "Respawn unavailable" message appearing at expedition start, a workbench interaction soft lock, bad anti-aliasing and upscaler behavior in menus, some invisible railings or colliders on Tramplers under packet loss, a T-pose death issue, and several pickup or large-item animation errors.

Do not assume every mention of those bugs is current. If you see one of those symptoms now, first confirm the client is updated and that you are not watching a pre-Update-#1 guide. That is exactly why pages such as roadmap, Early Access, and Steam release should always be read with dates in mind.

How to Triage the Problem Before a Real Raid

  1. Check the newest official Steam announcement date before trusting any community fix video.
  2. If the symptom looks like queue trouble or disconnects, compare it against matchmaking bucket behavior and wider server preparation advice.
  3. If the symptom looks local, re-check system requirements, overlays, drivers, and one clean restart after patching.
  4. If the symptom happened in Voyage after a service incident, run a throwaway session before returning to your normal route planning loop.
  5. If the symptom changes the risk of boarding, ladders, or exits, tighten your extraction rule for the next run.

What This Means for Guides on This Site

Bug awareness changes how you should use the rest of the wiki. If solo matchmaking is still unstable, the solo guide and crew size pages matter more. If ladders and collision launches remain live issues, then Storm Dive and Trampler guide advice should bias toward earlier exits and cleaner boarding paths. If reconnect or loading problems are trending, then low-risk Voyage tests and smaller-value loot runs become the correct research tool.

Known-issues rule: trust the newest dated official post for fix status, and use support workarounds only after you confirm the symptom still matches.

Related guides

Source basis: official Steam announcements on Jun 24 and Jun 26, 2026, the Steam store listing, current tinyBuild support known-issues and troubleshooting pages, the official site, and public search/video discussion signals checked on Jul 1, 2026.