#Stuck on horizon view / Cannot start match (Multiple players)

1 messages · Page 1 of 1 (latest)

coral shoalBOT
#

Thanks for the detailed info. Since this looks like a matchmaking/connectivity stall, please try the remaining checks below:

  • Press F11 to view the network debug overlay while queued (ping etc.).
  • If you get stuck in a queue/disconnection loop, switch to a different server region and try again.
  • Long matchmaking times: wait up to 15 minutes; if no match is found, restart the client and make sure your expedition is planned and a Trampler is selected.
  • Ensure the game is allowed through your Firewall/Antivirus.
  • Use a stable, wired (Ethernet) connection if possible.
  • Test an alternate internet connection (e.g., mobile hotspot) to see if the issue is ISP-related, and try opening the PlayFab website in a browser to verify access.

If issues persist, please attach your player.log and player-prev.log from:
%USERPROFILE%\AppData\LocalLow\Hologryph\SAND

For Linux/Steam Deck users: make sure the Proton BattlEye Runtime is installed from your Steam library.

Share any findings from the F11 overlay (ping/behavior changes when switching regions or networks) so we can narrow it down.

Sources:

worthy parrot
#

have you read my post?

worthy parrot
# coral shoal Thanks for the detailed info. Since this looks like a matchmaking/connectivity s...

VfxAmount
VfxAmount: 65
Client snapshot
last server tick: -2147483648 0 0,05
last server time: 12:00:00.000 12:00:00.000
remote delta: 136389 0
ping: 13
lastPacketReceived: 0
appr. server fps: 20,00
Player Avatar
Position: (0.00, 0.00, 0.00)
Network Messages
Last Second: 2 messages, 0,25 kbps / 32 Bytes, median size 16
Last Minute: 5,8 messages, 1,69 kbps / 216,83 Bytes, average size 31
Snapshots: 0,0 snapshot messages, 0,00 Bytes. Dropped: 0 Skipped delta ticks: 0
Game Match
Current match state: LOW
System
Update count: 0
Input
(0.00, 0.00)
Avatar Movement

Audio
Playing count: 0
Occlusion culling
Registered environments: 0 Environment occlusion: 0
Eye Of Storm
Current state: -----
Forecast: Waiting for forecast

coral shoalBOT
# worthy parrot VfxAmount VfxAmount: 65 Client snapshot last server tick: -2147483648 0 0,05 las...

From your debug it looks like a connectivity/desync issue (no snapshots, very low message rate). Please try:

  • Run the game as Administrator.
  • Press F11 to monitor ping/network stats while testing.
  • If you’re in a disconnection loop or see no snapshots, switch to another server/region and try again.
  • Check Firewall/Antivirus and make sure the game is allowed.
  • Prefer a stable, wired internet connection.
  • If possible, test another connection (e.g., a mobile hotspot) to rule out ISP issues. You can also test access by opening this PlayFab page in your browser: https://developer.microsoft.com/en-us/games/products/playfab/
  • If matchmaking takes long, wait up to 15 minutes; if nothing happens, restart the client and ensure your expedition is planned and a Trampler is selected.

Share what changes after trying the steps above so we can narrow it down further.

Sources:

Microsoft Game Dev
PlayFab

PlayFab is the complete backend platform for live games. Build cross-platform multiplayer, LiveOps, economy, and player identity services. Free to start.

#

A few targeted checks based on our guidance:

Connectivity/Matchmaking

  • Long matchmaking times: wait up to 15 minutes. If no match is found, restart the client and ensure your expedition is planned and a Trampler is selected.
  • Press F11 to view ping/debug info and play on the closest region.
  • Use a stable, wired connection if possible.
  • Try a different connection (e.g., mobile hotspot) to rule out ISP issues; also try opening the PlayFab developer site in your browser to verify it loads from your network.
  • Ensure the game is allowed through your Firewall/Antivirus.
  • If you hit disconnection loops, try switching servers.

BattlEye/Launch checks

  • Run the launcher as Administrator and start the game directly from it.
  • Move the game to the same drive as your OS.
  • Verify files via Steam and (re)install BattlEye using Install_BattlEye.bat.
  • Keep Windows and GPU drivers up to date and disable overlays/background services.

Logs location

  • Player logs are generated at: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND (player.log, player-prev.log).

If you try the connection tests (wired/alternate network + PlayFab site) and the admin/OS-drive steps, let us know what changes, along with whether F11 shows stable ping during queueing.

Sources:

