Skip to content

Troubleshooting

GreatDanish1026 edited this page Sep 22, 2026 · 3 revisions

Troubleshooting

This page covers common GameAtlas problems and the first steps to try when something is not working as expected.

GameAtlas interacts with launchers, local game files, hardware information, operating-system APIs, external metadata sources, and platform-specific gaming tools. Because of that, an issue may come from GameAtlas itself, the launcher, the operating system, file permissions, or the selected game.


Start Here

Before investigating a specific issue, try these basic steps:

  1. Close and reopen GameAtlas.
  2. Confirm the game or hardware is visible to the operating system.
  3. Rescan the GameAtlas library.
  4. Restart the relevant launcher.
  5. Verify that the game drive is connected and mounted.
  6. Check that the game has not been manually moved.
  7. Confirm that GameAtlas has permission to access the required files.
  8. Restart the computer after major driver, hardware, or launcher changes.

If the issue continues, use the sections below.

For coordinated analysis, begin with Diagnostics Center. For Linux mod deployment and Nexus download problems, see Linux Mod Manager and Nexus Mods Integration. For capture-provider problems, see Performance Capture.


Game Is Missing

If an installed game does not appear in GameAtlas:

  1. Confirm the game is fully installed.
  2. Check that its launcher is listed in Supported Launchers.
  3. Open the launcher and verify that it still recognizes the installation.
  4. Rescan the GameAtlas library.
  5. Check that the game drive is connected.
  6. Confirm that the installation path has not been manually moved.
  7. Check filesystem permissions.
  8. Add the game manually if automatic detection is not available.

See Game Detection.


Steam Game Is Missing

If a Steam game is not detected:

  1. Confirm Steam shows the game as installed.
  2. Verify the Steam library containing the game still exists.
  3. Confirm the drive is mounted or connected.
  4. Restart Steam.
  5. Rescan GameAtlas.
  6. Check whether the game is installed in an additional Steam library.

On Linux, also confirm that GameAtlas can access the Steam library path.


Epic, GOG, Ubisoft, EA, or Xbox Game Is Missing

On Windows:

  1. Open the relevant launcher.
  2. Confirm the game is listed as installed.
  3. Verify the installation path.
  4. Restart the launcher.
  5. Rescan GameAtlas.

If the game was manually moved outside the launcher, detection may fail until the launcher is repaired or the game is added manually.


Heroic Game Is Missing

On Linux:

  1. Open Heroic.
  2. Confirm the game is installed.
  3. Check the configured install path.
  4. Confirm the drive is mounted.
  5. Verify that GameAtlas can access the path.
  6. Restart Heroic.
  7. Rescan GameAtlas.

Also verify that the Heroic configuration has not been moved or reset.


Lutris Game Is Missing

If a Lutris-managed game does not appear:

  1. Confirm Lutris still lists the game.
  2. Check the configured executable and install path.
  3. Confirm the relevant drive or prefix exists.
  4. Verify filesystem permissions.
  5. Restart Lutris.
  6. Rescan GameAtlas.

Duplicate Games

A game may appear more than once if multiple valid installations exist.

Examples include:

  • Steam and GOG copies
  • Steam and Epic copies
  • Multiple editions
  • Native Linux and Proton versions
  • Manual entry plus automatic detection

A duplicate entry does not always indicate a bug.

Check the launcher or installation source shown for each entry.

See Game Detection.


Manual Game Is Not Working Correctly

For manually added games:

  1. Verify the executable still exists.
  2. Confirm the installation path is correct.
  3. Make sure the game has not been moved.
  4. Re-add the game if necessary.
  5. Check whether the selected executable is the actual game executable rather than a launcher or helper process.

Some features may have less information available for manually added games.


Wrong Game Information

If GameAtlas shows information for the wrong title:

  1. Confirm the correct game entry is selected.
  2. Check the detected executable.
  3. Check the launcher source.
  4. Verify the game edition.
  5. Rescan the library.
  6. Report the incorrect match if it persists.

This can be especially important for:

  • Remakes
  • Remasters
  • Collections
  • Definitive Editions
  • Games with similar names

PCGamingWiki Information Is Missing

