Key takeaways
- Improved PSO precaching, so shaders compile earlier and more predictably instead of mid-fight.
- Time slicing, which spreads heavy work such as respawn waves and weapon spawning across several frames.
- Weapon rendering scaling, which shows simplified weapon models for distant or off-screen players.
- A new mesh data format that cut memory use by about 20%.
Most FPS drops in Splitgate 2, now called SPLITGATE: Arena Reloaded, come from shader (PSO) compilation after a game or driver update, the extra rendering cost of portals, laptops running on the wrong GPU or a power-saving plan, and, since the September 3, 2026 switch to player-hosted matches, weak hosts whose hitches look like frame drops. Fix them by letting the shader cache build, keeping Portal Quality and Portal Frame Rate high while cutting shadows, post processing, effects and reflections, capping FPS just under your refresh rate, forcing the high-performance GPU, and hosting or joining lobbies over wired connections.
What changed with Splitgate 2
Splitgate 2 launched on June 6, 2025, went back into beta, and relaunched on December 17, 2025 as SPLITGATE: Arena Reloaded, without factions and abilities. That relaunch shipped with a dedicated performance overhaul from 1047 Games, which matters for anyone following older advice:
- Improved PSO precaching, so shaders compile earlier and more predictably instead of mid-fight.
- Time slicing, which spreads heavy work such as respawn waves and weapon spawning across several frames.
- Weapon rendering scaling, which shows simplified weapon models for distant or off-screen players.
- A new mesh data format that cut memory use by about 20%.
On August 26, 2026, 1047 Games ended active development of the game. On September 3, 2026, dedicated servers and matchmaking shut down and the game moved to peer-to-peer hosting with a server browser. It remains free on Steam, the Epic Games Store, PlayStation and Xbox, but no further performance patches are coming, so the current build is the one to tune.
Check your PC against the requirements
| Component | Minimum | Recommended |
|---|---|---|
| OS | Windows 10 64-bit | Windows 10 or 11 64-bit |
| CPU | Intel Core i3-6100 or i5-2500K, AMD Ryzen 3 1200 | Intel Core i5-6600K or i7-4770, AMD Ryzen 5 1400 |
| Memory | 8 GB | 12 GB |
| GPU | NVIDIA GeForce GTX 1050 | NVIDIA GeForce GTX 1060 or AMD Radeon RX 580 |
| DirectX | Version 11 | Version 11 |
These are modest numbers, so if a mid-range PC drops frames, the cause is usually a setting, the shader cache or the system configuration rather than raw power. Note the 12 GB recommended memory: on an 8 GB system with a browser and voice chat open, Windows paging can cause freezes that look like GPU drops.
Diagnose before you change settings
The game includes additional performance stats in its settings menu that show frame time consistency and hitches. Turn them on and read the pattern rather than the average FPS.
| Pattern | Likely cause | Fix |
|---|---|---|
| Hitches mostly in the first matches after a game or driver update, fading over time | PSO and shader compilation | Play a few full matches; do not clear the shader cache repeatedly |
| Steady low FPS that drops further in portal-heavy fights | GPU limit | Lower the non-portal settings listed below |
| FPS falls to 30 when you alt-tab or click another screen | The built-in 30 FPS lock when the game is unfocused | Expected behavior; click back into the game |
| Laptop runs well on menus but poorly in matches | Integrated GPU or power-saving plan | Force the high-performance GPU and power plan |
| Frame time graph is smooth but players teleport or shots land late | Host or network trouble in a peer-to-peer match | Change lobby or host on wired Ethernet |
Why small hitches feel big
Frame time budget is 1,000 divided by your frame rate: 16.7 ms at 60 FPS, 6.9 ms at 144 FPS and 4.2 ms at 240 FPS. A single 50 ms shader hitch therefore wipes out about three frames at 60 FPS but about seven at 144 FPS, which is why high-refresh players notice compilation stutter more even on faster hardware.
Settings that fix most FPS drops
| Setting | Value | Why |
|---|---|---|
| VSync | Off | Adds input lag; use a frame cap instead |
| FPS Limit | 141 at 144 Hz, 237 at 240 Hz | Trims spiky peaks and keeps variable refresh in range |
| Portal Quality | High | Low values make the view through portals hard to read |
| Portal Frame Rate | High | Low values make movement through portals look choppy |
| View Distance Quality | High | Helps you spot distant enemies at modest cost |
| Shadow Quality | Low | One of the bigger GPU costs |
| Post Processing Quality | Low | Frees GPU time with little gameplay impact |
| Visual Effect Quality | Low | Reduces spikes during explosions and respawn waves |
| Reflection Quality | Low | Little benefit in arena fights |
| Texture Quality | Medium, or High with 6 GB of VRAM or more | Cheap when it fits in VRAM |
| Super Resolution Method | DLSS or FSR in Quality mode if GPU-limited | Renders fewer pixels and upscales |
| Frame Generation Method | None | Adds latency in a fast arena shooter |
| Low Latency Method | NVIDIA Reflex On + Boost, or AMD Anti-Lag | Keeps the render queue short when the GPU is busy |
Portals are the special case. Each open portal shows another view of the map that has to be rendered alongside your own, so lowering Portal Quality and Portal Frame Rate does raise FPS, but it degrades the information the game is built around. Lower them only as a last resort on minimum-spec GPUs such as the GTX 1050, after everything else is already on Low.
System fixes
- Force the right GPU. The official support site has a dedicated article for the game not using the correct GPU. In Windows, open Settings, System, Display, Graphics, add the game and choose High performance.
- Use a performance power plan. Laptops often default to power-saving modes that hold back both CPU and GPU clocks; plug in and choose the best-performance mode.
- Give the shader cache room. In the NVIDIA Control Panel, set Shader Cache Size to 10 GB or larger so compiled shaders are not evicted between sessions.
- Reinstall the driver cleanly if hitching began after an update, then allow a few matches for precaching to finish.
- Try 1000 Hz on the mouse. Players have reported that very high polling rates (4000 to 8000 Hz) caused stutter in this game, and 1000 Hz is only a 1 ms reporting interval.
- Trim overlays and background recording, which compete for CPU time with an Unreal Engine 5 game.
Peer-to-peer matches: drops that are not your GPU
Since September 3, 2026, one player hosts each match and acts as the server, and other players join through the server browser. That changes troubleshooting in two ways. If you host, your PC runs the match for everyone in addition to rendering your own view, so cap your frame rate instead of running uncapped to leave CPU headroom, use wired Ethernet, and pause uploads and cloud syncing. If you join, a weak host can cause rubber-banding, delayed hits or sudden match endings when the host leaves, and none of that shows up as a frame time spike. When your performance stats look smooth but the match feels broken, switch lobbies rather than lowering graphics settings.
