Simhub Plugin, Dashboards, Overlays, Led Profiles, Streamdeck, Strategy planner and more (Last update: 26/06/2026 / v1.6.1.3)

Haagel

Well-known member

Simhub Plugin, Dashboards, Overlays, Led Profiles, Streamdeck, Strategy planner and more


1. Simhub Plugin:

This simhub plugin include :
  • All weather informations
  • All PitMenu Informations
  • All Tyres Informations
  • All Fuel, Batteries and Virtual Energy informations
  • Conversion script to convert dashboards using the Redadeg plugin
  • And a lot more
A great thanks to Temur, Shaun and Giacomo
- Instructions are included in the zip file (available at the bottom of this message).​


2. Simhub Dashboards:

- You can view a sample of data available in the plugin on my dashboard here: LMU NeoSuperDash
Capture d'écran 2026-04-17 161955.png

Capture d'écran 2025-06-13 190614.png


- There's also true-to-life dashboards available here: LMU Dashboards

- Others great dashboards are available on overtake: Click here

- The Lovely dashboards also use the Neored plugin and are therefore great for using with Le Mans Ultimate: Lovely Dashboards


3. Simhub Overlays:

- I like this one: doX LMU Overlays Collection

- There's others available on overtake.​


4. Simhub Led profiles:

- ATSR simhub's plugin is recommended to have the LEDs on your steering wheels or DDUs perfectly reflect the LEDs on the cars in the game: ATSR-Hub EVO

- For Fanatec users, you can use it with the Fanabridge Plugin: FanaBridge


5. Simhub Streamdeck:

- This simhub's plugin by Martin is fully recommended to use your Streamdeck with LMU: StreamDeck SimHub Plugin


6. Strategy planner:

- Although unrelated to SimHub, this planning tool works well and features a very interesting comparison function—with or without "lift and coast." It can run online: Strategy Master 3000

- Or you can download it and run it locally: Strategy Master 3000 sources


7. Simhub Bonus:

- This great plugin is worth a try to multiply the possibilities of your steering wheel: Donutz Switch Mode Plugin

My old demo:

Or Dan Suzuki one:


About the plugin:
___________________________________________________

Mandatory: LMU 1.3 and Simhub 9.11.12

All datas served by this plugins are available in online multiplayer and offline solo, for any simhub dashboards
___________________________________________________

Version:

1.6.1.3 (26/06/2026)


Following a user feedback (he will recognize himself), it appeared that certain fields in the plugin contained errors with languages other than English and French. This version fixes all these issues for all Latin alphabet languages

- LMU_NeoRedPlugin.PitMenu.BrakesReplace has been renamed LMU_NeoRedPlugin.PitMenu.BrakesReplace_Text. The still existing LMU_NeoRedPlugin.PitMenu.BrakesReplace field is now a boolean
- LMU_NeoRedPlugin.PitMenu.BrakesReplace has been renamed LMU_NeoRedPlugin.PitMenuRepairDamage_Text. The still existing LMU_NeoRedPlugin.PitMenu.RepairDamage field is now a boolean

___________________________________________________

1.6.1.2 (15/06/2026)


Here's a few fixes:

- Weather.CurrentSessionLengthMinutes and GameInfos.LengthTime are now reflected correctly the lenght of the session (thanks to Herve45 for his feedback)
- Several numeric fields that were previously of string type are now truly numeric fields
- Fix for the new Toyota TR010 custom team (motormap and ARB) (thanks to Kimi23 for his feedback)

And a big thanks to Herve45 for his deep dive...

___________________________________________________

1.6.1.1 (07/06/2026)


- Fix "PitMenu.ReplaceBrakes" and renamed it to "PitMenu.BrakesReplace"
- Added two new fields, following 1.3.3 update: "PitMenu.BrakesFrontDuct" and "PitMenu.BrakesRearDuct"
___________________________________________________

1.6.1.0 (06/06/2026)


For this plugin's first anniversary, many of its older functions have been rewritten to try and improve overall functionality and performance.

Simhub 9.11.12 minimum is mandatory for this version

New features:

- The PitMenu.Tyre.XX_TyreChange fields have been renamed to LMU_NeoRedPlugin.PitMenu.Tyre.XX_TyreChange_Type
- The four new PitMenu.Tyre.XX_TyreChange_Name fields have been created to have the exact same label as what is displayed in the game
- Weather field values no longer disappear when the game is paused
- The entire fuel/virtual energy calculation has been rewritten for improved logic and to fix several bugs
- The ABS (Extended.VM_ANTILOCKBRAKESYSTEMMAP) field now displays -1 for all vehicles not equipped with ABS (to simplify the use of a filter)
- Fixed an issue with a Toyota GR010 2026

Please feel free to report any problems.
___________________________________________________

1.6.0.3 (24/04/2026)