If PCGamingWiki information does not appear:

  1. Confirm the game is detected correctly.
  2. Check whether the title has a PCGamingWiki page.
  3. Verify the game edition.
  4. Rescan the game.
  5. Confirm internet access is available if the feature requires live lookup.

If GameAtlas matches the wrong page, report the incorrect title match.

See PCGamingWiki.


Cover Artwork Is Missing

If cover artwork does not appear:

  • The game may not have a matching artwork source.
  • The title match may be incomplete.
  • The external metadata request may have failed.
  • The selected game may use an unusual title.

GameAtlas functionality is not affected if cover artwork is unavailable.


RenoDX Support Looks Incorrect

If GameAtlas reports that RenoDX is unavailable for a supported game:

  1. Confirm the game edition.
  2. Verify the title and executable.
  3. Check whether RenoDX supports that exact version.
  4. Rescan or reselect the game.
  5. Report the missing match if the project definitely exists.

If GameAtlas links to the wrong RenoDX project, report the incorrect mapping.

See RenoDX.


Vortex Support Looks Incorrect

If Vortex support is not detected:

  1. Confirm that a Vortex extension exists for the title.
  2. Verify the game edition.
  3. Check whether the extension supports the installed launcher version.
  4. Confirm the executable and title.
  5. Report the missing extension if GameAtlas should detect it.

See Vortex.


Save Location Is Missing

If GameAtlas cannot find save data:

  1. Launch the game at least once.
  2. Create a save.
  3. Exit the game.
  4. Reopen or reselect the game in GameAtlas.
  5. Check whether PCGamingWiki documents the save location.
  6. Verify filesystem permissions.

On Linux, also check whether the save exists inside:

  • A Proton prefix
  • A Wine prefix
  • Steam userdata
  • A launcher-specific directory

See Save Management.


Save Backup Failed

If a backup fails:

  1. Close the game.
  2. Wait for cloud synchronization to finish.
  3. Confirm the save path exists.
  4. Verify that GameAtlas has read access.
  5. Confirm that the backup destination is writable.
  6. Check available disk space.
  7. Try again.

On Linux, permissions on secondary drives can also cause backup failures.


Save Restore Failed

If a restore fails:

  1. Close the game.
  2. Close the launcher if it is actively syncing files.
  3. Confirm the backup still exists.
  4. Verify write access to the save directory.
  5. Confirm sufficient free disk space.
  6. Try the restore again.

After restoring, be careful with cloud synchronization. The launcher may attempt to overwrite the restored files.

See Save Management.


Hardware Information Is Missing

If CPU, GPU, memory, storage, display, or controller information is missing:

  1. Confirm the operating system sees the device.
  2. Restart GameAtlas.
  3. Restart the system after recent hardware changes.
  4. Check relevant drivers.
  5. Verify required system utilities are available.
  6. On Linux, check permissions and device visibility.

See Hardware Detection.


GPU Is Not Detected

If GameAtlas does not show the expected GPU:

  1. Confirm Windows or Linux detects the GPU.
  2. Check graphics drivers.
  3. Restart GameAtlas.
  4. Restart the system.
  5. Confirm the GPU is enabled.
  6. Check whether multiple GPUs are present.

On Linux, verify that the GPU is visible through the active graphics stack.

Incorrect GPU detection can also affect:

  • Performance diagnostics
  • Shader cache tools
  • Driver diagnostics
  • Display information

See Hardware Detection.


Wrong GPU Is Shown

On systems with multiple graphics adapters, GameAtlas may show more than one GPU.

Examples include:

  • Integrated graphics
  • Dedicated graphics
  • Secondary GPUs

This is expected.

If a game is using the wrong adapter, see Performance Diagnostics.


Controller Is Not Detected

If a controller does not appear:

  1. Reconnect it.
  2. Try another USB port.
  3. Test with USB instead of Bluetooth.
  4. Confirm the operating system sees the controller.
  5. Restart GameAtlas.
  6. Check controller drivers or Bluetooth status.

See Controller Detection.


Controller Is Detected but Does Not Work in Game

If GameAtlas sees the controller but the game does not:

  1. Check the game's controller settings.
  2. Review Steam Input settings.
  3. Disconnect extra controllers.
  4. Disable unnecessary controller remappers.
  5. Check for virtual controllers.
  6. Confirm the game supports the controller type.

