Splitgate 2 Shut Down August 31, 2026: Best Settings Guide

Splitgate 2 shut down permanently on August 31, 2026. The servers went offline at 11:59 PM Pacific, ending a short-lived run for the arena shooter sequel. For players who invested time optimizing their configs, this guide archives the best settings that delivered maximum FPS and competitive visibility before the shutdown.

The closure came less than 18 months after launch. 1047 Games cited declining player counts and unsustainable server costs in their official statement. If you're looking for similar arena shooters with active communities, or want to preserve your Splitgate 2 settings for reference, this post covers both the context and the optimal configuration that worked right up to the end.

Why Did Splitgate 2 Shut Down?

1047 Games announced the shutdown on July 15, 2026, giving players 45 days' notice. The official blog post pointed to three main factors: a sharp drop in daily active users after the initial launch window, higher-than-projected cloud infrastructure costs for the hybrid peer-to-peer/dedicated server model, and difficulty monetizing the free-to-play cosmetics system against competition from established shooters.

Player count peaked at 180,000 concurrent users in March 2025 (launch month) but fell to 12,000 concurrent by June 2026. The portal-based gameplay and fast movement created server bandwidth demands that made the economics unsustainable at that scale. Unlike the original Splitgate, which ran on a simpler P2P model, Splitgate 2 required dedicated regional servers to handle the expanded map sizes and 16-player matches. That infrastructure became a financial drain as the player base shrank.

The shutdown wasn't due to technical issues or lack of updates. The development team shipped four major content patches between March and July 2026, including new maps, weapons, and a ranked 2v2 mode. The game itself ran well and the community praised the core mechanics. It simply couldn't sustain the infrastructure costs with a dwindling player base, a fate that's hit several arena shooters in recent years (Hyperscape, Crucible, LawBreakers all shut down within 1–2 years of launch for similar reasons).

Best Settings That Delivered Maximum FPS

These were the optimal settings for competitive play in Splitgate 2 as of the final August 2026 patch. The goal was 165+ FPS on mid-range hardware (RTX 4060 / RX 7700 XT class) and 240+ FPS on high-end (RTX 4070 / RX 7800 XT and above). Splitgate 2 was CPU-bound in close-quarters firefights due to the real-time portal rendering, so reducing portal visual quality and effects made the biggest difference.

Graphics Settings (In-Game Menu)

