Troubleshooting
Most trouble shows up on the Play screen as a failing check, and most failing checks say in their own words what is wrong and offer the fix next to it. This section is for the rest: the problems that come from the PC, from Windows, from a game being open, or from a damaged file.
Each page names the symptom as RigReady shows it, the cause, and what to do. Short answers to common questions, such as whether RigReady needs administrator rights or works without DCS, are on Questions and answers.
Reading a failing check
Every check on the Play screen has a summary line and, when you open it, details in plain words. A red item is required and not met: the rig is Not ready. A yellow item is optional and not met: the rig is Ready, with a warning. A check that could not be run at all, for example because the controllers could not be read, says so rather than pretending to fail.
Next to a failing item there is its fix, when RigReady has one (start the app, apply the layout, restore the file), and a re-check. Re-check all runs every check again. Items RigReady cannot fix by itself are listed under Needs you (After the fixes), with what to do. Launch is never blocked by a failing check; it only asks first. See Checks and fixes for every kind of check.
Reporting a problem
When a page here does not solve it, open Configure > Diagnostics, press Copy diagnostics, and paste the result into a report on the project's issues page (the Report a problem link in the About panel). The report has personal details removed; read it first if you like. Say what you did, what you expected, and what happened instead. See diagnostics.
- Game controllers could not be readThe input tester shows a red notice, the Devices page has no controller details, and a DCS bindings check says the controllers could not be read.
- A device is not foundA device check says Not connected although the device is plugged in: it is on another port, a different unit, hidden by HidHide, or was renamed by Windows.
- The monitor layout went back by itselfA layout you applied came back after a countdown, a screen went dark, or RigReady asks at the next start whether to put the earlier monitor layout back.
- RigReady will not write DCS filesBindings, screens, Export.lua, kneeboard pages, restores and undo are refused with "DCS is running", because DCS rewrites those files itself when it exits.
- A setup file cannot be readA setup edited by hand has a YAML error or an invalid value, or the file was made by RigReady 1; what the Setups page shows and how to fix it.
- Start with Windows is offRigReady does not start when you sign in although the setting is on, or the setting refuses to turn on: Windows has it switched off in Task Manager.
- Windows SmartScreen warns about the installerWindows protected your PC appears when the installer runs because the installer is not code-signed; here is how to get past it and how to be sure of the file.
- RigReady will not start, or a data file is damagedWhat RigReady does when it cannot start, when it is already running, and when one of its own files is damaged: nothing is deleted, and the app starts anyway.
- Questions and answers (FAQ)Short answers about administrator rights, what RigReady changes, using it without DCS, several PCs, where the data is, internet use and the licence.