Controls and configuration¶

Intro¶

Rigs of Rods is a simulator which strives for maximum realism, and hence you need an appropriate controller, such as a wheel for land vehicles and joystick for aerial or marine vehicles.

Input is configured from the in-game Controls menu (Keyboard only), editing configuration file input.map, or by using the Input Mapping Tool.

Keyboard layout¶

General controls¶

Character¶

Camera¶

Time¶

Sky type must be set to Caelum or SkyX. Sandstorm sky does not support time change.

Overview map¶

Saves¶

Common vehicle controls¶

Shifting¶

Lights¶

Misc¶

Commands¶

Aerial and marine controls¶

Planes¶

It is recommended to use: CTRL+Home to start all engines of a plane and CTRL+PAGE-UP to full throttle all engines because some planes could have more than 4 engines and you couldn't control them with your mouse.

Boats¶

Changing keyboard controls¶

Starting with Rigs of Rods version 2021.10, it is now possible to remap keyboard controls in-game. Just press the Controls button on the main menu:

From here it's pretty self-explanatory, just select which control you want to change and press the new key.

Config file 'input.map'¶

This file defines all key alias for RoR, located at Documents\My Games\Rigs of Rods\config (Windows) or ~/.rigsofrods/config (Linux) by default. It has the following format:

EVENT_NAME    EVENT_TYPE    MAPPING

For example:

BOAT_CENTER_RUDDER     Keyboard    DOWN

This binds the BOAT_CENTER_RUDDER event to the Down arrow on your keyboard.

A list of all valid events can be found in the Keypress Events section.

Keyboard¶

For the keyboard there are several special things:

Modifiers¶

• CTRL
• SHIFT
• ALT

Combine them with a + sign. Example:

CAMERA_FREE_MODE    Keyboard    EXPL+SHIFT+C

The EXPL tag¶

A special keyword used in defining commands.

In this example, only COMMANDS_01 is triggered when pressing F1, and COMMANDS_13 is triggered when pressing CTRL+F1 (but not COMMANDS_01)

COMMANDS_01                    Keyboard             EXPL+F1 
COMMANDS_13                    Keyboard             EXPL+CTRL+F1

In this example, COMMANDS_01 would be triggered if you press CTRL+F1, as F1 is part of the COMMANDS_13 combination.

COMMANDS_01                    Keyboard             F1 
COMMANDS_13                    Keyboard             CTRL+F1

List of usable keys¶

0
1
2
3
4
5
6
7
8
9
A
ABNT_C1
ABNT_C2
ADD
APOSTROPHE
APPS
AT
AX
B
BACK
BACKSLASH
C
CALCULATOR
CAPITAL
COLON
COMMA
CONVERT
D
DECIMAL
DELETE
DIVIDE
DOWN
E
END
EQUALS
ESCAPE
F
F1
F10
F11
F12
F13
F14
F15
F2
F3
F4
F5
F6
F7
F8
F9
G
GRAVE
H
HOME
I
INSERT
J
K
KANA
KANJI
L
LBRACKET
LCONTROL
LEFT
LMENU
LSHIFT
LWIN
M
MAIL
MEDIASELECT
MEDIASTOP
MINUS
MULTIPLY
MUTE
MYCOMPUTER
N
NEXTTRACK
NOCONVERT
NUMLOCK
NUMPAD0
NUMPAD1
NUMPAD2
NUMPAD3
NUMPAD4
NUMPAD5
NUMPAD6
NUMPAD7
NUMPAD8
NUMPAD9
NUMPADCOMMA
NUMPADENTER
NUMPADEQUALS
O
OEM_102
P
PAUSE
PERIOD
PGDOWN
PGUP
PLAYPAUSE
POWER
PREVTRACK
Q
R
RBRACKET
RCONTROL
RETURN
RIGHT
RMENU
RSHIFT
RWIN
S
SCROLL
SEMICOLON
SLASH
SLEEP
SPACE
STOP
SUBTRACT
SYSRQ
T
TAB
U
UNDERLINE
UNLABELED
UP
V
VOLUMEDOWN
VOLUMEUP
W
WAKE
WEBBACK
WEBFAVORITES
WEBFORWARD
WEBHOME
WEBREFRESH
WEBSEARCH
WEBSTOP
X
Y
YEN
Z

Joystick, Wheel or gamepad¶

This category covers all analogue input devices detected by the operating system, so all gamepads, joysticks, wheels, pedals, etc.

JoystickButton¶

Arguments:

• Joystick Number (unused in modern mappings), set to 0
• Button number

AIRPLANE_THROTTLE_DOWN    JoystickButton    0    2

JoystickAxis¶

Arguments:

• Joystick Number (unused in modern mappings), set to 0
• Axis number
• Options:
  • HALF
  • REVERSE
  • UPPER
  • LOWER
  • RELATIVE
  • DIGITAL
  • DEADZONE : add deadzone in percent with equal sign: "DEADZONE=0.15".
  • LINEARITY: add linearity in percent with equal sign: "LINEARITY=0.15".

AIRPLANE_STEER_RIGHT    JoystickAxis    0    1    UPPER+DEADZONE = 0.15

JoystickPov¶

Arguments:

• Joystick Number (unused in modern mappings), set to 0
• POV number
• Direction: North, South, East, West, NorthEast, SouthEast, NorthWest, SouthWest.

CHARACTER_FORWARD    JoystickPov    0    0    North

JoystickSlider, JoystickSliderX, JoystickSliderY¶

Arguments:

• Joystick Number (unused in modern mappings), set to 0
• Slider number
• Options:
  • REVERSE

