Important things to know before starting your DRE journey

Before DRE

Become familiar

  • Some features are only available in the subscription versions. This means commands with Essentials, Performance, or Ultimate marks are only functional after obtaining a subscription. See the Pricing.


  • Some commands need bindings set to be able to send keypresses to iRacing. Check the DRE -> Controls


  • Generally, DRE’s alerts and responses try to inform you once you are not busy turning or braking, but going straight full or at zero throttle.


  • It is recommended to set Max Cars to 63 in iRacing Options -> Graphics. Otherwise, live positions and some timing info may be distorted and false due to connection drop-outs. This is a limitation by iRacing unfortunately as we cannot expect iRacing to stream all 63 cars constantly even with Max Cars = 63.


  • Regular running of DRE should not impact your system as monitored CPU usage and footprint is only about 1-8%. Loading DRE and when loading into a session increase the footprint shortly. Memory usage should maintain a steady level between 200 and 800MB over the session depending on the number of drivers and alerts enabled.


  • Generally, voice commands work really well where DRE understands your voice easily, but a few may be shaky, where dictation is used. This is for example when using the command ‘start chat …’ and you speak a sentence. Consider using the pre-made commands starting with Say …

Become familiar

iRacing tips

  • If possible, set Connection Type to DSL, Cable, Fiber 1 Mbit/sec or faster. This may influence the data transmitted between cars and therefore the precision of The DRE.
  • Units are automatically changed to the units used in iRacing
  • DRE does not work fully during ghost races and spectator modes.

About gaps

The term gap has different meanings in practices and quals versus in races

  • In practice and qual, “gap” refers to the differences in fastest lap times set between your car and the other. Eg. If you did a lap time of 1:22 and the other car did a 1:23, DRE would give a feedback like “gap to car behind is 1 second”.


  • In races, “gap” refers to the interval time between your position on the track and that of the other car. So if you eg. are halfway through the lap (50% lap distance) of 1:22, you would be at 41 seconds into the lap (simplified calculation here). The other car would be eg. at 40% distance, so that would be around 33 seconds into the lap. The gap would then be 41 – 33 seconds = 8 seconds. DRE would report this as “Gap to car behind is 8 seconds”.


  • It is therefore only possible to compare the “gap” to the Relative Tab in races, where the gap should reflect the Relative Tab Timing data. In practice and qual sessions, the “gap” refers to the differences in lap times.

About gaps


Alerts in DRE automatically start monitoring the iRacing action for various alerts, warnings, proximity alerts, etc. You can select which alerts to get using the DRE app.

See the DRE in-app tips for more about alerts.


What’s next?

Started setting DRE up