Find your next step
The game will not start
Start with the game update and any graphics-driver warning shown at launch.
- Restart the game, then restart your PC or console if the problem continues. Install available game and system updates.
- If startup asks for a newer graphics driver, update it using your GPU manufacturer’s driver installer. The game checks its minimum driver requirement when it starts.
- Allow extra time on the first launch after a required graphics-driver update: the shader cache rebuild can make this launch take longer.
- On Steam, open Library, right-click Galactic Racer, then choose Properties → Installed Files → Verify integrity of game files.
- For your first PC launch, connect to the internet for authentication. If it still fails, record the exact warning and the point where startup stops.
RTX 50-series crashes with DLSS and Frame Generation
If the crash happens with DLSS and Frame Generation enabled, keep those setting details in your report.
- Install the available game update and check for a graphics-driver update. If a graphics-driver update was required, allow the next launch to rebuild the shader cache.
- Record your exact GPU model, driver version, and whether DLSS and Frame Generation are enabled.
- As an optional comparison, one player reported fewer crashes with both DLSS and Frame Generation off, but also rougher hub performance. This is not a confirmed fix. Change one setting at a time where possible, record the trade-off, and restore your preferred settings if it does not help.
- If the crash repeats, note the mode and scene where it happens. Add the exact error and any steps you have already tried to your support report.
A race, countdown or Tour closes the game
Player reports describe different crash points and hardware; they do not establish one cause or a universal setting change.
- Install available game and system updates. On Steam, verify the installed game files if the crash continues.
- Record the exact point: countdown, track loading, mid-race, results, paddock or another menu. Add the mode, track, vehicle and how long the game had been running.
- On PC, note the GPU and driver version and whether DLSS or Frame Generation is enabled. Change one setting at a time only if you choose to test; several reports persist with those options off.
- For stuttering that continues after settings and driver checks, fully restart the game and PC once, then compare the same track and session length. A Reddit reply suggested this for one long-running session; it is not an established remedy.
- If the crash risks ending a long Campaign or Multiplayer Tour, do not keep repeating that run just to reproduce it. Record what happened and contact support.
- Use the report builder below to include the time, session length, last screen and any error message.
The game closes near the finish or results screen
A recent PC report describes repeat crashes around the finish camera; replies do not confirm that the camera is the cause.
- Record whether the game closes before the finish line, during the finish camera transition, while the results screen appears, or later. Note the track, mode, vehicle, race number and whether the same point repeats.
- If the game remains open, capture the last screen or any error. Record the GPU, driver, game version and graphics settings; lowering all settings did not help one player, so do not treat low settings as a confirmed fix.
- Check for game and system updates. On Steam, verify the installed files. Avoid changing several settings at once so a repeat test remains useful.
- If the crash repeats, stop risking a long Campaign or Multiplayer Tour just to reproduce it. Include the finish or results transition and previous race count in the support report.
The game says Wrong Way or changes your place unexpectedly
A few players describe a sudden place change or elimination near a collision, lap line or camera transition. Reports do not establish one cause.
- If the game is still running, capture a short clip showing the track, lap line, position indicator and any camera transition. Note the track, mode, lap and vehicle.
- For one Reddit report, a reply suggested disabling the kill camera after it appeared to redirect the vehicle into a wall. Treat this as a single-player suggestion, not a confirmed fix; test it only if the same camera-triggered behavior repeats.
- If the place or Wrong Way warning changes without a clear route error, record the exact moment and whether it happened at a lap line, jump or collision. Do not assume a displayed place change proves the race result was recalculated correctly.
- If the race ends incorrectly again, include the clip, game version, platform, mode and track in a support report. Avoid repeating a long Campaign run solely to reproduce it.
Fullscreen flickers or hangs when switching apps
Switching focus while using Fullscreen can make the monitor blink and the system unresponsive.
- Close and relaunch the game session. Restart your PC if it remains unresponsive.
- Check that the game and system are updated. On Steam, verify the installed game files.
- Record the Display Mode and whether the problem starts when you switch to another app. Include that trigger in your report rather than describing it only as a crash.
Steam Deck hangs when the EOS overlay opens
The Epic Online Services overlay may be invisible on Steam Deck, making the game appear to hang.
- Press B to cancel the overlay and return to the game.
- If B does not return you to the game, restart the game session and check for game and system updates.
- If the problem continues, record what opened the overlay and whether pressing B had any effect.
Campaign crashes during a conversation or cutscene
The exact conversation, scene and crash point help narrow down a recurring campaign problem.
- Restart the game and your device, then check for game and system updates. On Steam, verify the installed files.
- Record the act, planet, character or menu you approached, and whether the crash happened before, during or after the conversation.
- Note whether other modes work and whether the same scene crashes every time. Keep any error message or short video of the problem.
- Use the report below to contact support. Include your existing progress and any progress that disappeared after the crash.
Campaign or Log Book progress disappeared
The developers list save-file corruption as a known issue and note that the game may not warn you when it happens. Player reports describe progress loss after crashes; those reports do not establish the cause or a guaranteed recovery method.
- Before changing anything, check that you launched the same platform account and game profile you used before. Do not delete, reset, or replace save files while the cause is unclear.
- If a cloud-save conflict appears, avoid choosing an overwrite option until you have preserved the current local and cloud copies or received platform support guidance.
- Record when the progress disappeared, what happened immediately beforehand, and which items are missing: Campaign, Log Book, Arcade results, unlocks, or more than one.
- Use the support report below and include the platform, recent crash details, affected progress, and any cloud-sync message. Recovery depends on the platform and available backups; no restore is guaranteed.
An online race shows a connection error
Read the exact GR code before retrying the queue.
- GR-01-06: your game needs an update. Install the update before joining again.
- GR-06-06: your game mode differs from the party leader’s. Choose the same mode before queueing.
- GR-06-23: too many matchmaking requests were made. Pause repeated attempts before trying again.
- For a different code, restart the game session and check for game and system updates. On Steam, verify the installed files.
- If the error continues, include the complete code, platform and race mode in a support report.
Back up your existing save before attempting recovery. Avoid deleting or replacing it as a first troubleshooting step.
Prepare a support report
Describe the problem, copy your report, then paste it into the support form. Your entries stay in this page; nothing is sent from here.
Wrong-way warnings and sudden place changes
A Reddit clip posted recently shows a player moved from fourth to eleventh and eliminated after a collision, with a Wrong Way warning. Replies suggest the kill camera may have redirected the vehicle, while another player describes a similar lap-line placement problem. These are player reports, not a confirmed cause or fix. Use the Wrong Way and race-position steps to capture the route, lap line and camera behavior, then report a repeat through official support.
After the latest stability updates
The official quality-of-life update specifically lists party stability fixes, a PS5 connection fix and an AMD Frame Interpolation crash fix. The launch-period hotfix separately lists general stability fixes and directs continuing problems to Customer Support. Neither note identifies a fix for every crash, GPU, save or campaign issue. The developer’s known-issues post still lists NVIDIA 50-series crashes with Frame Generation and DLSS. An earlier graphics update separately says it made stability fixes to DLSS options, without saying every listed case is resolved.
| Update or player report | What it tells you | What it does not confirm |
|---|---|---|
| Earlier graphics update | Raises the minimum graphics driver checked at boot and adds stability fixes to DLSS options. | It does not say every RTX 50-series Frame Generation crash is fixed. |
| Latest stability hotfix | General stability fixes; contact support if problems continue. | It does not identify which crash, GPU, save or campaign issue changed. |
| Recent player reports | Replies describe crashes at countdown, mid-race, in menus and at the start of a multiplayer Gauntlet; others report few or no crashes. | Different player reports do not establish one cause, a universal fix or a confirmed regression. |
If you use an NVIDIA 50-series card with DLSS and Frame Generation and the crash repeats, try one run with Frame Generation off, then record whether DLSS is on and which game version, driver, mode and scene you used. Recent player posts also describe a multiplayer Tour crash after a vehicle wreck, but this does not show that a normal in-game wreck causes the application to close on other systems. When the process closes, note whether the vehicle had just wrecked and the last screen shown. Record the approximate local time and timezone, graphics driver, and how long the game had been running; the official support form asks for the time and the mode, track or menu where the issue occurs.
If the game crashes after you pause, note how long the session ran and whether the crash happened in the pause menu or after resuming; this is one player's report, not a confirmed pause-specific bug. Record the game version, platform, GPU and driver, exact symptom, and steps that reproduce it. Keep your campaign and Log Book details in the report if progress is affected. Before changing cloud-save sync or deleting local data, contact support; a player’s report describes a cloud save being overwritten after progress loss, not a verified recovery method. Use the symptom checker above, then send diagnostics through official customer support.
