Collect diagnostics
Capture terminal output, identify the active backend and report reproducible failures.
Capture a launch
Run from the repository root in a Bash terminal:
For an X11/XWayland comparison, use a separate file:
The application logs to the terminal. tee displays the output and saves a copy owned by your shell user. These commands start the live application, so CS2 and the required display and device permissions must be available.
Reproduce the problem once, then close the application. Keep the startup output and the first error, together with the messages immediately around the failure.
Enable relevant diagnostics
In Debug, find Debug Diagnostics:
| Control | Use |
|---|---|
| Debug Game Reader | Reader state, packet processing and reader-specific diagnostic output. |
| Timings | Per-section GPU measurements and pipeline timing output. |
| Debug Visibility | Additional entity and grenade visibility diagnostics. |
| CS2 Focus Check | Controls whether unfocused CS2 suppresses game rendering and synthetic input. |
Enable only the diagnostics needed for the problem, then return focus to CS2. Packet and timing summaries appear periodically while frames arrive. The focus gate can prevent the usual game-frame summaries while another window is active.
Some timing messages retain labels such as Bridge active or IPC Read Time. They describe the internal snapshot path. The current executable does not provide a shared-memory simulation backend.
Under Memory Reader Thread Tuning, note the EST and ACT rates. The Offsets status summarizes the startup refresh. Hover it to inspect reported warnings and errors.
Record the conditions
Include these details with the relevant log excerpt:
- The revision from
git rev-parse --short HEADand whether local changes were present. - The failing feature, the expected behavior and the shortest sequence that reproduces it.
- Whether the command used
--x11and which backend the startup log selected. - Desktop or compositor, monitor selection, resolution, refresh rate, desktop scale and game resolution.
- Active GPU, Preferred GPU, Target FPS, VSync and enabled rendering effects for performance problems.
- Profile name, relevant settings, file overrides and the result of validating the specific profile file.
- Whether CS2 was focused and whether CS2 Focus Check was enabled.
Include a screenshot when alignment or appearance is the problem. Check log excerpts and screenshots for account names, home-directory paths or other personal details before sharing them.
Narrow the failure
| Symptom | Focused check |
|---|---|
| Overlay disappears after opening another window | Focus and shortcuts. |
| Missing player models or map geometry | Game assets, plus the first archive-loading error. |
| Misalignment or blur | Display scaling, using the same scene on both backends. |
| Low FPS or uneven updates | Performance tuning, plus timings and reader ACT rates. |
| Wrong settings after launch | Manage profiles, including startup selection and overrides. |
| Radar fails to start or update | Web radar, including status and both ports. |
Turn diagnostic switches off after collecting the report. Save the profile only if you want those switches enabled on the next launch.
Was this page helpful?