Features

OSD Setup

WTRTI (Built-in)

This type of OSD is enabled by default, if it is not, you can enable it at:
Settings -> OSD -> OSD Type -> WTRTI

Start the game. In the graphics settings, switch to Fullscreen window mode.

That's it. Go to the "Test Flight" for testing.

Tip

To change the font, see Changing the fonts.

Warning

Make sure that "Hardware Accelerated GPU Scheduling" (HAGS) is disabled.
See Troubleshooting section

Tooltips

Most controls have tooltips. Simply hover over them and a tooltip will appear.

Profiles

Profiles are located in the Profiles folder.
A profile may contain: Groups, Colors, Indicators and VR options (optional).
All other settings are stored in the main config file (WTRTI.cfg).
If you have downloaded a profile (.cfg file), place it in this folder and restart the application.
You can then select it from the combo box below.

If you want to create a new profile, click the Reset button (circle arrow) in the main window.

Vehicle Profiles

The type of profiles that are saved with a vehicle name, e.g. bf-109f-4, mig_29_9_13, spitfire_mk1.
To save a vehicle profile, go to Test Flight then ALT-TAB to the main window, and click on the Save button (floppy disk at the bottom).

Auto-loading profiles

This feature allows you to automatically load profiles when you start a battle or change vehicles.
You can enable it at: Settings -> General tab -> Auto-load profiles

Profiles have loading priorities:
1. Vehicle Profiles.
2. By a Type: Flighter, Strike, etc.
3. By a Propulsion: Prop, Jet.
This means that if you have a vehicle profile, it will be loaded first, ignoring other types.

Loading profiles by Hotkeys

Only works while in the battle.
Settings -> Hotkeys tab -> Loading profiles

Groups

Groups controls how the indicators are displayed, their position and layout.

You can also move a group using keyboard.
Select a group in the main window, ALT-TAB to the game and press:
SHIFT + ALT + ARROWS

Setting up Multiple Groups

This feature allows you to configure multiple groups at the same time.
Select multiple groups from the Groups list, make changes, and click Apply.
Only the changed settings will be applied to other groups.
You can also move multiple groups at once.
If you change the position of the leading group (the last one selected), the leading group's offset (new - old pos) will be applied to the others.

Multi-value layout

This option allows you to change the layout of neighboring multi-value indicators.

List: ENGN1, ENGN2, ENGN3, RPM1, RPM2, RMP3, etc
Shuffle: ENGN1, RPM1, ENGN2, RPM2, ENGN3, RPM3, etc

Colors and Color Schemes

WTRTI works with color slots.
You can Add, Delete and Set a color slots (maximum 32).

By default, all indicators have the same color scheme (All).

You can change the color for every part of an indicator: Name, Value, Units.
If you want to set up colors for a specific indicator, enable the Separate Color scheme, then you can change the colors in the indicators settings.

Indicators

Double-click on the indicator in the main window to open the indicator settings window.

General

Alert

Alerts, allows you to specify a range of values within which you will be alerted visually (color change) or sound playback when the value exceeds the threshold.

For example, you need an alarm when you are at low altitude.
Open the "Altitude, m" settings.
Add a new alert condition by clicking the Add button in the Alert section.
Then double-click on the new element.

Specify the threshold value (e.g 200 meters)
Note: Using < sign means that this condition will only be triggered for values below 200.

Choose a color and sound.

Click on the OK button.
This is it. Go to Test Flight for testing!

Tip

For sound alerts, it's recommended that you use a 'relative paths' for audio files by selecting them from the WTRTI root directory, e.g. Sounds folder.
This makes the profile more portable, so you can share it with others.

Advanced

In "State" list

This option allows you to place the final value of the indicator, after all postprocessing, into the "State" list (press F2 in the main window).
Enable the option and specify the key that will be in this list.

All In-State indicators are calculated in a separate order, from top to bottom, before Non-In-State indicators.
The indicator with an in-state key that depends on another in-state indicator (chained), must be placed below that indicator in the main list, otherwise it will be N/A.

Logging the data to a CSV file

Go to Test Flight.
Activate Benchmark mode with CTRL + ALT + B (by default).
To start logging press X key.
Press again X to stop.

All these hotkeys you can rebind in the Settings -> Hotkeys tab.
You can change the logging interval in milliseconds, at
Settings -> General tab -> Benchmark mode -> Logging Interval
Generated .CSV files are located in the Logs folder.

In the OSD, the benchmark information is positioned in the last group, so if you want to place it in a specific location, create an empty group and move it as you wish.

You can toggle Logging for a specific indicator in the Indicator's Settings, by default it's enabled.

Game Chat

Game chat - allows you to see, copy or translate messages of the in-game chat.
You can enable the auto-logging feature, Game Chat -> Settings -> Logging, this will automatically write into a log file for every game session.
Log files are located in the Logs folder.

Battle Log

Shows recorded battle events, with ability Logging to file.
You can enable the auto-logging feature, Battle Log -> Settings -> Logging, this will automatically write into a log file for every game session.
Log files are located in the Logs folder.

Highlights

Located at Battle Log -> Settings. Allows you to set a "keywords" to highlight certain words in battle log messages.

Vehicle Information

This window allows you to see some information about your current/selected vehicle.

Warning

