2025.1.0.37

✅ ACC

• The UDP connection is now attempted before Shared Memory is connected. This allows DRE to retrieve critical UDP broadcasting data up front.
• UDP connection did not look for correctly named "udpListenerPort" in broadcasting.json – DRE now scans for both the correctly spelled and the misspelled ("updListenerPort")
• When the port property wasn’t found, DRE would assign port 0 – DRE now assign port 9000 which is more common for ACC UDP connections.
• When "updListenerPort" wasn’t found in the file, DRE would carry on. ACC needs this misspelled property, so DRE now restores it with either the value from "udpListenerPort" or a default 9000 port value.

✅ Fanatec Controls

• Bug: Some Fanatec device names weren’t treated the Fanatec logic, due to missing out certain Fanatec product names.
  • The list is updated based on Fanatec products up to August 2023.
  • Currently awaiting newer SDK and product listings to make a more up-to-date filtering.
• Bug: DirectInput can report identical/ambiguous identities for Fanatec DD bases and different hubs.
  • Binds were matched by FullInstanceGuid; duplicate or non-enriched IDs caused the same bind to fire on multiple wheels.
  • Fixed Fanatec multi-wheel identity collisions by enriching device identity (name + FullInstanceGuid) using the Fanatec SDK and by adding comprehensive diagnostics.
  • Each wheel/hub now gets a unique, stable identifier so binds won’t cross-trigger between hubs.
• Bug: Hot-swapping steering wheels and hubs on Fanatec bases.
  • The enrichment process of appending Fanatec-specific IDs is only called when a new DirectInput device is discovered. Hot-swapping a steering wheel rim on a Fanatec wheel base does not create a new DirectInput device instance. The PC still sees the same wheel base.
  • Fixed by periodically checking for steering wheel changes on Fanatec bases
• Multiple new verbose logs added for further investigation

⚠️ Fanatec hubs/wheels binds in DRE may require re-binding to map the new naming scheme

✅ Fuel overrides

• Manually adjusting fuel levels via DRE commands did not always check if fuel was being overridden.
• This would allow DRE to continue automatically setting the fuel levels as the session progressed.
• This is now fixed, so whenever you adjust fuel levels manually, DRE understands that you’ve taken control of fueling until the next pit stop
• Commands and actions that "overrides" fuel and stops auto-fueling:
  • set fuel to ...
  • Maximize fuel
  • No fuel
  • Full service
  • No service
  • Changing the fuel level in black box
  • iRacing or 3rd-parties (not DRE) changing fuel
• Commands and actions that disabled override, allowing or retaining auto-fueling:
  • Fuel only (simple enabled fueling)
  • Auto Fuel only (auto fuels and unchecks other pit services)
  • Auto fuel now (auto fuels)
  • Entering the track