- Files updated in this version :
  • NeoRed.lmuDataPlugin.dll
- FARB and RARB are now the true values for each class, and no longer just for hyperclasses

___________________________________________________

1.6.0.2 (17/04/2026)

- Files updated in this version :
  • NeoRed.lmuDataPlugin.dll
- Added support for custom liveries (Beta), thanks to dakoriki for the report and nikolainr7 for the additional data.
- Feel free to report any missing values with custom liveries cars
___________________________________________________

1.6.0.1 (15/04/2026)

- Files updated in this version :
  • NeoRed.lmuDataPlugin.dll
- The mess with cars data mapping (motormap, ARB and Brake migration) should now be fixed. Thanks for all the feedback
- Minimum value for "LMU data update interval" is now 50 instead of 5

___________________________________________________

1.6.0.0 (13/04/2026)

- Files updated in this version :
  • NeoRed.lmuDataPlugin.dll

The LMU_SessionDataPlugin.dll file is no longer needed. You can and should delete it, as all the data has been integrated into the NeoRed plugin.
A conversion script is in the zip file to convert dashboards from LMU_Session plugin to Neored plugin (Conversion_Session_NeoRed_English.ps1)

Also:

- Fixed Hypercar Genesis issue
- Significant performance improvements, which should make the controls more responsive

There is a new modular interface that allows you to choose the data you want to use, thus saving some resources. You have to restart simhub for the change to take effect.

Capture d'écran 2026-04-13 144138.png

___________________________________________________

⚠️
  • Although from the version 1.0.0.5, this plugin can work with the Redadeg and Georace plugins, it is not recommended to use them simultaneously. To avoid any problems, it is recommended to remove "Redadeg.lmuDataPlugin.dll" and "georace.lmuDataPlugin.dll" from your simhub folder.
  • There's a powershell script to convert any dashboards or led profiles from Redadeg / Georace plugin toward Neored. (included with instructions in the zip file)
  • It works correctly with TinyPedals, although it is not recommended to use them simultaneously, as it can causes significant flickering in the MFD Pit menu; it is therefore not recommended to do so.
  • There's no known problem with CrewChief or other software until now.
 

Attachments

  • NeoRed Plugin 1.6.1.3.zip
    68.7 KB · Views: 252
Last edited:
Interesting, are you going to put this one on GitHub too?

And a question: what does "LMU_SharedMemoryMapPlugin64.dll" exactly do? Extract information not already present on the historic rF2 plug-in? Which information?
 
It's already on github, althoug not yet updated with the latest version.

"LMU_SharedMemoryMapPlugin64.dll" has been made originally by Temur, to access values like TC, TC Cut, ABS, Motormap, Antisway, Regen Level, etc ...
 
It's already on github, althoug not yet updated with the latest version.

"LMU_SharedMemoryMapPlugin64.dll" has been made originally by Temur, to access values like TC, TC Cut, ABS, Motormap, Antisway, Regen Level, etc ...
Thanks for your reply. The description of the github plug-in page was a little cryptic: "Reads two parameter from memmory, using by simhub plugin for electronics data"
 
Thanks for your reply. The description of the github plug-in page was a little cryptic: "Reads two parameter from memmory, using by simhub plugin for electronics data"
That's exactly what the dll does : it reads two parameters, translated by the plugin to have nice datas :)
 
I may have something plan to make direct change to the Pitmenu from outside. But I ask myself it's worth spending time on this now or waiting for the June update.
Great, that would be a great addition! If it requires a lot of work I'd say wait for the June update. Congrats on this new start and thanks for what you do
 
Hmmm, well it all seemed good BUT.....
If I have Neo and Redadeg both active, the pit menu 'random changing values' issue occurs!
As long as ONE of those two are made inactive then it stops.

Having the Weather and Session plugins enabled is no issue to that fault..... those can be both on with ONE of the above two plugins (Neo or Regadeg) and all works fine.

So it seems that it is linked to how both Neo and Redadeg access the TC/shared memory suff I guess(???)

Wouldn't it have seemed better that YOUR plugin is one made up of ONLY new things that you added? So that Redadeg does all that it always was used for, and then anyone wanting your additional items can run yours also then. Much like the Weather and Session plugins are only 'extras'.
Plus then there would be no need to edit any dashboards or current designed things.
Or..... another less graceful idea is you just leave out the shared memory access parts in yours (eg no TC etc)
 
Last edited:
Hmmm, well it all seemed good BUT.....
If I have Neo and Redadeg both active, the pit menu 'random changing values' issue occurs!
As long as ONE of those two are made inactive then it stops.

Having the Weather and Session plugins enabled is no issue to that fault..... those can be both on with ONE of the above two plugins (Neo or Regadeg) and all works fine.

So it seems that it is linked to how both Neo and Redadeg access the TC/shared memory suff I guess(???)

