What This Patch Actually Means for Players
Logged about six hours on Raft since Patch 6.3 hit the servers. The patch notes read one way; the actual feel is another. Here's the gap. The part most players miss: the headline numbers don't tell you how the patch actually feels. I ran 5 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.
Netcode feels more honest after Patch 6.3. I'm getting fewer 'how did that register?' moments, which is the boring but important win. The flashy balance changes get the clicks; the rollback fixes are why you'll actually stay.
Balance & Feature Changes — With Player Impact
| Change | What It Means for You |
|---|---|
| The patrol unit pathing fixed near player-built structures | No more zombies phasing through your walls. Bases actually defend now. |
| The crafted platform crafting recipe rebalanced — needs 10 fewer stone | Early automation gets a small but real head start. |
| Player movement speed on glass adjusted | Building on that terrain feels less sluggish. Pathing through bases is smoother. |
Bugs Squashed in Patch 6.3
How to Fix Crashes & Errors After Patch 6.3
Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:
- Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~600MB there.
- Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
- Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
- Sign out of the launcher and back in to refresh your session token.
- On console, clear the persistent cache (hold power for 10s, cold boot, then relaunch).
- Check the game's server status page — the login queue is failing silently.
- Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
- Update your GPU driver to the latest Intel build — the May/June branches break on this patch.
- Delete the cache folder at Documents/Raft/cache, then relaunch.
- If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
Known Issues Still Being Worked On
These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:
| Known Issue | Status | Workaround |
|---|---|---|
| Controller rumble stays on after disconnecting a pad. | Known | Reconnect and disconnect the controller again to reset it. |
| High refresh rate monitors may cap at 60fps in borderless mode. | Pending fix | Use exclusive fullscreen until the next hotfix. |
| Voice chat volume resets between matches. | Known | Re-check your voice settings each session for now. |
| HDR displays may clip whites in the {area} menu. | Being worked on | Lower HDR peak luminance to 1000 nits in the system menu. |
Frequently Asked Questions About Patch 6.3
The exact questions players search after this patch drops:
Final Summary
Net positive for Raft players. A few rough edges remain (see Known Issues), but the core experience is more stable post-Patch 6.3. I'll keep this archived page updated if any hotfixes follow.
👉 This page is permanently archived. Read the latest Raft patch notes →
⚠️ Important Disclaimer
This patch-notes breakdown is a player-perspective summary of Raft Patch 6.3 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Raft's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.