Cheat sheets

Configure > Cheat sheets draws every controller with what each control does in the aircraft or car you choose. It works for every game whose bindings RigReady reads: DCS World, iRacing, Le Mans Ultimate, BeamNG.drive and Assetto Corsa. For DCS the labels come from the same effective bindings as the DCS bindings page, with the plain-language names of the binding guide where it has one; for a racing game they come from the bindings its own page reads (see the other games).

Choose the aircraft or car under Aircraft or car. The page opens on the game of the setup in use.

By device

The devices are listed on the left, with the name you gave each one on the Devices page, how many of its controls are bound, and a warning count. What the picture is depends on the device; the line under its name says which:

RigReady drawing: these devices have a simple outline drawing:
WinWing Orion stick with the F-16EX (ViperAce) grip or the F/A-18 grip, and the Orion throttle with the F-15EX handles
WinWing MFD1 frames, UFC1 with its HUD1, ICP, startup panel and take-off panel 2
Thrustmaster HOTAS Warthog joystick (the grip seen from behind)
Thrustmaster HOTAS Warthog throttle (three views: the handles from the front, the thumb side of the right handle, the base from above)
Thrustmaster T.16000M stick (the base buttons by bank: left 5–10, right 11–16; the three head buttons as one group)
Thrustmaster TWCS throttle (three views: the side of the handle with the mini-stick, the side with the hats, the base from above; TFRP pedals plugged into the throttle show there too)

Each has one label block per control you put your hand on (a hat is one block with a line per direction) and a leader line from the block to the control. The labels place themselves beside the drawing so that no two lines cross. A block's head names the control and its input numbers; a ? there means nobody has checked on a real device which number or direction is which: press each way and see which row lights up. A device has a drawing only where the drawing is known to match the real thing: where each control is and which numbers it gives were checked against the maker's own number maps and the game's default bindings. The Thrustmaster controls are named the way the maker names them ("H2 TMS hat", "S2 weapon release"), numbered as the device reports them without a TARGET profile or other remapping software. If a control is not where your own device has it, drag the dot in Edit drawing. The outlines are schematic, not pictures of the real hardware, and only these devices have one so far. For a picture that looks like your own device, use photos of it: see Your own photos below.

Shipped layout: the other devices RigReady knows (pedals, the Virpil control panel, the Fanatec wheel) are drawn as cards on a simple outline: buttons, hats as crosses, and axes with a bar that follows the real axis.
Controls named for the device: a controller RigReady knows the buttons of but has no drawing of (the Saitek / Logitech X52 Pro) is a list with one block per control, named the way the maker names it, a hat as one block and the axes named. The list claims no places: it does not say where on the device a control is. Devices are found by their USB id, or by the name they report; press a control to check that its row lights.
Controls list: a device RigReady knows nothing about is a list of its controls, in blocks (the axes, each hat, buttons in runs of eight).
Your photos: your own photos of the device with the controls you placed on them, and how many are placed so far. See Your own photos.
Your layout or Your drawing: what you made in the editor, see below.

Every label reads what the control does, with the plain name where the binding guide has one; the colour says the kind of action, and the legend under the picture names the kinds and filters by one. A control that fires several actions on one press is outlined in amber, ×2 marks an action that is also somewhere else, and a dashed block or card has nothing bound; Unbound controls hides those. Bound controls a drawing has no place for are listed under it, so nothing you bound is ever left off.

Press a control on the device and its label lights up and is selected. Clicking a label does the same. The panel on the right shows every binding on it: the plain name, what the game calls it, modifiers, category, whether it is yours or a default, and where else the action is. Your note keeps up to 120 characters of your own words for that control, for example "hold for weapon release"; notes live in RigReady's folder and appear on the printed pages and on DCS kneeboard pages. Bindings opens the bindings page on that device.

Controls the device reports that are not on the picture are counted, and bindings on inputs that have no place on a controller picture are listed under the picture. On a drawing, a button, hat direction or axis the device reports that the drawing has no place for and nothing is bound to gets a small cell with its number under the drawing ("More controls · not on the drawing", or "not placed on a photo yet" under your own photos), so a press always lights something; Unbound controls hides those cells with the other empty controls. The search box finds a control by action, label or note, and shows how many matches each device has.

A button the drawing has no place for still lights up, in a cell under the drawing

By action

By action turns the sheet around: every bound action, grouped by kind, with where it is. Clicking a place jumps to that control on its device.

Quick look

Quick look is just the sheet, filling the window, for a glance while you fly or drive: a device dropdown, a search box that answers "which control does…" with the places that match, Follow my hands to switch to whatever device you touch, and a line with the last control pressed and what it does. Pop out opens it as a small window that stays on top, for a second monitor. Full page goes back.

Your own photos

Any controller gets a good sheet from your own photos of it, whether RigReady has a drawing of it or not. Take a photo of the device with your phone, get it onto this PC, and choose Use my photo… over the sheet of a device that has no drawing. (On a device with a drawing: Edit drawing, then Use my own photos…. In the layout editor: Make a drawing from a photo….)

Press a control on the device. RigReady says which one it heard, for example "Button 5: click where it is on the photo."
Click its place on the photo. That is all: there are no button numbers to type. Press the next control.

A control was pressed and waits for its place on the photo

