What This Patch Actually Means for Players
Quick reality check on Rogue Company Patch 3.5: some fixes land clean, a couple reintroduce old pain. I'll flag both so you're not blindsided. Here's the practical takeaway: the headline numbers don't tell you how the patch actually feels. I ran 4 hours across 4 sessions on PC and a couple of these changes ripple further than the notes suggest.
Netcode feels more honest after Patch 3.5. 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 vanguard hero ability cooldown increased by 8s | Main players should pre-plan engagements; you can't burn the escape as a panic button anymore. |
| Reload time on the LMG reduced by 1s | Aggressive pushes get a real buff. Worth swapping your secondary if you held off before. |
| The shotgun damage adjusted from 15 to 50 at range | Snipers who relied on the old TTK will need to relearn sightlines — the two-tap window is tighter now. |
| Hit registration on fast-moving targets improved | Tracking feels cleaner in chaos. Less 'I swear I hit him' moments. |
Bugs Squashed in Patch 3.5
How to Fix Crashes & Errors After Patch 3.5
Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:
- Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 3.5.
- Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
- Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
- 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/RogueCompany/cache, then relaunch.
- If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
- 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.
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. |
| Some players still see the old the support main/the SMG stats until a full client restart. | Acknowledged | Restart the client after the patch downloads. |
| Cross-save may delay inventory sync by up to 5 minutes. | Investigating | Wait a few minutes before assuming items are lost. |
| 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 3.5
The exact questions players search after this patch drops:
Final Summary
Patch 3.5 is a solid, if unglamorous, update for Rogue Company. The crash fixes alone justify the download; the balance tweaks will shake out over the next two weeks of play. Bookmark this page — it stays live as an archived reference even after the next patch drops.
⚠️ Important Disclaimer
This patch-notes breakdown is a player-perspective summary of Rogue Company Patch 3.5 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Rogue Company'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.