Report a Bug

Step 1 of 4

Gather your evidence

Before you write a single word of your report, collect four things. It takes about five minutes, and it is the difference between a bug that gets fixed and one that gets closed for lack of detail.

1. Find your build number

The build number tells developers the exact copy of the game you were running. Without it, they may test the wrong version and never see your bug.

Open the RSI Launcher. The version is shown under the big Launch Game button. Write it down, or keep the Launcher open so you can copy it later. Official RSI support article

Screenshot: The RSI Launcher with the version number under the Launch Game button

Annotate: circle the build number; caption 'write this down'

01-launcher-build-number.png

2. Find your Game.log file

The Game.log is a text file the game writes while you play. It records what loaded, what you did, and any errors. It is one of the most useful things you can attach. Official RSI support article

You will find it in your install folder. The default path is:

...\Roberts Space Industries\StarCitizen\LIVE\Game.log

Replace LIVE with PTU if your bug happened on the test build. Copy the file somewhere easy to find, like your Desktop, so you can attach it later.

Screenshot: File Explorer open at the StarCitizen LIVE folder with Game.log selected

Annotate: highlight the address bar and the Game.log file

02-game-folder-path.png

The game keeps backups of recent logs too. They are named by build number and date, so an older one may match the session your bug happened in.

Screenshot: The folder showing backup logs named by build number and date

Annotate: arrow to the build-number/date naming pattern

03-game-log-backups.png

3. Save a DxDiag report

A DxDiag report lists your computer’s parts and drivers. Some bugs only happen on certain hardware, so developers ask for this. It is a required part of a full report. Official RSI support article

  1. Press the Windows key and R together to open the Run box.
  2. Type dxdiag and select OK.
  3. Wait for the bar at the bottom to fill. This takes a few seconds.
  4. Select Save All Information and save the file somewhere easy, like your Desktop.

Screenshot: The Windows Run box with dxdiag typed in

Annotate: circle the OK button

04-run-dxdiag.png

Screenshot: The DirectX Diagnostic Tool with the Save All Information button

Annotate: circle Save All Information

05-dxdiag-saveall.png

Screenshot: The saved DxDiag text file on the Desktop

Annotate: caption 'you'll attach this file'

06-dxdiag-saved.png

4. Capture a screenshot or short video

A picture shows what words cannot. A screenshot or a short clip of the bug gives developers context they can trust. Official RSI support article

For a still image, the Windows shortcut Win + PrtScn saves a screenshot to your Pictures folder. Aim to show the bug and enough of the scene around it to make the location clear.

Screenshot: A good evidence screenshot: the bug clearly visible with its surroundings

Annotate: caption what makes this a good shot

07-screenshot-example.png

For anything involving movement or timing, a video is better. The built-in Windows Game Bar (Win + G) can record a short clip. Upload it somewhere public and link it in your report.

Screenshot: A single frame from a short clip of the bug in motion

Annotate: caption 'video beats a still for movement bugs'

08-evidence-video-frame.png

Your evidence checklist

  • ✓ Build number, written down or copied
  • ✓ Game.log file, saved somewhere easy to find
  • ✓ DxDiag report, saved as a text file
  • ✓ A screenshot or short video of the bug

Have all four? You are ready to search the Issue Council and make sure no one has reported it already.