Farever Performance Fix
The Farever Early Access build has three common performance issues: first-launch shader compilation stutter, GPU-bound FPS drops in 4-player dungeons, and rare client crashes on Alt-Tab. All three have known fixes.
Fix first-launch stutter (shader compilation)
On first launch, Farever compiles shaders for ~3–5 minutes. If you alt-tab or play immediately, the compile job pauses and you will stutter for hours. Fix: launch the game, leave it at the main menu for 5 minutes without touching it, then play. This is a one-time cost per driver update.
Fix FPS drops in 4-player dungeons
The streaming system is the bottleneck, not the GPU. Lower Texture Streaming from High → Medium and Shadows from High → Medium. Cap FPS at 60 if your monitor is 60Hz — uncapped 120+ FPS triggers thermal throttling on most GPUs and ironically averages lower FPS.
Fix Alt-Tab crash
A known EA bug: alt-tabbing during a loading screen crashes the client ~30% of the time. Workaround: run Farever in Borderless Windowed mode (Settings → Display → Window Mode → Borderless) instead of Fullscreen. Shiro Games has this on the patch list.
Fix audio crackle
A minority bug on certain Realtek drivers. Fix: Windows Sound Settings → Output Device → Properties → set to 48000Hz 24-bit. Resolves ~90% of reports.
Best low-end settings
Resolution scale 80% · FSR 2.0 Quality · Texture streaming Low · Shadows Low · Foliage Medium · Effects Medium. Hits 60 FPS on a GTX 1060 / RX 580 class GPU.
When to file a bug report
If you have done all of the above and still see issues, file via the in-game F1 → Report Bug menu. Include your DxDiag (Win+R → dxdiag → Save Information) and the latest Farever log from %appdata%/Shiro/Farever/Logs/. The dev team triages community reports every Thursday.
Related
Browse the full Walkthroughs & Quests hub, or return to the Farever wiki home.