Performance reports

If the game runs badly on your computer, /diagnose records a few minutes of measurements and lets you read the report before deciding whether to send it.

Nothing is recorded until you ask, and nothing leaves your computer until you press Send.

Making a report

  1. Go to where the game runs badly — the busy town, the crowded map, the fight.
  2. Type /diagnose in the chat and press Enter. The game says it is recording, and a small badge at the top of the screen counts down. The command is not sent to the server and nobody else sees it, though it shows in your own chat.
  3. Play as you normally would. It records for five minutes; /diagnose 10 records for ten, up to fifteen. /diagnose stop finishes early.
  4. When it finishes, a window shows what the report found, lists what it holds, and gives its size. Press Send, or Don't send. Enter presses whichever button has the focus, and the focus starts on Don't send.

Either way, the report is saved in your game folder as a realms-diagnostics-….json file named with the date and time. It is plain text: open it in Notepad to read every word. If you change your mind, or the game could not send it, upload the file on the upload page.

If the game runs under ten frames a second for several seconds, it tells you once that /diagnose exists. That message sends nothing. To turn it off, add this to realms-graphics.ini in your game folder:

[Diagnostics]
DiagnoseHint=0

When the game will not start

Run the launcher, ConquerRealmsLauncher.exe, and press Send diagnostics in its top corner. A shortcut to ConquerRealmsLauncher.exe --diagnostics opens only that window, without updating or starting the game.

It saves a report about your computer and the game folder — with no recording, since the game never ran. Press Open the upload page: it opens the page and shows the file in Explorer. Sign in on the website as usual and choose the file there. The launcher never sends anything itself.

What is in a report

Part What it is
Frame times How long every frame took, the slowest twenty and what was drawn in each, and a row for every second
Where the time goes How long a frame spends drawing, waiting for the graphics card, on text, the map and interface, loading textures, posing animated models, and lighting
Which part of the game was running About 500 times a second, which part of the game's own code was running — or of Windows or the graphics driver on its behalf. Nothing from your files, your screen or other programs
Once a second The game's memory use, how busy the processor is, free graphics memory, the game's ping, and how much it sent and received
Your computer Windows version, processor, memory, battery and power plan, graphics cards and drivers, and screens
DirectX The graphics device the game created, and the versions of DirectX, Visual C++ and .NET installed
Files loaded in the game Every program library loaded into the game — this is how an overlay such as Discord, Steam or OBS shows up
Your settings Every .ini file in the game folder and its ini folder; large data tables only by size and checksum
Logs The last 200 lines of realms-connect.log, and the last 40 of realms-loaded.txt

What is never in a report

  • Your password or any sign-in token. A setting whose name mentions an account, user, password, login, token, e-mail or the like has its value replaced with [removed].
  • Your Windows user name and your computer's name, wherever they appear.
  • Your account name. Sending the report tells us which account, character and realm sent it; the account name itself is removed from the text.
  • Where other programs loaded into the game are installed. A file from outside the game folder and Windows is listed by its name and the kind of place it came from, not its full path.
  • Other programs you have open. Only files loaded inside the game are listed.

Reports are kept for 30 days and then deleted. Only staff can read them, and every time a member of staff opens one it is recorded.