Wouldn't it have seemed better that YOUR plugin is one made up of ONLY new things that you added? So that Redadeg does all that it always was used for, and then anyone wanting your additional items can run yours also then. Much like the Weather and Session plugins are only 'extras'.
Plus then there would be no need to edit any dashboards or current designed things.
Or..... another less graceful idea is you just leave out the shared memory access parts in yours (eg no TC etc)
Running Neo and Redadeg alongside one another is not necessary as they both supply the same information, therefore duplicates. If you require the extra info that Neo provides your best bet would be to disable/delete Redadeg and update all your dashboard json files to replace the Redadeg used properties with the renamed Neo property names.

Old Name (Original Redadeg Plugin)New Name (NeoRed Plugin)
RedadegNeoRed
Redadeg.lmu.currentBatteryNeoRed.lmu.Energy.Batt.Current
Redadeg.lmu.maxBatteryNeoRed.lmu.Energy.Batt.Max
Redadeg.lmu.currentFuelNeoRed.lmu.Energy.Fuel.Current_L
Redadeg.lmu.maxFuelNeoRed.lmu.Energy.Fuel.Max_L
Redadeg.lmu.currentVirtualEnergyNeoRed.lmu.Energy.VE.Current
Redadeg.lmu.maxVirtualEnergyNeoRed.lmu.Energy.VE.Max
Redadeg.lmu.energyPerLast5ClearLapNeoRed.lmu.Energy.VE.PerLast5ClearLap_%
Redadeg.lmu.energyPerLast5LapNeoRed.lmu.Energy.VE.PerLast5Lap_%
Redadeg.lmu.energyPerLastLapNeoRed.lmu.Energy.VE.PerLastLap_%
Redadeg.lmu.energyTimeElapsedNeoRed.lmu.Energy.VE.TimeElapsed
Redadeg.lmu.Virtual_EnergyNeoRed.lmu.Energy.VE.Current_%
Redadeg.lmu.timeOfDayNeoRed.lmu.GameInfos.timeOfDay
Redadeg.lmu.maxAvailableTiresNeoRed.lmu.Pit.MaxAvailableTires
Redadeg.lmu.newTiresNeoRed.lmu.Pit.NewTires
Redadeg.lmu.pitStopLengthNeoRed.lmu.Pit.StopLength
Redadeg.lmu.DriverNeoRed.lmu.TeamInfos.Driver
Redadeg.lmu.WeatherInfos.Current.CloudCoverageNeoRed.lmu.WeatherInfos.Current.CloudCoverage_%
Redadeg.lmu.WeatherInfos.Current.HumidityNeoRed.lmu.WeatherInfos.Current.Humidity_%
Redadeg.lmu.WeatherInfos.Current.LightLevelNeoRed.lmu.WeatherInfos.Current.LightLevel_%
Redadeg.lmu.WeatherInfos.Current.RainingNeoRed.lmu.WeatherInfos.Current.Raining_%
Redadeg.lmu.WeatherInfos.Current.RainIntensityNeoRed.lmu.WeatherInfos.Current.RainIntensity_%
Redadeg.lmu.WeatherInfos.RainChanceNeoRed.lmu.WeatherInfos.RainChance_%
Redadeg.lmu.WeatherInfos.Track.WetnessNeoRed.lmu.WeatherInfos.Track.Wetness_%
 
Last edited:
Absolutely agree! This version of the plugin is more complete, more organized, and has all the necessary information in one place. Adapting dashboards is a job that takes only a few minutes
 
...Adapting dashboards is a job that takes only a few minutes
Imo. Adapting dashboards is actually the hard part. Telemetry is based on scenario's and the aspect of time is continuous. Whereas a sql database uses timestamps to determine the status of a field for one single moment (bit of a functional/technical argument).

Scenario based dashboard development means you need to test a lot. To understand if one piece of telemetry is correctly displayed at any given moment, you need to test with things like: the practice session, the race session, multiclass, single class, first lap of the race, last lap of the race, when in pit lane, when a yelow flag is active in sector 2.... etc. etc.

Editing a piece of code is indeed easy and takes only a few minutes. Testing for flaws in the logic of on-track scenario's takes a serious amount of time. You will need multiple Simhub replay files. And store specific replay moments so you can test them now and in the future for comparison after updates (like plugin updates, game updates, Simhub updates). Having custom telemetry plugins that need regular updates, makes it quite the challenge to maintain these LMU dashboards with a certain level of quality.
 
There are way more properties to change than that list above...... (to change Redadeg to NeoRed)

This is a bit of a debacle.
As long as BOTH exist, with overlapping data values, they are in competition and will cause/encounter dashboard clashes. eg one person makes adash for Redadeg and another person makes a different good dash for NeoRed..... users will be hunting and editing.....

