| Play mode | Resolution | Overlay gateway | Avg. FPS | 1% low FPS |
|---|---|---|---|---|
| Direct play | 2560 × 1440 | Off | 323.4 | 111.5 |
| Direct play | 2560 × 1440 | On | 283.7 | 96.7 |
Measured performance
Compare average FPS and 1% lows at each tested resolution.
Recommended settings
| Settings | Direct 2K |
|---|---|
| Resolution | 2560 × 1440 |
| Graphics preset | Custom (based on Balanced) |
| Overlay gateway | Off |
| Runtime | native Linux |
| VSync | Off |
| Tested frame-rate limit | Unlimited (fps_max 0) |
Graphics settings
Both gateway configurations used these custom settings, based on the Balanced preset. Graphics values were read from cs2_video.txt. The frame-rate limit was recorded during testing.
| Setting | Tested value |
|---|---|
| MSAA anti-aliasing | 4× |
| Shadow quality | Medium |
| Dynamic shadows | On |
| Texture detail | Medium |
| Particle detail | High |
| Ambient occlusion | Off |
| NVIDIA Reflex (configuration file) | On |
| Texture filtering | 16× anisotropic |
| VSync | Off |
| Tested frame-rate limit | Unlimited (fps_max 0) |
| DLSS | Unsupported |
| Frame generation / ray tracing | Unsupported |
The Reflex entry records the configuration-file value. These tests did not measure input latency or verify whether Reflex was active in the native Linux build.
Frequently asked questions
Should I enable Proton for CS2?
Use the native Linux version. In Steam, open Counter-Strike 2 → Properties → Compatibility and leave “Force the use of a specific Steam Play compatibility tool” unchecked.
Why is only direct play recommended for CS2?
Competitive aiming is sensitive to input delay. Direct play avoids the video encoding, network transit, and decoding stages of streaming. No streaming FPS or latency results were collected for this page.
Should I cap the frame rate at 240 FPS?
Try fps_max 240 as a starting point and adjust it to your display and preferences. The published results used fps_max 0 (unlimited). The 240 FPS cap was not benchmarked.
Which CPU governor should I use?
Keep the Linux CPU governor on its default powersave setting. Forcing performance caused severe frame drops in testing. Restoring powersave resolved them. This is separate from the Olares One power mode, which should remain on Performance.
How do I change the CPU and memory limits for Steam?
In Control Hub, locate the Steam Headless deployment and edit its resource limits. The recommended allocation is 18 CPU cores and 64 GB of memory. Follow the resource-limit section of the guide below. Steam resource-limit guide
Test conditions
- CPU
- —
- GPU
- —
- Memory (GB)
- 96
- VRAM (GB)
- 24
- GPU power limit (W)
- 175
- OS
- Olares OS 1.12.6
- GPU driver
- 595.84.0
- Game version
- —
- Steam chart version
- 1.0.43
- Memory limit (GB)
- 64
- CPU limit
- 18 cores
- Power mode
- Performance
- Last tested
- 2026-09-29
Test sessions
| Overlay gateway | Test date | Session duration | Steam client version |
|---|---|---|---|
| Off | Sep 29, 2026 | 150 minutes | 1790548020 |
| On | Sep 23, 2026 | 160 minutes | 1789781627 |

