Repository navigation
Diagnostics Center
The Diagnostics Center coordinates GameAtlas's game, system, launch, configuration, and performance troubleshooting tools in one workflow.
Available checks depend on the operating system, selected game, launcher, installation metadata, and optional utilities installed on the system.
GameAtlas 2.4 can surface:
- Display and refresh-rate validation.
- Crash evidence and recent failure context.
- Runtime and redistributable dependencies.
- Configuration-file validation.
- Mod conflicts and suspicious DLLs.
- Launch-failure evidence.
- Background applications, overlays, capture tools, and injectors.
- Shader-cache locations and state.
- Graphics-driver and GPU-selection context.
- CPU, GPU, VRAM, memory, storage, and frame-pacing indicators.
- Controller and virtual-device conflicts.
- Proton runtime, prefix, environment, and compatibility information on Linux.
- Fully exit the affected game.
- Select the correct installation in GameAtlas.
- Run the relevant read-only checks first.
- Review evidence, severity, scope, and recommended next steps.
- Make one reversible change at a time.
- Relaunch and reproduce the same scenario.
- Re-run the check to compare the result.
Detected evidence is not proof of the root cause. A running overlay, unusual DLL, old log entry, or missing optional component can be harmless for a particular game.
Some maintenance tools can modify configuration, caches, launch options, prefixes, saves, or deployed mods. GameAtlas separates those operations from analysis and provides previews, confirmations, backups, or rollback information where supported.
Close the game and any launcher process actively writing the same data before using a repair or restore operation.
Support bundles are generated locally and are never uploaded automatically. Review the export before sharing it because it can describe installed software, hardware, processes, game names, and local paths.
See Privacy and Security.