#

Thanks for the detailed checks. Please try these targeted steps:

Connectivity

  • Press F11 to view ping/network debug.
  • If you get disconnection loops, switch servers. For long matchmaking, wait up to 15 minutes; if no match is found, restart the client and ensure your expedition is planned and a Trampler is selected.
  • Prefer a wired connection. Double‑check Firewall/Antivirus allows the game. Test with a different connection (e.g., mobile hotspot) to rule out ISP issues, and confirm you can access the PlayFab site in a browser.

BattlEye/Launch

  • Run the launcher as Administrator and start the game directly from it.
  • Try moving the game to the same drive as your OS.
  • On Linux/Steam Deck, install the Proton BattlEye Runtime from your Steam library.
  • If you see “Failed to Initialize BattlEye Service,” disable Kernel‑mode Hardware‑enforced Stack Protection in Windows Core Isolation, then restart.

Software conflicts

  • Fully close always‑on anti‑cheats (e.g., Riot Vanguard), aggressive overlays, and third‑party antivirus as they can block anti‑cheat initialization.
  • If using a controller, disable Steam Input to avoid issues.

Logs

  • Player logs (player.log / player-prev.log) are saved at %USERPROFILE%\AppData\LocalLow\Hologryph\SAND.

Also ensure your PC meets minimum requirements, verify game files, and consider lowering graphics settings if loads are long.

Sources:

#

Thanks for all the detail. Please try the following checks that apply:

Connectivity

  • Press F11 in-game to view ping/network debug.
  • Matchmaking: wait up to 15 minutes; if no match is found, restart the client and ensure your expedition is planned and a Trampler is selected.
  • Use a stable, wired connection if possible.
  • Try a different connection (e.g., mobile hotspot) to rule out ISP issues. Also check you can open the PlayFab website in a browser.
  • Confirm your Firewall/Antivirus allows the game.

BattlEye / Launch

  • Run the launcher as Administrator and start the game directly from it (not only via Steam).
  • Try moving the game to the same drive as your OS.
  • If you’re on Linux/Steam Deck, install the Proton BattlEye Runtime from your Steam library.

General

  • Ensure your PC meets the minimum hardware requirements.
  • If loading is just very long, lower graphics settings.

Logs

  • After attempting a launch, player.log and player-prev.log should be at: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND. If they appear after another attempt, please share them here to help narrow it down.

If the issue persists after these steps, let us know whether switching to a different internet connection changed anything, and whether starting via the launcher (as Admin) made any difference.

Sources:

#

This one’s beyond my AI brainpower, but no worries—our support team will take a closer look! Let me know if you have any extra details; every bit helps!

coral shoalBOT
#

We can help with a real fix, but we need specifics so the team can reproduce it. Please share here:

  • Exact steps to reproduce the problem
  • Screenshots/video
  • Your Server/Region and whether you were solo or in a party
  • A direct link to your Steam profile
  • If it’s a disconnect/crash/missing Trampler/inventory issue: your 17‑digit SteamID, approximate time it happened, whether it was on the Trampler or outside, and if you used a custom or default Trampler
  • Attach player.log and player-prev.log from: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND

If it’s connectivity/performance/crashes, try these while you share details:

  • Run the game as Admin
  • Press F11 to check your ping/debug info
  • If stuck in disconnection loops, try switching servers
  • Ensure the game is allowed in your Firewall/Antivirus
  • Prefer wired internet; test another connection (e.g., hotspot) to rule out ISP issues

This info lets us investigate and respond with a targeted fix instead of a generic one.

Sources:

#

We want to help get you a real fix, but we need specifics. Please share:

  • A detailed description and exact steps to reproduce
  • Any screenshots/videos
  • Your Server/Region and whether you were solo or in a party
  • player.log and player-prev.log from: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND
  • If it’s about disconnects, crashes, missing Tramplers, or inventory: your 17-digit SteamID, approx time, whether it happened on the Trampler or outside, and if you used a custom or default Trampler
  • A direct link to your Steam account

Meanwhile, try these proven steps:

  • Update Windows and your GPU drivers; ensure your PC meets minimum requirements
  • Verify integrity of game files
  • Long loading: lower graphics settings
  • Connectivity: run the game as Admin, press F11 to check ping, switch servers if in a disconnection loop, allow the game through Firewall/Antivirus, prefer a wired connection, and if matchmaking takes long, wait up to 15 minutes—if no match, restart the client and ensure your expedition is planned and a Trampler is selected. Try another connection (e.g., mobile hotspot) or check access to the PlayFab site
  • Linux/Steam Deck: install the Proton BattlEye Runtime from your Steam library