Pressed the wrong one? Press another before you click, or Cancel. Undo (or Ctrl+Z) takes back the last change, as often as you like.
To move a control, drag its dot, or press it again and click its new place. The arrow keys nudge the selected dot. Take it off the photo (or Delete) removes it.
Name gives the control a name of your own, such as "Trigger". Label goes chooses the side its label is on.
A hat that moves several ways is one control. A hat Windows reports as a hat comes whole with its first push. Many hats report plain buttons instead: choose Place a hat…, push it up, right, down and left and press it in as RigReady asks (skip a way it does not have), then click its place once. Its ways share that one place, and the sheet shows them as one block.
On a controller RigReady knows the controls of by name (such as the Thrustmaster HOTAS Warthog throttle), a press gives the whole control with its maker's name and all its ways: one click places the "MS mic switch" with its five ways.
Several photos. Add another photo… adds a second photo of the same device, up to six, such as the top and the back of a grip. Give each a name under This photo; the names are printed over the photos. Pressing a control that is already placed brings its photo to the front.
A device that is not connected cannot be pressed. Click a control under Not placed yet, then click its place. The list is what is bound on it in the chosen aircraft or car.

The panel on the right says how far you are ("9 of 43 controls placed") and what is not placed yet. You do not have to finish: Save layout works as soon as one control is placed. Whatever is not placed yet stays on the sheet in a list under the photos, and lights when you press it, so a half-done photo is already a full cheat sheet. The line over the sheet names what is left; Edit drawing takes you back to place more.

Two named photos, nine controls placed, and what is left

The sheet of a half-done photo: the rest is listed under the photos

From then on your photos are the picture of that device model everywhere a RigReady drawing is used: on this page, in Quick look, in Learn your controls, on printed pages and on DCS kneeboard pages.

Your photos stay on this PC. They are kept in RigReady's folder and nothing is uploaded. They leave it only when you say so: on a page you print or save as PDF, on DCS kneeboard pages you export (those are written to the game's kneeboard folder), and in the file Share as file… makes, which holds the photos so that someone with the same device can import them. RigReady keeps its own smaller copy of each photo, drawn again as a JPEG, so where and when the photo was taken is not kept with it.

RigReady takes JPEG, PNG and WebP photos of up to 25 MB, and keeps its own smaller copy of each. All the pictures of one layout together hold about 5 MB at most; a layout or drawing file someone shares with more is refused on import with the reason. A file that is not a picture, or is too large, is refused with the reason, and nothing changes. An iPhone's HEIC photo has to be saved or sent as a JPEG first.

Discard my layout drops your photos and goes back to what RigReady ships for the device.

Use RigReady's drawing and Arrange cards myself, under Instead, put RigReady's drawing or the cards in place of your photos. Undo cannot bring the photos back, so both ask Drop your photos? first; Keep the photos leaves everything as it was. What is saved stays until you save.

While the editor is open, By device, By action and the aircraft or car wait, like the list of devices: save or cancel first.

Edit drawing

Edit drawing opens a device that has a drawing. (With your own photos it opens the photos, as above.) The labels still place themselves; you correct the drawing:

Click a label or the dot of a control, or press the control on the device, to select it. Drag its dot to where the control really is; the arrow keys nudge it. Its label and leader follow.
Name renames the control, Label goes puts its label left, right, above or below the drawing, and Put it back undoes your changes to it.
Use a photo of the device… puts a photo in place of RigReady's drawing and keeps its controls, with a strength slider; drag the dots onto the real controls.
Use my own photos… starts from your photos instead, as described under Your own photos.
Arrange cards myself switches to the card layout described below.

A drawing file

Import… also reads a drawing file (a picture plus the controls and where they are, described in LAYOUT-FORMAT.md in the source), for example one someone made for the same device with Share as file….

Edit layout

A layout says where the label cards of one device model sit on the picture. Edit layout opens a device drawn as cards (and Arrange cards myself in the drawing editor); your layout is kept for that device model, and a layout you made before RigReady 2.0 keeps its places.

Drag cards, their pointers and group frames into place; the arrow keys nudge the selected one. Press a control on the device to find its card.
The field Printed on the device is the label on the card, such as "OSB 6". Add pointer draws a line from the card to a spot on the picture.
Add a group frame draws a labelled frame; a control inside carries the frame's name, and the frame moves its contents with it.
Choose a photo or drawing… puts a PNG, JPEG, WebP or SVG picture of about 5 MB at most behind the cards, with a strength slider.
Not on the layout lists every control the device reports that is not placed; a dot marks one that has a binding. Click one to add it. A control with a binding is never left off a sheet: unplaced ones are added below the picture under "More controls".
Import… reads a RigReady layout or drawing file, or a Joystick Diagrams SVG template, which becomes the background with a card at each placeholder. Share as file… saves your layout or drawing as a file to give to someone else. Discard my layout goes back to what RigReady ships.

Nothing is stored until Save layout, in either editor.

Print or PDF

Print / PDF makes one page per chosen device, on white, with the aircraft or car and the device name on top, and a summary of the most important actions when ticked, on A4 or US Letter. The summary takes a second page when one does not hold every action; nothing is left out to make it fit. Print… uses the system print dialog; Save as PDF… writes a file and says where.

The Kneeboard button, shown for a DCS aircraft, is described on Kneeboard pages, and Learn on Learn your controls.

Edit this page on GitHub