On Linux, Proton or Wine input translation may also be involved.

See Controller Detection.


Duplicate Controller Inputs

Symptoms can include:

  • Double button presses
  • Menus moving twice
  • One controller appearing as two
  • Unexpected Player 1 assignment

Possible causes include:

  • Steam Input
  • Virtual controllers
  • Controller remapping software
  • Multiple physical controllers

Try disconnecting unnecessary devices and disabling one input translation layer at a time.


Performance Section Looks Wrong

If performance information appears incomplete or incorrect:

  1. Confirm CPU and GPU detection.
  2. Check display resolution and refresh rate.
  3. Verify the selected game is correct.
  4. Restart GameAtlas.
  5. Restart after graphics driver updates.
  6. Check whether the system has multiple GPUs.

See Performance Diagnostics.


Game Is Stuttering

Common causes include:

  • Shader compilation
  • Asset streaming
  • CPU bottlenecks
  • VRAM pressure
  • Slow storage
  • Background overlays
  • Driver changes
  • Wrong GPU usage

Recommended workflow:

  1. Check Clean Launch.
  2. Review Performance Diagnostics.
  3. Determine whether stutter improves over time.
  4. Check shader cache behavior.
  5. Review recent driver or game updates.

See Shader Cache Management.


Low FPS

If performance is unexpectedly low:

  1. Confirm the correct GPU is being used.
  2. Check the display resolution.
  3. Check the refresh rate.
  4. Look for a frame-rate cap.
  5. Check V-Sync.
  6. Review background applications.
  7. Check GPU and CPU utilization with an external monitoring tool if needed.
  8. Review GameAtlas performance warnings.

See Performance Diagnostics.


High FPS but Game Feels Unsmooth

Investigate:

  • Refresh rate
  • Frame-time consistency
  • VRR
  • V-Sync
  • Frame-rate caps
  • Background overlays
  • CPU spikes

Average FPS alone does not guarantee smooth frame delivery.


Clean Launch Does Not Detect an App

If a known overlay or background application is missing:

  • The process name may have changed.
  • The software may have been updated.
  • The overlay may run under another executable.
  • The application may not yet be included in detection rules.

If the software is commonly used for gaming, report it so support can be improved.

See Clean Launch.


Clean Launch Shows an App That Is Not Causing Problems

This is normal.

Clean Launch identifies software that may interact with a game. It does not claim that every detected process is harmful.

Treat the result as a troubleshooting suggestion.


Shader Cache Option Is Missing

A shader cache may not appear if:

  • The game has never been launched.
  • The cache has not yet been created.
  • The GPU vendor uses a different cache location.
  • The driver changed its cache structure.
  • GameAtlas does not support that cache type yet.

This does not necessarily indicate an error.


Game Stutters More After Clearing Shader Cache

This is expected in many cases.

After clearing shader data, the game may need to recompile shaders.

Temporary stuttering may occur until the cache is rebuilt.

See Shader Cache Management.


Windows-Specific Problems

Command Window Flashes Briefly

Background Windows processes should normally run without opening visible console windows.

If a command or PowerShell window flashes while using GameAtlas, report:

  • What action triggered it
  • Which game was selected
  • GameAtlas version

This is a UI bug rather than expected behavior.


Windows Version Looks Wrong

If GameAtlas displays incorrect Windows information:

  1. Restart GameAtlas.
  2. Confirm Windows reports the expected version.
  3. Report the incorrect value if it persists.

Platform-specific labels should not appear incorrectly on Linux.


Graphics Driver Information Is Missing

If driver information is unavailable:

  1. Confirm the GPU is detected.
  2. Verify the graphics driver is installed.
  3. Restart GameAtlas.
  4. Restart Windows after a driver update.

Linux-Specific Problems

Game Drive Is Not Detected

On Linux, confirm:

  1. The drive is mounted.
  2. Your user account can read the drive.
  3. The launcher can access the drive.
  4. GameAtlas can access the mount point.

Common mount locations include:

/run/media/<user>/<drive>
/mnt/games
/var/mnt/games

Clone this wiki locally