PC setup

SAND System Requirements Guide

Always check the current Steam page for official minimum and recommended requirements before installing SAND: Raiders of Sophie. This page focuses on how to read those specs, how to prepare your PC, and how to separate a hardware problem from a server or route problem.

SAND is an online extraction game with large vehicles, other players, PvE pressure, and open spaces. That means a playable setup is not only about launching the game. A stable first session also needs a reliable connection, updated drivers, enough storage headroom, and conservative settings while you learn the route loop.

Official PC Requirements Compared

The minimum column is the official entry point, not a promise that every large fight will hold a high frame rate. The largest gap is memory and graphics hardware: the recommended listing doubles RAM from 16 GB to 32 GB and moves from entry-level GTX 1650 or RX 570 class hardware to an RTX 3080 or RX 6800 XT. If your PC sits close to minimum, begin with lower visual settings and close browser tabs, recording software, and other GPU-heavy overlays before testing.

Before Your First Raid

1. Compare your PC against the current Steam system requirements.
2. Update graphics drivers before blaming in-game performance.
3. Use a stable connection because SAND is an online extraction game.
4. Run a low-value first session after major updates.

First-Run Setup Checklist

How to Test Performance Safely

Do not test a new setup during a high-value Storm Dive or a serious crew session. Start in a lower-risk run, move the Trampler, enter and leave a point of interest, watch for stutter during combat, and then extract. If performance problems appear, repeat the same route after lowering settings so you can compare one change at a time.

If the game stutters only when other players appear, treat it differently from constant low frame rate. Constant low frame rate points toward settings or hardware. Sudden spikes during online pressure can also involve network conditions, server load, background apps, or recording software.

Common Setup Mistakes

1. Joining a crew run before checking whether the game is stable on your own machine.
2. Changing graphics settings, drivers, overlays, and recording tools all at once.
3. Assuming every disconnect is a server problem without testing local network stability.
4. Using outdated guide claims instead of checking the current Steam listing.

When the Game Will Not Start or Stay Connected

Follow the official support order before reinstalling the whole game. Restart Steam and the PC, install current Windows and graphics-driver updates, then use Steam's installed-files menu to verify file integrity. If a launcher, security tool, or BattlEye prompt appears, record the exact message instead of treating every startup failure as the same problem.

For crashes, official support may ask for the game log and Windows crash dump. Windows commonly stores application dumps under %USERPROFILE%\AppData\Local\CrashDumps. Do not publish those files on a forum because they can contain device or account details; attach them only through the official support request. Linux and Steam Deck users should also check that Proton BattlEye Runtime is installed, while remembering that the current Steam requirements list Windows rather than promising native Linux support.

If the game reaches the menu but a session disconnects, use the known-issues checklist. Test another network route, disable VPN or proxy software temporarily, and compare a solo attempt with the same local setup. That comparison helps distinguish a repeatable PC problem from a temporary service or routing problem.