Repository navigation
Game Information
Selecting a game in GameAtlas opens the game details view.
This is the main workspace for an individual title. It combines locally detected information with supported external resources, diagnostics, save tools, modding integrations, and platform-specific utilities.
The exact information shown can vary depending on the game, launcher, operating system, and available integrations.
The top of the game details view identifies the selected title and summarizes the most important information.
Depending on the game, this can include:
- Game title
- Cover artwork
- Launcher or installation source
- Install location
- Executable information
- Detected version
Cover artwork helps make the selected game easier to identify visually while keeping the rest of the page focused on useful technical information.
GameAtlas surfaces the local installation information it was able to detect.
This may include:
- Installation folder
- Main executable
- Launcher or store
- Version information
- Local game paths
Installation information is useful for:
- Troubleshooting
- Mod installation
- Finding configuration files
- Locating save data
- Confirming which copy of a game was detected
- Verifying the executable GameAtlas is inspecting
See Game Detection for more information about how games are discovered.
GameAtlas identifies the source of the installation where possible.
Examples include:
- Steam
- Epic Games Launcher
- GOG Galaxy
- Ubisoft Connect
- EA App
- Xbox / Microsoft Store
- Heroic Games Launcher
- Lutris
- Manual installation
This is important because the launcher can affect:
- Installation paths
- Save locations
- Executable access
- Runtime behavior
- Compatibility-layer usage
- Available metadata
See Supported Launchers.
Where possible, GameAtlas identifies the primary executable associated with the game.
Executable information may be used for:
- Version detection
- Launch diagnostics
- Modding support
- Performance inspection
- Local path access
- Game-specific tooling
Some games contain multiple executables, including:
- Launchers
- Anti-cheat executables
- Benchmark tools
- DirectX 11 and DirectX 12 variants
- Helper applications
GameAtlas attempts to identify the executable most relevant to the actual game.
For supported games, GameAtlas can display locally detected version information.
The version may come from:
- Executable metadata
- Launcher metadata
- Installed manifests
- Package information
Not every game exposes a useful version number, so this information may not always be available.
GameAtlas can surface PCGamingWiki information for the selected game.
PCGamingWiki is useful for quickly finding technical information such as:
- Save locations
- Configuration file locations
- Known issues
- Fixes and workarounds
- Graphics options
- Input support
- API information
- Compatibility notes
GameAtlas makes this information easier to reach without requiring a separate manual search.
See PCGamingWiki.
For supported titles, GameAtlas checks whether RenoDX support is available.
When support is found, the RenoDX section can provide a direct path to the relevant project or resource.
RenoDX can be especially useful for games where community improvements are available for areas such as:
- HDR
- Color presentation
- Rendering behavior
- Display output
See RenoDX.
GameAtlas can check whether a selected game has a supported Vortex extension.
If a compatible extension is found, GameAtlas surfaces that information in the game details view.
This makes it easier to determine whether the title can be managed through the Vortex mod manager ecosystem.
See Vortex.
When reliable save-location information is available, GameAtlas can provide save-management tools directly from the selected game.
Available workflows can include:
- Detecting save locations
- Creating backups
- Restoring backups
- Managing snapshots
- Opening save locations
- Surfacing related configuration files
Save support depends on the title and operating system.
See Save Management.
GameAtlas can surface configuration-file locations for supported games.
Configuration files may contain settings related to:
- Graphics
- Resolution
- HDR
- Input
- Audio
- Display mode
- Engine options
- User preferences
Having direct access to these locations can make troubleshooting or advanced configuration much easier.
The selected game can use GameAtlas's Clean Launch functionality to help identify background applications that may interfere with gameplay or benchmarking.
GameAtlas may detect software such as:
- Overlays
- Recording tools
- Monitoring utilities
- Communication applications
- Launcher-related background processes
- Other applications that may hook into games
The presence of a detected application does not necessarily mean it is causing a problem.
Clean Launch is intended to highlight software worth considering during troubleshooting.
See Clean Launch.
For supported configurations, GameAtlas can provide shader-cache management tools.
These may be useful when troubleshooting:
- Persistent stuttering
- Graphical corruption
- Shader compilation problems
- Issues after graphics driver updates
- Damaged cached shader data
Shader cache behavior depends on the operating system, GPU vendor, launcher, and game.
GameAtlas can use local system and game information to help diagnose performance problems.
The performance section may consider information such as:
- CPU
- GPU
- VRAM
- System memory
- Storage
- Display refresh rate
- Background applications
- GPU selection
- Runtime environment
Potential issues GameAtlas can help surface include:
- Shader compilation stutter
- CPU bottlenecks
- VRAM pressure
- Slow storage
- Overlay conflicts
- Refresh-rate mismatches
- V-Sync configuration issues
- Wrong-GPU usage
The game details view can make use of hardware information detected by GameAtlas.
This may include:
- CPU
- GPU
- Memory
- Storage
- Displays
- Connected controllers
- Operating system
Hardware information allows GameAtlas to provide more useful context for diagnostics.
See Hardware Detection.
Connected controllers can be displayed as part of the system and game context.
This can help determine whether the operating system recognizes a controller before troubleshooting the game itself.
Controller-related problems can also involve:
- Steam Input
- Multiple active controllers
- Virtual controllers
- DirectInput
- XInput
- SDL
- Proton or Wine
See Controller Detection.
On Windows, the selected game may expose additional information or tools such as:
- Windows executable version metadata
- Registry-derived installation information
- Graphics driver diagnostics
- Windows shader caches
- Windows process inspection
- Xbox / Microsoft Store package context
See Windows.
On Linux, the selected game may expose additional runtime context such as:
- Native Linux vs Windows game
- Proton usage
- Wine context
- Heroic or Lutris source
- Compatibility prefixes
- Linux performance controls
- MangoHud-related options
See Linux.
For Windows games running on Linux, GameAtlas may need to work with both Linux paths and Windows-style paths inside a compatibility prefix.
This can affect:
- Save files
- Configuration files
- AppData
- Documents
- Registry-related data
- Runtime environment
GameAtlas uses the detected launcher and runtime context where possible to make this easier to understand.
Not every section will appear for every game.
Information may be unavailable because:
- The game does not expose it
- The launcher provides limited metadata
- PCGamingWiki has incomplete coverage
- RenoDX support does not exist
- No Vortex extension is available
- Save paths cannot be determined reliably
- The installation is unusual
- File permissions prevent access
- The game is packaged differently from a traditional desktop application
GameAtlas generally avoids showing irrelevant features when no useful information is available.
Two games installed through the same launcher may expose very different amounts of information.
This can depend on:
- Game engine
- Launcher
- Executable structure
- Save system
- Modding support
- PCGamingWiki coverage
- Operating system
- Runtime
- Installation type
A well-documented conventional desktop game may expose far more information than a heavily sandboxed or unusually packaged title.
Games added manually can still use supported GameAtlas features.
The amount of information available depends on what GameAtlas can determine from the executable and local installation.
A manually added title may still support features such as:
- Executable inspection
- Version detection
- PCGamingWiki
- RenoDX detection
- Vortex detection
- Save management
- Diagnostics