Skip to content

General FAQ

Welcome to the General FAQ! Here you'll find answers to common questions and errors. It is organized into sections to make finding answers easier.

Supported operating systems

Rigs of Rods is officially supported on 64 bit Windows 7 SP1, Windows 8/8.1, Windows 10, and Linux.

Windows XP & Vista are no longer supported as of version 0.4.8 RC5.

32 bit is no longer supported as of version 2020.01.

ChromeOS (Chromebooks), MacOS, and mobile platforms (Android/iOS) are not supported and most likely never will be.

Downloading Rigs of Rods


You can find the latest version on the home page. If you need help, check out the Beginner's Guide.


Linux users can download the latest version from

It is recommended to install using the Itch desktop app.

Development builds

If you want to try the latest changes to RoR, you can download a development build.

Old versions

You can find old RoR versions on SourceForge. These versions are entirely unsupported!


Downloading mods

You can find mods on the Repository, the content section of the forum, and the archives.

For help with installing mods, see this page.


You can find links to the archives here. These contain content from previous versions of the website.


To play multiplayer, see this section of the Beginner's Guide.

Please know that multiplayer is still a work-in-progress, and crashes may happen.

Wrong server version

This means you're trying to join a server that is running an older or newer RoRNet version than what your current RoR version supports.

The latest version, 2022.04, supports RoRNet 2.43.

Errors & glitches

These errors may occur when launching RoR.

No render system plugin available



If you downloaded RoR using the zip file, you may receive these errors. This is caused by the DirectX 9 Runtime not being installed. Install it from Microsoft's website then restart your PC.

MSVCP DLLs missing

When launching RoR, you may receive a MSVCP140.dll/MSVCP110.dll/MSVCP100.dll error.

This is caused by the required Visual C++ x86/x64 Redistributable not being installed.

Install the correct version that matches the .dll name in the error then restart your PC.

When the site asks what version to download, just install both.

Latest release:

Older versions:

Special characters crash (Cannot open controller input map)



This is caused by having Unicode characters in the path to the Documents\My Games\Rigs of Rods folder, usually caused by the Windows username (e.g. Usér).

This will be fixed in a future version. For now, there is a workaround with two methods. Choose the second method if you don't want RoR to run as administrator.

Method 1
  1. Inside the installation directory, where RoR.exe is (usually C:\Program Files\Rigs of Rods) create a folder named config
  2. Right click RoR.exe and click Properties
  3. Under the Compatibility tab, check the Run this program as administrator box, then click Apply and close the window.
Method 2
  1. Move any mods from the Documents\My Games\Rigs of Rods\mods folder if you have any installed
  2. Uninstall RoR from Windows settings, then remove the Documents\My Games\Rigs of Rods folder if required
  3. Download the zipped release from and extract into any directory that isn't in Program Files or the users folder (Documents, Downloads, etc).
    Example: C:\Games
  4. Inside the extracted folder, create a folder named config
  5. Launch the game by double clicking RoR.exe. You can optionally create a shortcut by right clicking.

RoR will now use the config folder instead of the default Documents\My Games\Rigs of Rods folder.

If you installed the content packs, you will have to move the *.zip files from Documents\My Games\Rigs of Rods\mods to config\mods. New mods are also installed there.

Full screen crash (Cannot create device)


This error is usually caused by enabling full screen with the wrong resolution (video mode) set.

  1. Browse to Documents\My Games\Rigs of Rods and delete the config folder inside.
  2. Start RoR, the game will be in a small window. Click Settings -> Render system and change the Video Mode setting to your monitor's native resolution. Enable full screen if you want.
  3. Restart RoR.

If this doesn't fix your error, then your GPU is most likely too old to run RoR.

Null program bound


This error occurs with some Intel integrated graphics chips. Unfortunately there's currently no fix.

More info: GitHub issue

Glitchy vehicle shadows

With some GPUs (mostly integrated ones), shadows on vehicles may appear glitchy:


This is caused by your GPU not supporting self-shadowing (Shadows from other objects casting onto the vehicle). Please try one of the following workarounds:

#1: Disable shadows

The simplest workaround is to just disable shadows. (Settings -> Graphics -> Set shadows to "None" -> Restart RoR).

#2: Enable classic materials

Starting with version 2020.01, an option to enable classic (0.38-era) material shaders is available. This can be found under Settings -> Graphics -> Classic material shaders.

Currently they do not support self-shadowing, so the glitch is not present using these.

#3: Disable self-shadowing from default materials

If you prefer to use the default materials instead, do the following:

  1. Browse to where RoR is installed. This is usually C:\Program Files\Rigs of Rods by default.

  2. Open the resources folder, followed by the managed_materials folder.

  3. Copy the managed_mats_vehicles.material file onto your Desktop.

  4. Open the file with Notepad (Right click -> Open with -> Notepad)

  5. Add // to the beginning of the first line: //import * from "shadows.material"

  6. Save the file, then copy it back to resources\managed_materials, overwriting the original file. Allow administrator permission when prompted.

Airplane spawning crash

If the game crashes when spawning an aircraft, change the Lights setting (Graphics tab) to anything that isn't None (fastest):



Reporting bugs

You can report bugs and other issues on RoR's GitHub repo issue tracker.

Make sure your issue hasn't already been reported.

The issue tracker is only for issues relating to the latest development build, if you're using an official release, please post on the correct support forum instead.

Last update: February 17, 2023