If DRE detects Le Mans Ultimate (LMU) as running but does not connect or receive session data, do the following:

1. Start LMU
2. Open General Settings in LMU
3. Scroll to the bottom
4. Make sure Enable Plugins is set to ON.
5. Fully restart LMU and join the track.

DRE uses a LMU plugin to receive live session data, so it cannot connect while LMU plugins are disabled.

When restarting DRE while in ACC, DRE takes a long time before connecting after restart.

The workaround is to pause the sim so it shows the in-car pause menu, before restarting DRE.

If you missed this step, you can either wait a few minutes, or restart the simulator session, by going back to the main menu.

If nothing happens for a while, try exiting out to ACC main menu and then start the session again.

Basic features shared with iRacing work. Advanced features like class leader RPM, offtracks, and telemetry snapshots unavailable. See the full details here

To connect DRE with a racing simulator, make sure the simulator is supported by DRE and is enabled.

To enable the simulator connection, go to `Settings -> Sim Connection -> Racing Simulators` and check on the simulator from the dropdown box

Two ways:

• Rerun Get Started Wizard: Settings -> General -> Start Wizard
• Directly by enabling ACC from the dropdown in: Settings -> Sim Connection -> Racing Simulators

You will need to enable Broadcasting as well. You need to edit your broadcasting.json file in the ACC config folder. At minimum, you must set the updListenerPort value. The broadcasting.json file is located in: Documents\Assetto Corsa Competizione\Config\.

You can use these settings that mirror the test client’s default values:


{
"updListenerPort": 9000,
"connectionPassword": "asd",
"commandPassword": ""
}

Make sure to restart both ACC and DRE after these changes.

If this doesn’t enable ACC, check out this FAQ

Short answer

DRE can control a supported subset of Assetto Corsa pit options by automating AC’s built-in quick pit menu. This is not a direct Assetto Corsa pit-service API integration, so setup and command support are more limited than in sims with richer pit APIs.

Required Assetto Corsa setup

DRE sends the same quick pit menu inputs you would send with keyboard arrows or a wheel D-pad. First make sure AC’s built-in quick pit menu works manually.

1. Open your Assetto Corsa install folder.
2. Open system/cfg/pitstop.ini.
3. Set:

USE_MOUSE_PITSTOP=0

4. Start a Practice, Qualifying, or Race session.
5. Confirm AC’s quick pit menu responds to arrow keys or your D-pad before testing DRE voice commands.

Optional settings sometimes help with visibility, but should be treated as troubleshooting options rather than hard requirements:

AUTO_APP_ON_PITLANE=1
VISIBILITY_MAX_TIME=5

What DRE supports in Assetto Corsa

Supported AC quick pit commands currently include:

• Fuel changes: set/add/remove/max fuel where DRE can map the command to AC’s quick pit fuel row.
• No fuel / clear fuel.
• Change all tyres.
• Clear tyre changes.
• Change tyre compound, using the current car’s AC tyre data where available.
• Adjust tyre pressures by relative clicks, including all tyres or individual front/rear/left/right/corner combinations.

Example commands:

• “Add 10 liters of fuel”
• “No fuel”
• “Change all tires”
• “Set tires to slick medium”
• “Change tire pressures up 3 clicks”
• “Change rear tire pressures down 2 clicks”

What DRE does not support in Assetto Corsa

Some DRE pit commands are not supported for AC because stock AC does not expose a deterministic quick pit action for them, or because DRE has not verified a safe stock-AC flow.

Currently unsupported for AC:

• Full service / no service composed flows.
• Clear all pit services in one command.
• Fast repair.
• Tear-off / windscreen / windshield cleaning.
• Partial tyre changes such as only front-left tyre change, unless the command is a tyre pressure adjustment.

If you use mods that add extra pit menu features, DRE does not currently support those mod-specific options.

Depending on the simulator you race with, there are different ways DRE and the simulator handle fueling.

• Le Mans Ultimate (LMU) is strategy-based – or, how much fuel to carry
• iRacing and ACC are additive-based – or, how much fuel is added

As an example with commanding DRE to “set fuel to 70 liters”:
– LMU: Sets the Fuel or Virtual Energy + Fuel Ratio so you will leave the pits with 70 liters carried
– iRacing, ACC: Adds fuel to the car, so it adds 70 liters on top of what is already there

Here’s the mapping between iRacing and DRE track wetness states:

• 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.

If DRE never connects to Assetto Corsa Competizione (ACC), here are some tips to get going:

