LMU Results Companion

1742045906056.png

Hi, I discover your app, a lot of feature !!
How did you find who is fault ? In this screen the guy hit me several times in my back because of a little loss car control (race fact, I don't blame him), just for understand your algo ?
 
View attachment 7355

Hi, I discover your app, a lot of feature !!
How did you find who is fault ? In this screen the guy hit me several times in my back because of a little loss car control (race fact, I don't blame him), just for understand your algo ?
Take it with a pinch of salt. The car behind at the time of collision is "Guilty". Bear in mind there is latency as well so the relative positions might not be correct
 
Last edited:
Ok, I think I had a bad understand at first. I thinked the column "at fault" was for me, but there is for the driver in the next column.

So it's not so bad, You should ssell your tech to S397 :LOL:
 
I want to be able to run the software on a different PC.
How do I change/set a different LOG folder so I can use a shared network drive folder?
 
I want to be able to run the software on a different PC.
How do I change/set a different LOG folder so I can use a shared network drive folder?
Go to the LMU Settings page and click the button with the folder icon (tooltip says "Move data folder....."
zfMId7w.png

You now select a target folder. LMU-RC will restart and all files in the data folder will be moved to the target folder.

Note...if your shared folder is a cloud drive (OneDrive, GoogleDrive etc), make sure you have the option to make files available offline otherwise you may get errors
 
Last edited:
Go to the LMU Settings page and click the button with the folder icon (tooltip says "Move data folder....."
zfMId7w.png

You now select a target folder. LMU-RC will restart and all files in the data folder will be moved to the target folder
Sorry @doug99... I meant how do I change the LMU Results Folder?
That's where we get the LMU data from... I'm guessing?
That's this folder

1742237215348.png
 
Hi Doug, I mentioned at the start of the thread that I wanted to use the timing widget for sectors etc. and having tried it this morning it seems to work well, except the colouring for slower, faster, best sectors just doesn't seem to work. Is that a known thing? Screenshot 2025-03-20 120343.jpg
 

LMU Results Companion 1.3.2 Released (here)​

  • Replay widget
  • Proper time sorting of accidents by time
  • Translucent widgets


Accident Replay Viewer
I wrote this mainly because I'm a big fan of DaveCam's videos, especially his review of accidents at the end of races on iRacing. It frustrated me that there was nothing similar on LMU. So here we have something - not sure what to call is - Accidents Almanac/Carnage Cam/Wreckage Reviewer - answers on a postcard.

So, this is a helper function to scroll through all accidents reported in the replay. To view, select a session, right click on the laps widow and select Show Accident Replays.

XWCpxJF.png


LMU must be running and in the main menu (ie not in a race or in another replay). The LMU replay will then start (note this takes 20 seconds or so). Initially the replay will be at the very start focussing on your car. The widget will display initially in the top left corner, although this can be moved. (Note, for widgets/overlays to be visible, LMU must be in windowed mode, not full screen)
nTPgj9g.png

The widget shows the driver to filter on (initially * for all drivers) and the current accident and total number of accidents. If you want to focus on a particular driver, right click on the Driver field and select the driver. Note, only drivers involved in accidents are displayed
SrFeOUf.png

If you select a driver, it shows their total number of accidents and the current one being viewed. The replay will switch focus to the selected car and jump to 2 seconds before the accident. You are free to use the replay controls to select different views. When you switch driver, it jumps to their first accident. To switch back to all drivers, choose *. If a driver have multiple impact in a couple of seconds, these are just collected into one accident.

You can use the next and previous buttons to jump to the next or previous accidents.
AarW0KK.png

Some caveats:

  • This is a rough first attempt. I'm finding it useful interesting to review incidents so other people may find the same. I'll probably be refining it as I work out what could be improved
  • There may be an issue with some older replays - I've found occasionally that LMU mis-reported the track in the metadata so the replay isn't matched correctly. I'll see if I can find a workaround to that
  • This uses the REST API interface for LMU which can be a little shaky. I have found that very occasionally (I've only seen this once in a Le Mans replay) it causes LMU to crash. In the replay I had it always crashes jumping to the same incident. If this happens, you may find better luck selecting each car and scrolling through their accidents in turn rather than all accidents in one go

Finally
Thanks again to all those who donated - I really appreciate it

 
Hi Doug, I mentioned at the start of the thread that I wanted to use the timing widget for sectors etc. and having tried it this morning it seems to work well, except the colouring for slower, faster, best sectors just doesn't seem to work. Is that a known thing? View attachment 7463
I was never happy with the way I tagged these and just wasn't consistent. I'll have another look and try to make sure everything makes sense
 
Hi Doug,
I'm having issues with timings in the Sessions tab in general with the app. Not all (if any) reported times are being populated correctly. The affected columns are:

Duration
Total Time
xLap Time
Best Lap

I don't know if this is just me, or a known issue but (for me at least), none of this data has worked as anticipated from day one. Any help would of course be very much appreciated. I know it's early days for the app and it's coming together well, just these 'niggles' for me! :oops:

My uploaded diagnostic ID: uB7Niw-LrOdP0rMSpmkolL9ECrD55i3y6XaywwehBek

Many thanks.
 
Hi Doug,
I'm having issues with timings in the Sessions tab in general with the app. Not all (if any) reported times are being populated correctly. The affected columns are:

Duration
Total Time
xLap Time
Best Lap

I don't know if this is just me, or a known issue but (for me at least), none of this data has worked as anticipated from day one. Any help would of course be very much appreciated. I know it's early days for the app and it's coming together well, just these 'niggles' for me! :oops:

My uploaded diagnostic ID: uB7Niw-LrOdP0rMSpmkolL9ECrD55i3y6XaywwehBek

Many thanks.
Hi,
To unpack all the issues here
  • It looks like I should have duration, but I wasn't copying that across the the final results - that should be an easy fix
  • Total time was a bit of a pain - times are reported differently to ACC and I hadn't gotten around to sorting this. I think I have a possible solution which needs testing
  • I see there are some circumstances where average/best laps aren't calculated. I know invalid and in/out laps won't be counted, along with laps without reported sectors (which I regard as purely estimated times) - I'll check the rules and see if anything is wrong
 
Quick bug report: when driving the Aston Martin GT3, LMU-RC reads the file as if it was a Cadilac Hypercar (Cadilac V-lmdh)

What may or may not be useful:
On the Session tab, when selecting multiple sessions by Ctrl+click, all lap times of selected sessions are shown in the bottom window, with green and purple taking into account all laps from those sessions. This would be handy to compare lap and sector times across sessions.

Anyway, lovely tool, thanks!
 
Quick bug report: when driving the Aston Martin GT3, LMU-RC reads the file as if it was a Cadilac Hypercar (Cadilac V-lmdh)

What may or may not be useful:
On the Session tab, when selecting multiple sessions by Ctrl+click, all lap times of selected sessions are shown in the bottom window, with green and purple taking into account all laps from those sessions. This would be handy to compare lap and sector times across sessions.

Anyway, lovely tool, thanks!
I've just run a test session and I see that occasionally the AMR isn't recognised (the Cadillac ends up being the default car because of legacy reasons). I'll investigate and see what is going on

EDIT: Actually it is a very specific set of circumstances. In my case I didn't complete the 3rd sector on my quali lap, causing it to be incorrectly recorded. I want to confirm if this is the same issue as you. Can you export diagnostics - (instructions here)
 
Last edited:
I ran three separate private (Race Weekend) sessions and completed 10+ laps in each of them. I would have escaped to the pit at some point on my final lap before exiting the session.

I have exported/uploaded all three sessions. User ID is t-2D2UyhB1O_1mfPUWM8zKNQGyujaRDborJax5Ia-PE.

Thanks for your attention :)
 
I ran three separate private (Race Weekend) sessions and completed 10+ laps in each of them. I would have escaped to the pit at some point on my final lap before exiting the session.

I have exported/uploaded all three sessions. User ID is t-2D2UyhB1O_1mfPUWM8zKNQGyujaRDborJax5Ia-PE.

Thanks for your attention :)
OK - this was a reference data issue - I'd misnamed the AMR so it didn't recognise it in the files and didn't pick it up as I hated the car with the default setup so never raced it (I've just tried with the Coach Dave setups and it is a hoot, so I might give it the benefit of the doubt).

This will be fixed in the next update
 

LMU Results Companion 1.3.4 Released (here)​

• Replay control tweaks (add penalties to events that can be scrolled through)
• Total/Duration fields in session
• Fix colours in Lap Times widget
• AMR GT3 not recognised from past files
• Driver incorrectly reported in some log messages
 
Back
Top