LMU Analyzer

[armin]

I should be so lucky, I have quite a few 'tail enders'.....

ya...i also think the benchmark times are probably a bit too fast, but I fully rely on the ohne_speed spreadsheet which is really great...and I am anyhow not good enough to rate it, so will stick to that. But - if they update the sheet, it will also be reflected in lmu analyzer.

Loving this tool, keep up the amazing work.

I have spotted an issue. The track name in the benchmark times tab for Paul Ricard (1A v2 short) is wrong. The game gives back Paul Ricard - 1A-V2-Short.

So i have zero sessions in the Paul Ricard (1A v2 short) one where the benchmark times are and 3 sessions in the Paul Ricard - 1A-V2-Short where there are no benchmark times.

I just published a new version which should fix this. please let me know if it doesnt (check version in about tab - upper right side - should show Build 24 Apr 09:44 => if it doesnt, wait a bit or press F5 a few times

There is something you need to fix, as you can see the category is not recognised


View attachment 14276

i checked it with my data and for those, it detects Oreca 07 as LMP2-ELMS, but maybe you use different year or series or whatever. could you please check the LMU Analyzer version (About - upper right side) that it is higher than 14 Apr. If it is, could you open the XML file of one of the session in a text editor and check what values you have in <CarType> and <CarClass>. alternatively, you could also DM me one of the XML files so I can check it.

thanks all for the feedback!

 

[kartname]

ya...i also think the benchmark times are probably a bit too fast, but I fully rely on the ohne_speed spreadsheet which is really great...and I am anyhow not good enough to rate it, so will stick to that. But - if they update the sheet, it will also be reflected in lmu analyzer.


I just published a new version which should fix this. please let me know if it doesnt (check version in about tab - upper right side - should show Build 24 Apr 09:44 => if it doesnt, wait a bit or press F5 a few times


i checked it with my data and for those, it detects Oreca 07 as LMP2-ELMS, but maybe you use different year or series or whatever. could you please check the LMU Analyzer version (About - upper right side) that it is higher than 14 Apr. If it is, could you open the XML file of one of the session in a text editor and check what values you have in <CarType> and <CarClass>. alternatively, you could also DM me one of the XML files so I can check it.

thanks all for the feedback!

<Driver>
<Name>Marcello Bellingheri</Name>
<Connected>1</Connected>
<VehFile>397_25ELMS_ORECA07.VEH</VehFile>
<UpgradeCode>08000800 00000000 00000000 00000000</UpgradeCode>
<VehName>Oreca 07 ELMS Custom Team 2025 #397</VehName>
<Category>ELMS 2025, LMP2_ELMS, Oreca 07</Category>
<CarType>Oreca 07</CarType>
<CarClass>LMP2_ELMS</CarClass>

 

[XaG]

ya...i also think the benchmark times are probably a bit too fast, but I fully rely on the ohne_speed spreadsheet which is really great...and I am anyhow not good enough to rate it, so will stick to that. But - if they update the sheet, it will also be reflected in lmu analyzer.

The point is, as previoulsy noted by leppie, that according to Ohne Speed's spreadsheet, 101-101.9% should be rated as Competitive, 102-103.9% should be Good, etc. The ratings applied by your app are one rank below.

 

[Energy2k8]

@armin My Paul Ricard 1a v2 short is working fine now. Thank you!!

 

[armin]

<Driver>
<Name>Marcello Bellingheri</Name>
<Connected>1</Connected>
<VehFile>397_25ELMS_ORECA07.VEH</VehFile>
<UpgradeCode>08000800 00000000 00000000 00000000</UpgradeCode>
<VehName>Oreca 07 ELMS Custom Team 2025 #397</VehName>
<Category>ELMS 2025, LMP2_ELMS, Oreca 07</Category>
<CarType>Oreca 07</CarType>
<CarClass>LMP2_ELMS</CarClass>

hm...tried it and it should work with this data. can you please try to reload all data/re-import the xml. maybe its a caching issue - reimport recalculates it...maybe that fixes it

 

[armin]

The point is, as previoulsy noted by leppie, that according to Ohne Speed's spreadsheet, 101-101.9% should be rated as Competitive, 102-103.9% should be Good, etc. The ratings applied by your app are one rank below.

ok, ya, valid point, thanks! fixed in latest version

- 100.99 => Alien
101.00 - 101.99 => Competitive
102.00 - 103.99 => good
... and so on

 

[Atomic Andi]

102.00 - 103.99 => good

OMG, I got sooo good this week!

I would personally leave out the Alien column and move the percentage further left - it's the important bit after all
next target could be last. "gap" is a bit misleading
nitpicking now, but hey

 

[Energy2k8]

Can you check the sector timings for Imola? After 1.3.3 patch the sector timings are not correct anymore. My sector 1 is 9 seconds quicker, sector 2 is 3 seconds quicker and sector 3 is 12 seconds slower.

 

[armin]

Can you check the sector timings for Imola? After 1.3.3 patch the sector timings are not correct anymore. My sector 1 is 9 seconds quicker, sector 2 is 3 seconds quicker and sector 3 is 12 seconds slower.

just checked it - those are the sector times coming from LMU. i have the same differences - so its an issue of LMU

 

[WarmRed]

Thank you so much for your work here...

Could you integrate the top speeds and driver aids for each driver into the overview table? Currently, you have to select each driver individually, which is cumbersome. Is it possible to view the tire wear values somewhere?

 

[Energy2k8]

Is it somehow possible to excluse sessions from the results? With the change in sector timings at Imola, the theoratical times are way off. I want to exclude all my previous imola attempts to basically start over for that circuit.

 

[armin]

Thank you so much for your work here...

Could you integrate the top speeds and driver aids for each driver into the overview table? Currently, you have to select each driver individually, which is cumbersome. Is it possible to view the tire wear values somewhere?

hey!
ya, just added it. with new version, you get:
- top speed & tyre wear/lap is shown in overview
- there is a new tab "Tyre Wear" in session view
- session view allows to click on another driver and you'll see all infos about this driver (e.g. Aids are shown in the driver info)

 

[armin]

Is it somehow possible to excluse sessions from the results? With the change in sector timings at Imola, the theoratical times are way off. I want to exclude all my previous imola attempts to basically start over for that circuit.

not in lmu analyzer, but you can move all the xml files that contain imola sessions into a separate folder - e.g. a subfolder "archive". lmu analyzer only reads the XML files from the folder you select - subfolders are ignored

 

[leppie]

not in lmu analyzer, but you can move all the xml files that contain imola sessions into a separate folder - e.g. a subfolder "archive". lmu analyzer only reads the XML files from the folder you select - subfolders are ignored

I does not remove the results previously imported though, unless you start from scratch. Not a biggie though.