This information depends on the pre-generated offline database.
Please do not use it for bug reports!

You can also see this information in the overlay.
All you need is to set up a hotkey at:
Settings -> Hotkeys tab -> Vehicle Information -> Show in OSD

VR

VR support is implemented with SteamVR.

Install SteamVR.
Start WTRTI and enable VR mode (Settings -> Advanced).
Click the VR button in the main window to display the VR Settings.

Warning

If you have an iGPU, make sure you are using WTRTI on the discrete GPU (High performance):
https://pureinfotech.com/set-gpu-app-windows-10/

SteamVR Controller Bindings support

Allows you to assign VR controller buttons to specific WTRTI actions.
To make settings to be available in SteamVR, you need first go in a "Test Flight", then select WTRTI from the list of programs in the SteamVR's Controller Bindings window.

Hotkeys

CTRL + ALT + V - toggles "HMD tracking" mode.
CTRL + ALT + Z - toggles "Left controller tracking" mode.
CTRL + ALT + X - toggles "Right controller tracking" mode.
CTRL + ALT + S - saves the overlay's position and rotation from "tracking" modes to the no "tracking" mode.
SHIFT + ALT + R - resets the overlay's position and rotation(x:0.0, y:0.0, z:-0.5).
SHIFT + ALT + LEFT/RIGHT - moves the overlay along the X axis.
SHIFT + ALT + UP/DOWN - moves the overlay along the Y axis.
SHIFT + ALT + PAGE UP/PAGE DOWN - moves the overlay along the Z axis.
SHIFT + ALT + Q - decrease the overlay's size.
SHIFT + ALT + E - increase the overlay's size.

Meta/Oculus headsets

If you are using Steam Link, ensure that the Current OpenXR Runtime is SteamVR.

Meta/Oculus headsets (Legacy)

To make the game run through SteamVR, you have to set the compatibility mode to Windows 7, for aces.exe in win32 and win64 folders.
How-To:
In the game root folder, open win32 folder and find aces.exe, open its Properties and set Compatibility mode to Windows 7:

Do the same for aces.exe in the win64 folder.
It is also recommended to run the game through Steam.

Advanced

RTSS OSD Setup

Download and Install RTSS.
Start WTRTI.
Settings -> OSD -> OSD Type -> RTSS

Note

By default RTSS has 2x "On-Screen Display zoom".
If you do not change it to 1x, the position of a group in WTRTI will be magnified by 2.
For example, 200,100 in config becomes 400,200 on screen.

Warning

RTSS only works with text-based indicators.
Also, RTSS only supports ASCII characters.

To change the font, see Changing the fonts.

Gamescope Setup (Linux)

There are two ways to use gamescope:

Create a script:

#!/bin/bash
export PATH=$PATH:/path/to/WTRTI
./launcher &
WTRTI

Place it in the game root directory, where the launcher is, and run it with Gamescope:
gamescope ./run.sh

From command line:

Start the game with Gamescope:
gamescope ./launcher
Launch WTRTI from another command line:
GAMESCOPE_DISPLAY=:2 ./WTRTI

Note

GAMESCOPE_DISPLAY should be the name of the gamescope Xwayland server.
When you start the game with gamescope, you can see what name gamescope uses.
wlserver: [xwayland/server.c:108] Starting Xwayland on :2

Warning

After playing, first close WTRTI and then the game!
Otherwise it will crash and you may lose your configuration.

FM Mode

This mode contains additional indicators, that only works in "Test Flight":

Excess power, W
Drag, kgf (lbf)
Total mass, kg (lb)
No fuel mass, kg (lb)
Thrust to Weight ratio
Critical G, % (in-battle approximate version)

To make these indicators to work, follow these steps:

Open the game root folder.
Open config.blk file with text editor.
Find debug section
Emplace this line:
```
enableFMCommands:b=yes
```
Save the file and Start/Restart the game.
Enable "FM mode" in Settings -> Advanced.

Custom indicators

Open Add window (+ button) -> New (or RMB on the indicators list).

Use State window(press F2 in the main window) to see which parameters are available.

Warning

Empty State Key - switches the indicator into "label" mode, which will only show OSD name and trigger an alerts.

Multiple values

Replacing numbers in the State Key with %d, allows reading multiple parameters (e.g. multiple engines) with the same key.
Examples:
RPM 1 -> RPM %d
manifold_pressure1 -> manifold_pressure%d

"Lua-script" option

Allows you write a custom value processing in Lua.
Right after enabling this option and pressing OK, a template script will be created, you can find it at:
Indicators/NAME/update.lua

Also have a look at the Lua API to see all the functions that are available.

OSD on a second screen

Simply switch "Window mode" (Settings->OSD) to "Windowed" and move the "WTRTI OSD" window to a second screen.

Receive data from another PC or Console on the local network

Set another PC's local IP address in Settings -> Network -> Address:

Warning

Leave 8111 port unchanged

DCS World Setup

Copy-Paste the DCS/Scripts/Export.lua into
%USERPROFILE%/Saved Games/DCS/Scripts/
For DCS Open Beta use this directory:
%USERPROFILE%/Saved Games/DCS.openbeta/Scripts/
Start WTRTI, open Settings -> Advanced tab -> Enable "TCP Listener".
Start the game.