TRUCK_MANUAL_CLUTCH    JoystickSliderY    0    Y    0    REVERSE+DEADZONE = -30

Keypress Events¶

These are all the valid keypress events as of version 2022.12, they can be used in a input map or for prop animations. Not all make sense though for animated props.

Common: Generic¶

Common: Actor interaction¶

Common: UI¶

Common: Savegames¶

Truck: Generic¶

Truck: Transmission¶

Airplane¶

Boat¶

Commands¶

Character¶

Camera¶

Sky¶

Grass (Unused)¶

Survey map¶

Menu¶

Truck editing¶

Road editing¶

Controllers¶

Xbox¶

Rigs of Rods supports Xbox 360 / One / Series controllers out of the box, just plug in your controller and play!

You can find a list of controls here.

If your Xbox controller does not work with RoR, please create a thread on the support forum or send a message in the #support channel on the official RoR Discord server.

PlayStation controller support using Steam¶

Currently, Rigs of Rods does not support PlayStation controllers. However, thanks to Steam's excellent input interface, it is possible to "disguise" your PlayStation controller as an Xbox controller, allowing it to work with the game.

This has been tested with a DualShock 4 controller, these instructions should also work with the DualSense (PS5) controller as well.

To begin, install Steam if you don't already have it and sign in.

You will first have to enable PlayStation controller support. Click Steam -> Settings

On the Controller tab, select General controller settings

Enable PlayStation Configuration Support then click Back to return to the settings menu

Next you'll have to add RoR as a non-Steam game. To do this click Games -> Add a Non-Steam Game to My Library...

Click , locate where RoR is installed (usually C:\Program Files\Rigs of Rods) then double-click RoR.exe

Finally, click Add selected programs. RoR will now be in your game library.

If you've done everything correctly, you should now be able to launch the game from Steam and your controller should be working!

Controls are listed here.

If you wish to edit the controls, you can use Steam's UI by clicking "Controller layout" under the green play button (only shown when controller is connected).

For advanced editing you'll need to edit the Controller__XBOX_360_For_Windows_.map file inside the Rigs of Rods\config folder. See Config file 'input.map' for more info.

Mouse¶

Required applications¶

vJoy joystick emulator

FreePIE input emulator

Setting up the input map and FreePIE script¶

After installing the above applications, download this zip file which contains the required input map and FreePIE script.

There will be two files in the zip: vJoy_Device.map and MouseControl.py.

Extract both files into Documents\My Games\Rigs of Rods\config.

Using FreePIE¶

Open FreePIE and press File -> Open. Browse to the MouseControl.py file you downloaded earlier:

Then press Script -> Run script:

The script should now be running. If you get an error, install vJoy.

Leave FreePIE running, launch RoR and you should now have mouse control!

You can modify both the script and the input map to make them better suit for your use.

For example the numbers 40 and 80 in the script are the sensitivity of the controls.

Mouse middle button in the script above, will reset the axises in game, in this case the steering and throttle.

Configuring controls with the Input Mapping Tool¶

The easiest way to configure your device for use in Rigs of Rods is to use the Input Mapping Tool.

vJoy Conflicts¶

Launching the tool¶

After downloading, extract the zip into a new folder. Then double-click Run.bat to launch the tool.

Adding new inputs¶

To begin adding inputs, click Add.

Select the event you want to assign an input to. In this example, I will use TRUCK_ACCELERATE

Then select the correct input type:

Click Add once ready, the tool will then ask you to move the axis/press a button.

The popup will automatically close once the requested action is completed. If not, press Enter.

Repeat the process for all the inputs you want to add.

Once you're done, it's time to export the keymap.

Exporting the keymap¶

Click Export Keymap then select your device from the list.

Browse to Documents\My Games\Rigs of Rods\config, set the name you copied earlier in the File name box, then click Open to save the file.

And finally, run Rigs of Rods and test your device! If you wish to make further edits in the future, you can import your input map by clicking Import Keymap.

If you want to share your created input map, upload it to the Input Maps section of the Repository. Thanks!

Troubleshooting¶

If your input mapping isn't working in-game, you'll first want to check if the name of your input map file is correct.

To do this, you'll find a file named getdeviceinfo.exe in the same folder as the tool. Double-click it, a command prompt window will appear for a split second, this is normal. You will now see a inputinfo.txt file in the directory. Open the text file.

Example output:

System info:
    OIS Version: 1.3.0
    OIS Release Name: 1.3.0
    Input Manager: Win32InputManager
    Total Keyboards: 1
    Total Mice: 1
    Total JoySticks: 1

Devices:
    - OISKeyboard, Vendor: Win32InputManager
    - OISMouse, Vendor: Win32InputManager
    - OISJoyStick, Vendor: Controller (Xbox One For Windows)


Joystick 0:
    Vendor: Controller (Xbox One For Windows)
    VendorMapFilename: Controller__Xbox_One_For_Windows_.map
    ID: 0
    Type: [3] OISJoyStick
    Axes: 5
    Sliders: 0
    POV/HATs: 1
    Buttons: 16
    Vector3: 0
    Vector3Sensitivity: 2.28

VendorMapFilename will be the name of your exported file. In this example, the name will be Controller__Xbox_One_For_Windows_.map.

This is what you'll want to name your file. You can choose to just save your input map through the tool again or rename the file from File Explorer.

If you rename the file, it is highly recommended you enable file extensions (View -> File name extensions):

This is to help avoid you naming the file .map.map by mistake.

If you've made sure your input map is named correctly and the device still doesn't function in-game, please create a thread on the support forum or send a message in the #support channel on the official RoR Discord server.