Sources:

#

Refunds are handled directly by Steam under their refund policy. For a non-working game or accidental/unauthorized purchases, please contact Steam Support to request a refund. We also recommend reviewing Steam’s parental controls to help prevent unauthorized transactions in the future.

Sources:

#

This one’s beyond my AI brainpower, but no worries—our support team will take a closer look! Let me know if you have any extra details; every bit helps!

coral shoalBOT
#

This one’s beyond my AI brainpower, but no worries—our support team will take a closer look! Let me know if you have any extra details; every bit helps!

#

Here’s a quick checklist to fix common issues:

  • Update Windows and your GPU drivers; make sure your PC meets the minimum specs.
  • Verify game files in Steam.
  • On Linux/Steam Deck: install the Proton BattlEye Runtime from your Steam library.
  • Run the launcher as Administrator and start the game from it.
  • Disable overlays/background tools (e.g., Razer Synapse, Nvidia App, Discord overlay, MSI Afterburner).
  • Reinstall BattlEye (run Install_BattlEye.bat in the game folder).
  • If you see “Failed to Initialize BattlEye Service”: Windows Core Isolation → turn off Kernel‑mode Hardware‑enforced Stack Protection → restart PC.
  • BSOD on launch: update BIOS/drivers; open Command Prompt as Admin → run: verifier /reset → restart PC.
  • Connectivity: press F11 to check ping; try switching servers if you loop on disconnect; allow the game in Firewall/Antivirus; use wired internet. Long matchmaking: wait up to 15 min; if no match, restart the client and ensure your expedition is planned and a Trampler is selected.
  • Performance: force the game to use your dedicated GPU (Windows Settings → System → Display → Graphics → add the game .exe → set to High performance).

If you’re still stuck, share player.log and player-prev.log from %USERPROFILE%\AppData\LocalLow\Hologryph\SAND, your 17‑digit SteamID, approximate time, where it happened (on Trampler or outside), and whether you used a custom or default Trampler.

Sources:

#

We need more details to help with a proper fix. Please share: what exactly is happening (error/messages), when it occurs, your platform/OS, and what you already tried. Meanwhile, try these verified steps:

  • General: Update GPU drivers and Windows, verify game files. On Linux/Steam Deck, install Proton BattlEye Runtime. For long loading, lower graphics settings.
  • Connectivity: Run the game as Admin; press F11 to view ping; if you’re in a disconnect loop, switch servers; allow the game in Firewall/AV; prefer wired; try another connection.
  • BattlEye/launch issues: Verify files; run Install_BattlEye.bat from the game folder; update Windows/GPU/other drivers; run the launcher as admin; try installing the game on your OS drive. “Failed to Initialize BattlEye Service”: disable Kernel‑mode Hardware‑enforced Stack Protection (Core Isolation) and reboot. BSOD: update BIOS/drivers, then run “verifier /reset” in admin Command Prompt and reboot. “Client not responding”: restart router, close background apps, restart the BattlEye Service in services.msc.
  • Known workarounds: If Trampler props are invisible/corrupted or crates leave stuck visuals: Win+R → regedit → Computer\HKEY_CURRENT_USER\Software\Hologryph\ → delete the Sand folder. Stuck on ladders: press F. Stuck on rails/props/stairs/ramps: try jump+crouch or respawn. If extraction was interrupted by the Trampler: call extraction again. Extra memory use after re‑entering the same expedition: restart the game.

If it persists, please share player.log and player-prev.log from %USERPROFILE%\AppData\LocalLow\Hologryph\SAND; and for disconnects/crashes/inventory/Trampler issues also include your 17‑digit SteamID, approx time, whether it was on/off the Trampler, and if the Trampler was custom or default.

Sources:

#

Hey! I am looking this up for you, I will update this message shortly

#

We don’t have an exact ETA to share yet, but the team is actively investigating the current set of known issues. Some have temporary workarounds:

  • Invisible/corrupted Trampler props or stuck duplicate crates: open Registry Editor (Win+R -> regedit) and delete the Sand folder at Computer\HKEY_CURRENT_USER\Software\Hologryph.
  • Ladder exit leaves you levitating/stuck or drops you: press F to free your character.
  • Stuck on rails/props/stairs/ramps/scaffolding: try jumping and crouching; in some cases a respawn is needed.
  • Extraction interrupted by the Trampler: call for extraction again.
  • Extra memory use after re-entering the same expedition: close and relaunch the game.