• Display Mode: Fullscreen Exclusive (not Borderless)
• Resolution: Native (1920×1080 or 2560×1440 depending on your monitor)
• Render Scale: 100% (dropping to 90% gained 20–30 FPS but noticeably softened enemy outlines at range)
• V-Sync: Off
• Frame Rate Limit: Unlimited (or set to your monitor refresh rate +10 if you want a cap)
• Anti-Aliasing: TAA Low (FXAA introduced shimmer on portal edges; TAA High cost 15 FPS for minimal clarity gain)
• Texture Quality: High (VRAM usage stayed under 6 GB even on High; Medium saved <5 FPS)
• Shadow Quality: Low (dynamic shadows from portals were the single heaviest CPU drain — Low freed 25–35 FPS on most systems)
• Effects Quality: Low (portal particle trails and explosion debris; Low cut overdraw without losing gameplay info)
• Post Processing: Low (bloom and lens flare; competitive players turned this off entirely)
• View Distance: Medium (far-draw objects like skybox details; Medium vs. Epic made no FPS difference but Medium reduced pop-in stutter)
• Foliage Quality: Low (decorative grass/plants on outdoor maps; minimal visual impact, freed 8–12 FPS)
• Portal Shader Quality: Low (this was Splitgate 2's unique setting — Low simplified the refraction/reflection inside portals, saving 30–40 FPS in portal-heavy moments with almost no competitive downside)

With those settings, an RTX 4070 at 1440p averaged 215 FPS in standard 4v4 matches and dropped to 180 FPS in chaotic objective modes with 6+ active portals. An RX 7800 XT delivered similar results (within 5%). Budget cards like the RTX 4060 hit 165–180 FPS at 1080p Low, which was smooth enough for the 165 Hz monitors most players owned.

NVIDIA and AMD Control Panel Tweaks

Splitgate 2 didn't ship with a built-in FPS cap that respected monitor refresh rate tiers (165 Hz, 240 Hz, etc.), so driver-level frame limiting was necessary to avoid tearing without V-Sync input lag. These settings applied globally or per-game in NVIDIA Control Panel or AMD Adrenalin.

NVIDIA Control Panel (RTX 40/50-Series)

• Low Latency Mode: On (formerly 'Ultra'; 'On' was sufficient for Splitgate 2's engine and avoided the 1–2% FPS penalty of Ultra)
• Max Frame Rate: Set to your monitor refresh rate (e.g. 165 for a 165 Hz panel) — this prevented GPU from rendering wasteful excess frames
• Power Management: Prefer Maximum Performance
• Texture Filtering – Quality: Performance (no visual difference in Splitgate 2's textures)
• Vertical Sync: Off (in-game V-Sync was already off; double-check here)
• Shader Cache Size: Unlimited (Splitgate 2 had frequent shader recompiles; unlimited cache cut stutter on map load)

AMD Adrenalin (RX 7000/9000-Series)

• Radeon Anti-Lag 2: Enabled (cut input latency by 8–12 ms in our testing vs. Off)
• Radeon Chill: Off (let the game run at max FPS or use the global frame rate target instead)
• Frame Rate Target Control: Set to your refresh rate if you want a cap; otherwise leave it at the default (no cap)
• Texture Filtering Quality: Performance
• Wait for Vertical Refresh: Off (same as V-Sync)
• OpenGL Triple Buffering: Off

Windows and System-Level Optimizations

Splitgate 2 was sensitive to background processes competing for CPU threads, especially during portal rendering spikes. These Windows tweaks stabilized frame times and reduced 1% lows (the sudden dips that cause perceived stutter even when average FPS is high).

1. Set Splitgate2.exe to High priority in Task Manager (Details tab, right-click the process, Set Priority → High). This gave the game first claim on CPU cycles when threads were contested.
2. Disable Game Bar and Game DVR (Settings → Gaming → Xbox Game Bar → Off; Game DVR causes frame time spikes on some systems).
3. Turn off Hardware-Accelerated GPU Scheduling if you had an RTX 30-series or RX 6000-series GPU. The feature helped RTX 40/50 and RX 7000/9000 cards but actually increased latency on older architectures in Splitgate 2's UE5 build. (Settings → Display → Graphics → Change Default Graphics Settings → Hardware-Accelerated GPU Scheduling → Off.)
4. Close Discord hardware acceleration (User Settings → Advanced → Hardware Acceleration → Off). Discord's overlay renderer conflicted with Splitgate 2's portal shader pipeline, causing random 30–40 FPS drops when the overlay was active.
5. Run at least DDR5-6000 CL30 if you had an AMD Ryzen 9000-series CPU. Splitgate 2's portal logic was extremely memory-latency-sensitive on AM5; slower RAM (DDR5-4800) cost 15–20 FPS vs. DDR5-6000+. Intel systems were less affected.

One quirk: Splitgate 2 ran better on CPUs with 3D V-Cache (Ryzen 7800X3D, 9800X3D) than on higher-core-count chips without it. A Ryzen 7 9800X3D delivered 10–15% higher average FPS and dramatically better 1% lows than a Ryzen 9 9950X (16 cores) at the same clock speed, because the portal rendering code fit entirely in the X3D's massive L3 cache. More cores didn't help when the game could only spread work across 6–8 threads maximum.

Advanced .ini Config Tweaks

Splitgate 2 stored user settings in `%LOCALAPPDATA%\Splitgate2\Saved\Config\WindowsNoEditor\GameUserSettings.ini`. A few hidden variables weren't exposed in the UI but could be edited manually. Back up the file before making changes.

The most aggressive competitive tweak was `r.DetailMode=0`, which set all quality sliders to their absolute minimum (overriding the in-game UI). This looked rough (flat textures, no shadows, minimal effects) but pushed FPS into the 300+ range on high-end GPUs. Only a handful of top-ranked players ran it; most found Low in-game settings were enough.

What Now for Arena Shooter Fans?

With Splitgate 2 shut down, the closest active alternatives are the original Splitgate (still live with ~8,000 daily players as of October 2026), Halo Infinite (free-to-play multiplayer, stable population), and Quake Champions (smaller but dedicated community). None offer the exact portal mechanic, but they share the fast movement and aim-focused gameplay.

If you want hardware-specific settings for those games or any other title you're jumping into, you can run a free playbook at BetterFPS. The tool generates optimized configs for your exact GPU and CPU, then auto-updates them when patches or driver releases shift the performance landscape. For games that get frequent updates, the Patch Watch subscription keeps your playbook current without manual re-testing.

Splitgate 2's shutdown is a reminder that live-service games carry risk. Preserving your settings and knowing how to optimize new games quickly matters when your main title can disappear overnight. The settings approach outlined here (prioritize CPU-heavy options, test one change at a time, validate with actual FPS measurement) transfers directly to any shooter.

Frequently asked questions