The software can be seen on the attached images, here are explanations and features:
Toolbox is divided in three categories:
1.Game variables – here you have all data which the game outputs
2.Display controls – currently there are 12 implemented controls. In future we will be adding more
3.Custom variables – your custom defined variables will be here.
-BarGraph – shows numeric data which have unit set to Percentage
–ColorGraph – control which is ideal for showing temperature(tire, brakes). You define your color stops and Telemetry value and as telemetry value changes it changes its color. If you want it to look like tire just set the RadiusX and RadiusY
-Ellipse, Rectangle – basic drawing shapes
-EnumLabel – shows enumeration values (SessionType, PitState, etc…)
-FlagsLabel – if there is any active flag it will be displayed. You can define which flags you want to be shown
-ImageLabel – show image
-NumericLabel – shows numeric data. It has automatic unit conversion so you can choose in which unit numeric data should be presented.
-Status label – control for showing boolean variables. You can configure its look based on the state of telemetry variable(ON/OFF)
-TableView – for displaying tabular data. It’s ideal for Driver statistics. You can define which columns to show, etc.
-TextLabel– for displaying text data(DriverName, TrackName, etc.). Also you can use it without Telmetry variable if you want to show your own custom text
-TimeSpanLabel – for displaying timing data (Best lap time, last lap,etc.). Also you can check option “show pefix” which can be useful for split time
You can configure RPM leds to use it in old boring way or you can, like in F1, use them for multiple variables. For example, you can set the first 4 leds to show you KERS data and other for RPMS, everything is completely configurable.
As with RPM leds, here we’ve also gone one step further. For each extra led you can set multiple variables, for each variable you can choose whether you want it to blink or not, blink rate, and invert value.
Here comes the true power of PRO version. With custom variables only your imagination is the limit. Real power of custom variables comes when you combine them. There are five types of custom variables:
Writing custom functions is similar to Excel formula bar. For example to calculate average fuel consumption per lap you would write:
if( [Laps completed]>0 , ([Fuel capacity] – [Fuel level]) / [Laps completed], 0)
You can combine many of implemented functions, for example Math functions include Pow, Sqrt, Trigonometric etc. There are also string functions, for example Strlen, ToUpper, Substring… Also you can combine functions with operators like OR, AND, NOT, *, /, +, -, %, <<,>> <>, == etc. Before using operators it would be best to consult the help on the right side. After you write your expression you can test it and change input variables’ values in DataGrid.
If calculated value isn’t unitless you can set its unit so that you can show it in NumericLabel.
Triggers are fired when selected variable changes its value. They can be used for automatic switching of shown display and for setting timers, counters and global variables.
They can also be delayed, so for example you can set trigger to fire only if new value remains longer than some period.
For example you can configure multiple displays some of which are intended for Race session, some for Practice, Qualify etc. and triggers automatically switch between displays based on current session.
Counters are custom variables which are incremented when some trigger fires. You can also set reset trigger which resets counter value. Also you can specify minimum and maximum values which can be constant or telemetry values. For example, you can set counter to count number of pitstops made, number of time that you overtake somebody, or anything that comes to your mind.
Timers are similar to counters, they act as stopwatch. When they are triggered they start counting time until stop trigger fires or they reach maximum.
Global variables, as their name suggest, are variables which are set/reset by some trigger. When trigger fires global variable is set to telemetry variable. For example if you want to calculate last lap consumption or anything else you can use global variables in combination with custom functions and triggers.