Repository navigation
Settings
GameAtlas includes configurable settings that control how the application starts, how certain platform-specific features behave, and how information is presented.
The exact settings available may differ between Windows and Linux because some options only apply to one operating system.
Open the Settings section from the GameAtlas interface to review or change application preferences.
Settings are saved locally and are intended to persist between sessions.
GameAtlas can control which section opens when the application starts.
Depending on the available options, you may be able to choose a default destination such as:
- Game library
- Dashboard
- Settings
- Another supported section
This is useful if you prefer GameAtlas to open directly to the part of the application you use most often.
To change the startup destination:
- Open Settings.
- Find the Startup Destination option.
- Select the section you want GameAtlas to open to.
- Close Settings or continue using the application.
The selected destination will be used on future launches.
Some GameAtlas settings only appear when they are relevant to the current operating system.
For example:
Windows-specific settings may relate to:
- Diagnostics
- Driver-related features
- Windows game detection
- Background process inspection
- Shader cache handling
Linux-specific settings may relate to:
- Linux gaming tools
- Proton or Wine workflows
- Performance utilities
- Runtime integration
- Linux-specific launch behavior
GameAtlas avoids showing settings that do not apply to the current platform.
Game detection behavior may depend on available launcher support and local installation paths.
Settings related to detection can influence how GameAtlas handles:
- Automatic scans
- Manual game entries
- Rescanning
- Additional library locations
- Platform-specific game sources
For more information, see Game Detection.
Games added manually may require local path information.
Depending on the feature set available, GameAtlas may allow configuration of:
- Game executable
- Installation directory
- Game title
- Launcher or source information
Manual entries are useful when a game is not detected automatically.
See Game Detection.
GameAtlas includes performance-related features that may expose configurable options.
Depending on the platform, these can include:
- FPS limiting
- Performance overlays
- Runtime options
- Diagnostic preferences
- Linux performance controls
These options may only appear when the required system tools or runtime support are available.
On Linux, GameAtlas may surface options related to tools such as:
- MangoHud
- FPS limiting
- Runtime environment variables
- Proton or Wine behavior
- Linux gaming performance controls
Availability depends on the current system and installed tools.
See Linux.
Clean Launch is used to identify background applications that may interfere with gaming or benchmarking.
Where configurable, related options may influence:
- Which process categories are inspected
- How detected applications are displayed
- Platform-specific process behavior
See Clean Launch.
Shader cache management may include settings or options that vary by:
- Operating system
- GPU vendor
- Driver
- Game
- Runtime
GameAtlas aims to show only shader cache actions that are relevant to the detected system.
Controller behavior is usually controlled by the operating system, Steam Input, or the game itself rather than GameAtlas.
However, GameAtlas may expose controller-related information or preferences where appropriate.
See Controller Detection.
GameAtlas automatically detects hardware and generally does not require manual hardware configuration.
Detected hardware may include:
- CPU
- GPU
- Memory
- Storage
- Displays
- Controllers
If the detected information is incorrect, see Hardware Detection and Troubleshooting.
GameAtlas settings may also control parts of the application experience such as:
- Startup behavior
- Navigation preferences
- Displayed sections
- Platform-specific UI behavior
The available options may expand as GameAtlas develops.
GameAtlas is designed around a dark interface.
Controls such as:
- Dropdowns
- Select boxes
- Cards
- Menus
should follow the overall dark visual design.
If a control unexpectedly appears with a bright or light background, this is generally a UI issue rather than an intentional setting.
Some system-level changes may require GameAtlas to be restarted before updated information appears.
Examples include:
- Changing GPUs
- Updating graphics drivers
- Connecting a new display
- Installing a new launcher
- Adding a new game library
- Changing controller hardware
Restarting GameAtlas ensures that system information can be detected again.
If GameAtlas provides a reset option for a particular setting or section, use it to return the feature to its default behavior.
For settings without a dedicated reset control, change the option back to the desired default manually.
Avoid deleting configuration files directly unless troubleshooting instructions specifically recommend it.
GameAtlas settings are stored locally on the system.
They are not intended to modify:
- Game files
- Launcher settings
- BIOS settings
- GPU firmware
- Operating system configuration
unless a specific GameAtlas feature clearly indicates that an action will affect external data.
Most GameAtlas settings affect application behavior rather than games themselves.
However, features that involve:
- Save restoration
- Shader cache clearing
- Configuration-file changes
can affect local game data.
These actions should be reviewed carefully before use.
See:
A setting may not appear if:
- It does not apply to the current operating system
- Required hardware is not detected
- A required tool is not installed
- The selected game does not support the feature
- The feature is unavailable on the current platform
GameAtlas generally hides settings that are not relevant.
If a setting does not persist between launches:
- Change the setting again.
- Close GameAtlas normally.
- Reopen the application.
- Confirm the setting was retained.
- Check whether GameAtlas has permission to write its local configuration.
- Review Troubleshooting if the problem continues.
For most users, the default GameAtlas settings should be appropriate.
Change settings when you want to:
- Customize startup behavior
- Enable platform-specific performance options
- Adjust how a feature behaves
- Troubleshoot a specific issue
There is generally no need to change every available setting after installation.