It would be best if they can BOTH co-exist!!!! And that seems to mean one of them should lose that clashing shared memory access....
OR...... R.I.P Redadeg and have all those dashboards edited to NeoRed ! (at the creator/source point)

But for ME... it is not too hard to alter dashoards etc as I am doing that stuff all the time. But for general, layperson, users.... well they will run into all the overlap clashes..... (who knows if that will be a low amount or a lot of cases).
 
There are way more properties to change than that list above...... (to change Redadeg to NeoRed)

This is a bit of a debacle.
As long as BOTH exist, with overlapping data values, they are in competition and will cause/encounter dashboard clashes. eg one person makes adash for Redadeg and another person makes a different good dash for NeoRed..... users will be hunting and editing.....

It would be best if they can BOTH co-exist!!!! And that seems to mean one of them should lose that clashing shared memory access....
OR...... R.I.P Redadeg and have all those dashboards edited to NeoRed ! (at the creator/source point)

But for ME... it is not too hard to alter dashoards etc as I am doing that stuff all the time. But for general, layperson, users.... well they will run into all the overlap clashes..... (who knows if that will be a low amount or a lot of cases).
Hi,

All your complaints reflect exactly this:
https://community.lemansultimate.co...ownload-here-simhub-dashboards.646/post-45545

Despite my warnings, I was asked to create a separate plugin. Since I only use this one, I won't delete any data.

This new "NeoRed" plugin is compatible with the original "Redadeg" plugin, not the latest versions that I've made.
 
Imo. Adapting dashboards is actually the hard part.
Editing a piece of code is indeed easy and takes only a few minutes.
Hi,

I think Massilu77 was talking about modifying the existing dashboard as explained in the first post.
And I wouldn't be so sure that editing a piece of code is easy and takes only a few minutes, especially when you aren't the original author.
 
I installed V1.0.0.2
Then went to look at all the Properties in Simhub (filter - neo)
I did not see the three new properties you listed..... and the fuel.current and fuel.max were still there also. (though they are really .current_L and .max_L..... I have never seen/had any plain .current and .max values in any version. I keep a text file of all properties, updated per plugin version.)

The file I copied into Simhub was the exact same as per inside the V1.0.0.2 zip (when extracted and compared later to be sure), so I am sure it was the one from the new zip, downloaded from the first post link. (the DLL is 105,984 bytes in size... a bit smaller than V1.0.0.1 was)
I had copied over all three DLL's even though the Weather plugin was the same one as V1.0.02 included. (Session was newer)

Doing a file properties check on NeoRed (Windows) in Details it shows V1.0.0.0...... so I guess that has never been updated per version(?)
SessionData is also not version updated in Details either.

In Simhub it shows plugin V1.4.5.... which all Redadeg and NeoRed have always shown also.... so I guess that is never updated also(?).

It would be good if those two version locations (Windows Properties Details, and Simhub plugin options page) were kept up to date to show the true versions the files are.

I am not sure why, but so far it SEEMS the V1.0.02 is the same as V1.0.0.1.... in its properties... but not in the file size.
 
I installed V1.0.0.2
Then went to look at all the Properties in Simhub (filter - neo)
I did not see the three new properties you listed..... and the fuel.current and fuel.max were still there also. (though they are really .current_L and .max_L..... I have never seen/had any plain .current and .max values in any version. I keep a text file of all properties, updated per plugin version.)

The file I copied into Simhub was the exact same as per inside the V1.0.0.2 zip (when extracted and compared later to be sure), so I am sure it was the one from the new zip, downloaded from the first post link. (the DLL is 105,984 bytes in size... a bit smaller than V1.0.0.1 was)
I had copied over all three DLL's even though the Weather plugin was the same one as V1.0.02 included. (Session was newer)

Doing a file properties check on NeoRed (Windows) in Details it shows V1.0.0.0...... so I guess that has never been updated per version(?)
SessionData is also not version updated in Details either.

In Simhub it shows plugin V1.4.5.... which all Redadeg and NeoRed have always shown also.... so I guess that is never updated also(?).

It would be good if those two version locations (Windows Properties Details, and Simhub plugin options page) were kept up to date to show the true versions the files are.

I am not sure why, but so far it SEEMS the V1.0.02 is the same as V1.0.0.1.... in its properties... but not in the file size.
Hi,

Maybe a mistake. As I'm not on my PC now, could you try the plugin from the dashboard zipfile? The link is in the first post of this thread.
 
Good evening @Haagel 🖐️ ,

if your plugin is an extension of redadeg's plugin, haven't you both considered working together instead of side by side ?

I don't mean to belittle your work or redadeg's work in any way - quite the opposite.
I greatly appreciate both of your efforts, because you sacrifice your time to create added value
for the community & that deserves the highest recognition 🤝
 
Back
Top