Tell us which specific issue you’re hitting and we’ll point you to the best workaround from the list.

Sources:

#

Could you share what issue you’re hitting? Here are the current confirmed fixes/workarounds:

  • Trampler props invisible/corrupted or duplicate crate visuals: Win+R → regedit → Computer\HKEY_CURRENT_USER\Software\Hologryph\ → delete the “Sand” folder.
  • Ladder exit leaves you levitating/stuck/dropped: press F.
  • Stuck on rails/props/stairs/ramps/scaffolding: try jumping + crouching; if that fails, respawn.
  • Extraction interrupted by your Trampler: call for extraction again.
  • Memory keeps growing after re-entering the same expedition: close the game to free it.

If it’s connection/matchmaking:

  • Run the game as Admin; press F11 for ping/debug.
  • In disconnection loops, switch servers.
  • Long matchmaking: wait up to 15 minutes; if no match, restart the client and ensure your expedition is planned and a Trampler is selected.
  • Check Firewall/Antivirus allows the game; prefer wired internet; if possible, try another connection (e.g., mobile hotspot) or test by opening the PlayFab site in a browser.

If it’s BattlEye (launch/crash/“Failed to initialize”/BSOD/“Client not responding”), say the exact error and I’ll share the specific steps.

Sources:

#

Thanks for reaching out. To help us assist you here, please include:

  • A detailed description of the problem and exact steps to reproduce it
  • Screenshots or video (if available)
  • Your Server/Region and whether you were solo or in a party
  • A direct link to your Steam account

If it’s a technical issue (connectivity, performance, crashes, missing items/Trampler), also add:

  • player.log and player-prev.log from: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND
  • Your 17-digit SteamID
  • Approximate time the issue occurred
  • Whether it happened on the Trampler or outside
  • Whether you used a custom or default Trampler

Quick checks that often help:

  • Update Windows and GPU drivers
  • Verify game file integrity via Steam
  • For long loading times: lower graphics settings
  • On Linux/Steam Deck: install the Proton BattlEye Runtime from your Steam library

Also, please check our Known Issues list first to see if your issue is already being tracked.

Sources:

drowsy sinew
#

clanka

coral shoalBOT
#

Could you clarify which issue you mean? Some have current workarounds:

  • Invisible/corrupted Trampler props or stuck duplicate crates: Win+R > regedit > go to Computer\HKEY_CURRENT_USER\Software\Hologryph\ and delete the Sand folder.
  • Ladder exit leaves you levitating/stuck/dropped: press F.
  • Stuck on rails/props/stairs/ramps/scaffolding: try jump + crouch; if that fails, respawn.
  • Extraction interrupted by the Trampler: call extraction again.
  • Memory grows after re-entering the same expedition: close the game to free it.

If it’s launch/BattlEye-related: verify game files, reinstall BattlEye (run Install_BattlEye.bat from the game folder), update Windows and GPU drivers, run the launcher as admin. For “Failed to Initialize BattlEye Service,” disable Kernel-mode Hardware-enforced Stack Protection and restart.

If none of the above fits, please share a brief description plus player.log and player-prev.log from: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND. For disconnects/crashes/missing Tramplers/inventory issues, also include your 17-digit SteamID, approximate time, whether it happened on the Trampler or outside, and if the Trampler was custom or default.

Sources:

drowsy sinew
#

this clanker is stupid

#

lol

worthy parrot
#

yes

coral shoalBOT
#

Can you clarify which issue you mean? Current confirmed fixes/workarounds:

  • Invisible/corrupted Trampler props or duplicate crate visuals: Win+R → regedit → HKEY_CURRENT_USER\Software\Hologryph\ and delete the Sand folder.
  • Ladder exit leaves you levitating/stuck or drops you: press F.
  • Stuck on rails/props/stairs/ramps/scaffolding: try jumping+crouching; if that fails, respawn.
  • Extraction interrupted by the Trampler: call for extraction again.
  • “Respawn unavailable” widget at expedition start: visual only; you should still be able to respawn.
  • Memory usage increases after re-entering the same expedition a few times: close the game to free memory.

If it’s a different problem, share what happens and we’ll match it to a known workaround. For general issues: ensure your PC meets requirements, update GPU drivers/Windows, verify game files, and (Linux/Deck) install Proton BattlEye Runtime.

