Logitech Wheelbases
Logitech wheelbase users must also disable the iRacing simulator’s support for TrueForce. To do this, edit the iRacing app.ini file which is located in your documents iRacing folder, and find and replace loadTrueForceAPI=1 with loadTrueForceAPI=0 and save.
Loss of FFB
If you are experiencing issues with the FFB going away, iRacing might be trying to steal back the FFB. To stop that from happening, you can edit the iRacing app.ini file which is located in your documents iRacing folder, and find and replace resetWhenFFBLost=1 with resetWhenFFBLost=0 and save.
App Crashes
If MAIRA crashes or behaves unexpectedly, the most helpful thing you can do is grab the log file. Every time it runs, MAIRA writes a new log file to Documents\MAIRA\Logs, named after the date and time it started (for example MAIRA – 2026-07-04 14-30-15.log). Grab the most recent one — it records what the app was doing leading up to a problem, so it is usually the fastest way to figure out what went wrong. MAIRA keeps the last 7 days of logs and removes older ones automatically.
When you report a crash, please attach this log file. If you can, reproduce the crash first and then grab the log right afterward, so it captures the failure.
You can report crashes (and anything else) on the Discord Server or on the iRacing Forum. Including the log file with your report makes it much easier to diagnose and fix the issue.
Main Window Off-Screen
If the MAIRA window ever ends up off-screen — usually after changing your monitor layout or display scaling — MAIRA recovers it automatically: at startup, and whenever Windows reports a display configuration change, it checks that the window’s title bar is still reachable and recenters the window on your primary display if it is not. If you ever need to force it, enable Minimize to system tray in the app settings, then right-click the MAIRA tray icon and choose Reset window position.
Settings Backups and Recovery
MAIRA saves everything you configure to Settings.xml in its Documents folder, and keeps two kinds of backup beside it. Every time it saves, it first copies the previous settings file to Settings.xml.bak. On top of that, it keeps a folder of timestamped backups in a Backups sub-folder, each one named after the date and time it was taken (for example Settings 2026-07-04 14-30-15.xml). The Open documents folder button on the App Settings page takes you straight there.
The first save after each app launch always makes a fresh timestamped backup, and after that at most one every 15 minutes — so you end up with a trail of snapshots going back over many sessions rather than dozens of copies of the same one. MAIRA keeps the newest 50 and deletes the rest. Anything else you put in that folder is left alone.
If the settings file is ever damaged — a power cut in the middle of a save, for example — MAIRA repairs itself at startup without asking. It tries Settings.xml first, then Settings.xml.bak, then the timestamped backups newest first, and carries on with whichever one loads. It writes down what it did in the log file, so if your settings ever look like they jumped back in time, the log will tell you which backup they came from.
You can also do it by hand. Close MAIRA, copy the backup you want out of the Backups folder over Settings.xml, and start MAIRA again.
Controlled Folder Access
If you have turned on Windows’ controlled folder access feature (part of ransomware protection in Windows Security), Windows can block the installer from creating the Documents\MAIRA folder, and block MAIRA from saving your settings and writing its log files. If MAIRA seems to forget your settings between runs, if there are no log files, or if the MAIRA folder never shows up in your Documents folder, this is the most likely cause. See the Downloading and Installing page for how to let MAIRA through.
Previous page: Graph
Next page: Wheel Force Settings