Ensure you’ve set up DRE and ACC correctly

First of all, see this FAQ how to set up DRE and ACC the right way.

Add exceptions in your Anti-Virus software

Some times, Anti-Virus applications will block port sharing, causing DRE to never reach the very much needed UDP connection.

The location of the DRE execution file can be found through DRE: Settings -> General -> Show installation folder -> DRE.exe

Allowing DRE Through Windows Defender Firewall

For many users, the built-in Windows Defender Firewall is the first line of defense. Here’s how you can allow DRE through:

1. Allow an app through the firewall:

• Open Windows Security by searching for it in the Start menu.

• Navigate to Firewall & network protection.

• Click on “Allow an app through firewall”.

• Click the “Change settings” button. You might be prompted for an administrator password.

• Find DRE in the list. If it’s not there, click “Allow another app…” and browse to DRE’s installation folder to select the main executable file.

• Once DRE is listed, ensure the checkbox next to it is ticked.

• Also, tick the boxes for the network types your users will be on (usually Private).

• Click OK to save the changes.

2. Create a specific rule for UDP port 9000:

If allowing the app doesn’t resolve the issue, creating a specific inbound rule for UDP port 9000 can help.

• In the Firewall & network protection screen, click on “Advanced settings”.

• In the new window, select “Inbound Rules” on the left.

• On the right, click “New Rule…”.

• Select “Port” and click Next.

• Choose “UDP” and in “Specific local ports,” type 9000. Click Next.

• Select “Allow the connection” and click Next.

• Choose the network profiles where the rule should apply (e.g., Private). Click Next.

• Give the rule a name (e.g., “DRE x ACC UDP”) and click Finish.

Configuring Third-Party Antivirus Software

Many users rely on third-party antivirus suites that come with their own firewalls. The process of adding an exception is similar across most of them.

For Avast Users:

1. Open the Avast application and go to Protection > Firewall.

2. Click on “Application Rules”.

3. If DRE is not listed, you can add it manually.

4. You can also create a new rule to allow traffic on UDP port 9000 if the option is available.

For AVG Users:

1. Open AVG and go to Menu > Settings.

2. Navigate to General > Exceptions and click “ADD EXCEPTION”.

3. You can then browse for DRE’s executable file to add it to the exceptions list.

4. Alternatively, for firewall-specific settings, go to the Firewall section and look for “Application rules” to allow DRE.

For McAfee Users:

1. Open the McAfee Security Center and go to the “Firewall” section.

2. Look for an option like “Internet Connections for Programs” or “Program Permissions”.

3. Click “Add” or a similar button to browse for and select DRE’s executable file.

4. Ensure the permission is set to “Allow” or “Full”.

5. Some versions allow adding exceptions for specific ports under the “Ports and System Services” section.

For Norton Users:

1. Open Norton 360 and go to Settings > Firewall.

2. Select the “Program Control” tab.

3. Click “Add” to browse for and add DRE to the list of allowed programs.

4. You can also create a specific traffic rule by going to Advanced Settings > General Rules and adding a new rule to allow UDP traffic on port 9000.

Important Note: You should always ensure you trust an application before allowing it through the firewall. If you are unsure about any of these steps, it is recommended to consult the support documentation for the specific antivirus software.

Core racing features work. See feature comparison table in docs for specifics.

DRE supports the following racing simulators:

• iRacing
• ACC
• LMU

That message usually means one of these is true:

• The command is outside DRE’s supported simulator quick pit subset.
• The simulator ‘s pit menu is not configured for keyboard/D-pad control.
• You are not in a supported live simulator session.
• The simulator is paused, disconnected, replaying, finished, or otherwise not in a safe state for menu automation.

The below can assist you getting DRE set up with Assetto Corsa (AC)

AC Troubleshooting checklist

Before reporting a problem, check:

1. Can you manually open and control AC’s quick pit menu with the keyboard arrows or D-pad?
2. Is USE_MOUSE_PITSTOP=0 set in system/cfg/pitstop.ini?
3. Are you in a live Practice, Qualifying, or Race session?
4. Is AC unpaused and connected?
5. Does a simple fuel command work before trying tyre or pressure commands?
6. If a tyre compound command fails, try the exact compound wording shown by AC for the current car.

Important limitation

DRE’s AC pit commands work by deterministic quick pit menu navigation. DRE does not claim authoritative AC pit-service telemetry or pit countdown state, and it cannot guarantee support for third-party pit-menu mods.

No. ACC support limited to features shared with iRacing due to simulator limitations.