Graph

This page shows a live scrolling waveform graph of several internal signals. What you see depends on which of the 8 toggles (below the graph) you turn on.

The graph is meant for “at-a-glance” monitoring while you drive and tune. It only draws while this page is open — switch to any other page and MAIRA stops spending time on it.

This is a live view of what is happening right now. If you want to stop and study a stretch of force feedback in detail — scrub through it, zoom in, compare it against the track — record it and use the preview graph on the Racing Wheel page instead.

What each toggle shows

Each toggle enables a “layer” in the graph. If a toggle is off, that layer isn’t drawn. Layers are drawn on top of each other, so turning on only the one or two you care about is usually easier to read than turning on all eight.

Input torque

Shows the 360 Hz steering torque iRacing is providing (the “input” the FFB graph receives), drawn in red. This is the raw signal before any of your FFB graph modules touch it.

Output torque

Shows the final force value MAIRA is sending to your wheel after the FFB graph has run — every module in the graph, plus the fades MAIRA applies when it starts, stops, or hands control back. Drawn in cyan.

Comparing this against Input torque is the quickest way to see what your graph is actually doing to the signal.

Input torque (60 Hz)

Shows the 60 Hz steering torque iRacing is providing, drawn in red. This is one value per telemetry frame, held for the whole frame, so it looks like a staircase next to the 360 Hz trace.

Input LFE

Shows the current low-frequency-effect magnitude MAIRA is producing, drawn in blue.

More information about Wheel LFE can be found here – Wheel LFE

Clutch pedal haptics

Shows the current clutch haptics waveform MAIRA is generating (a live sine-based signal), drawn in blue.

Brake pedal haptics

Same concept as clutch, but for the brake haptics waveform, drawn in red.

Throttle pedal haptics

Same concept as clutch/brake, but for the throttle haptics waveform, drawn in green.

Timer jitter

Shows timing jitter in the playout timer loop — how stable MAIRA’s 360 Hz timing is — drawn in green. Each tick is plotted as how far it landed from the ideal 2.78 ms period, so a flat line on the center is perfect timing and the full height of the graph is one whole period late or early.

A little fuzz here is normal. Large, repeated spikes mean something on your PC is starving the timer thread, which is worth chasing down because it shows up in the wheel as roughness.

Quick reading tips

Midline and scaling

• The vertical center is “0”.
• Up/down indicates positive/negative depending on the signal.
• The top and bottom edges of the graph are full scale. For the torque traces that is your Max force setting on the Racing wheel page — a trace touching the edge is a force as large as your wheel is set to produce.
• Horizontal grid lines mark every 25% of full scale, with the two halfway lines picked out in a lighter color so you have something to judge against.
• The intensity of the line increases with magnitude.

Background flashes

Instead of drawing anything extra on the waveform, the graph tints its own background while something notable is happening. The tint is painted column by column as the graph scrolls, so you get a colored band that lines up with exactly when the event happened:

• Red — output torque is clipping. The graph asked for more force than your wheel is set to deliver, so the peaks are being flattened. This is the one to care about: it means detail is being thrown away.
• Orange — crash protection is active.
• Yellow — curb protection is active.

Only one color shows at a time. Clipping wins over crash protection, which wins over curb protection.

Crash protection and curb protection are FFB graph modules on the Racing Wheel page — if your graph does not include those modules, you will never see their colors here.

This makes it easy to spot clipping and protection events without staring at the waveform.