Counter-Strike 2 operators against an orange and gray background
Back to all games

Counter-Strike 2

In Counter-Strike 2, clear sightlines and consistent frame times matter in every duel. Compare 2K direct-play FPS and 1% lows, then use the tested graphics settings to configure the native Linux version.

Device
Runs wellLast tested Sep 29, 2026

Measured performance

Compare average FPS and 1% lows at each tested resolution.

323.4Average game FPS, 2K direct
111.51% low game FPS, 2K direct
Play modeResolutionOverlay gatewayAvg. FPS1% low FPS
Direct play2560 × 1440Off323.4111.5
Direct play2560 × 1440On283.796.7

Recommended settings

SettingsDirect 2K
Resolution2560 × 1440
Graphics presetCustom (based on Balanced)
Overlay gatewayOff
Runtimenative Linux
VSyncOff
Tested frame-rate limitUnlimited (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.

Graphics settings
SettingTested value
MSAA anti-aliasing4×
Shadow qualityMedium
Dynamic shadowsOn
Texture detailMedium
Particle detailHigh
Ambient occlusionOff
NVIDIA Reflex (configuration file)On
Texture filtering16× anisotropic
VSyncOff
Tested frame-rate limitUnlimited (fps_max 0)
DLSSUnsupported
Frame generation / ray tracingUnsupported

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

Test sessions
Overlay gatewayTest dateSession durationSteam client version
OffSep 29, 2026150 minutes1790548020
OnSep 23, 2026160 minutes1789781627