Sources:

#

Thanks for flagging this. To help the team investigate the missing UI after match start, please share:

  • Exact steps to reproduce
  • Mode (Voyage or Storm Dive) and whether you were solo or in a crew (and size)
  • Your server/region
  • Screenshots or a short video
  • A direct link to your Steam account

Quick checks you can try now (from our troubleshooting steps):

  • Temporarily disable overlays/background tools (Discord overlay, Nvidia App, MSI Afterburner, Razer Synapse) and relaunch.
  • Verify game files in Steam.
  • Update Windows and your GPU/system drivers.
  • Run the launcher as administrator and start the game directly from it.

If it still happens, let us know if it’s consistent or tied to specific actions right after spawn.

Sources:

#

SAND has two modes:

  • Voyage: lower-stakes, persistent open world with no time limit—you choose when to extract.
  • Storm Dive: action-focused, battle-royale style; limited by the Sandstorm moving to the center, but you can extract any time before that.

Team options:

  • Play solo or in crews of 2–6 (max crew size is 6; ensure your trampler has enough crew rooms).
  • Matchmaking is based on your crew size.

Server population caps:

  • Solos: up to 15 players per server.
  • Small teams (2–3 players): up to 36 players.
  • Large teams (4–6 players): up to 45 players.

Sources:

coral shoalBOT
#

The math part isn’t covered by the info I have. For fixing the game, here are confirmed steps you can try:

  • Invisible/corrupted Trampler props or duplicate crate visuals: Press Win+R → regedit → go to Computer\HKEY_CURRENT_USER\Software\Hologryph\ and delete the Sand folder.
  • Ladder/clipping/stuck issues: Press F; try jumping + crouching; in some cases only respawning helps.
  • Disconnections/long matchmaking: Run the game as Admin; press F11 to view ping; switch servers if you hit a disconnect loop; ensure the game is allowed in your firewall/antivirus; prefer wired; if no match after ~15 min, restart the client and ensure an expedition is planned and a Trampler is selected.
  • BattlEye/launch problems: Verify game files; reinstall BattlEye via Install_BattlEye.bat in the game folder; update Windows and GPU drivers; run the launcher as admin; try installing the game on the OS drive; disable overlays/background software. On Linux/Steam Deck, install the Proton BattlEye Runtime.
  • General tips: Ensure your PC meets minimum requirements; update Windows/GPU drivers; lower graphics for long loading times.

Sources:

coral shoalBOT
#

Hey! I am looking this up for you, I will update this message shortly

worthy parrot
coral shoalBOT
# worthy parrot when you back with response? how to set launch options to generate log file?

We don’t have information about response times.

For logs: there aren’t steps here for launch options to generate them, but you can collect the existing logs from your PC at:
%USERPROFILE%\AppData\LocalLow\Hologryph\SAND
Files: player.log and player-prev.log

If you’re troubleshooting an issue, share those two files along with a brief description of what happened.

Sources:

#

There isn’t a documented Steam launch option like “-log.” The game’s logs are expected at:
%USERPROFILE%\AppData\LocalLow\Hologryph\SAND
as player.log and player-prev.log. For technical assistance, those are the files referenced. General steps you can try if you’re troubleshooting: ensure your PC meets the minimum requirements, update GPU drivers and Windows, verify game file integrity, and (on Linux/Steam Deck) install the Proton BattlEye Runtime from your Steam library.

Sources:

#

The snippet only shows the engine initializing (no error yet). If the game hangs or crashes after this point, please try:

  • Verify game file integrity (Steam).
  • Update your GPU drivers and Windows.
  • Ensure your PC meets the minimum hardware requirements.
  • If load times are very long, lower graphics settings.
  • On Linux/Steam Deck: install the Proton BattlEye Runtime from your Steam library.

If it still happens, please share more details and attach your logs so we can check what happens after “Initializing input”:

  • Files: %USERPROFILE%\AppData\LocalLow\Hologryph\SAND\player.log and player-prev.log
  • Describe the exact behavior (freeze, crash to desktop, black screen, etc.) and the steps to reproduce.
  • For disconnects/crashes/missing Tramplers/inventory issues, also include: your 17-digit SteamID, approximate time, whether it happened on the Trampler or outside, and if you used a custom or default Trampler.

Sources:

#

This one’s beyond my AI brainpower, but no worries—our support team will take a closer look! Let me know if you have any extra details; every bit helps!

#

Hey! I am looking this up for you, I will update this message shortly