Hopefully it is fixed in v1.5.0 Delete the file LMU-Results.DB and it should try to reprocess all your results file
LMU Results Companion
- Thread starter doug99
- Start date
LMU Results Companion 1.5.1 Released (here)
• Redesigned accident replay control• Session final standings
-> Properly account for post race penalties
-> Gaps now for class only
-> Fix default sorting
• Retry queries when DB locked (no need for manual refresh)
• Add session Refresh button
• Reshuffle controls on sessions screen
• GT3 now green (race number flash and leaderboard widget)
• Update LMU versions
• New cars recognised with custom liveries
skywalker22
Active member
Is it possible to include also the Practice sessions of Daily (Weekly and Special) races?
These are on separate servers, and only run practice for some particular race, which comes afterwards.
These are on separate servers, and only run practice for some particular race, which comes afterwards.
They should already be recorded. For instance, the sessions highlighted in red are all from a daily race. The first practice highlighted is from the free practice before the session started
skywalker22
Active member
Strange, but after the today's app update, I did a practice and the session is there now. Don't know why I don't have any previous practice sessions...
Anyway, I have 2 questions:
1. How do you color fields like Lap time and sectors (like you have it)?
2. Wear (FL, FR, RL, RR) shows some strange %s. Can you take a look into it? Example bellow is 20min race at Spa.
Anyway, I have 2 questions:
1. How do you color fields like Lap time and sectors (like you have it)?
2. Wear (FL, FR, RL, RR) shows some strange %s. Can you take a look into it? Example bellow is 20min race at Spa.
Customising Appearance
Colours
All the colour settings can be customised on the Colours page
Dark Mode
The default scheme is the standard Windows scheme. If you prefer to have a dark theme, use the Dark Mode setting. You can choose to override the background and window colours.
Lap/Sector Times
You can configure the scheme used for lap and sector times
The different types available are
Colours where faster or slower than real life records.
Click each button to choose a colour
Results
Used to configured the colours for the different sections of Result Statistics. Click each button to change the colour. (Note P1/P2/P3 are always Gold/Silver/Bronze)
Font Colour Contrast
Slider to decide the contrast on fonts on coloured areas (ie when font switches from black to white dependent on background.
It can be seen how this is displayed by the test buttons on this screen.
Here, with the default setting, only the black background causes the font to switch to white.
When the slider is moved to the right, you can see the display changing.
Therefore you may want to reduce the weighting for blues
This will adjust the blue contrast without affecting reds/greens
Heatmaps
Heatmaps can be used instead of the standard schemes in certain list views (eg Circuits). Choose the slowest and fastest colours by clicking on the relevant buttons. A 3-way heatmap means that the mid point transitions through a 3rd colour.
No Heatmap
If no heatmap used, then just the faster, slower colours used.
Standard heatmap
The standard heatmap blends from a slow colour to a fast colour. Click on Slowest/Fastest buttons to adjust colours
3-way heatmap
Similar to above but blends via a midpoint colour. Click on the mid-point button to customise
Customising Columns
If you want to show or hide extra columns, right click on the column header and choose the columns you want to chow or hide.
Columns can be re-ordered by dragging the column header. You can re-size the columns widths by dragging the column edges.
In addition, you can sort by fields by left clicking the column header
Help
Help is always available by pressing F1 or the ? button
Colours
All the colour settings can be customised on the Colours page
Dark Mode
The default scheme is the standard Windows scheme. If you prefer to have a dark theme, use the Dark Mode setting. You can choose to override the background and window colours.
Lap/Sector Times
You can configure the scheme used for lap and sector times
- The default is the ACC scheme (the same as ACC uses)
- "F1 Scheme" is similar to that used by Formula 1
- Custom Scheme allows you to choose your own colours. Click on each of the buttons (Slower/Faster etc) to choose a colour
The different types available are
- Slower – no improvement on fastest time/sector
- Faster – fastest lap/sector so far
- Sector Max – Faster sector in session
- Record lap – Fastest lap in session
- Invalid – Track limits exceeded: Invalid lap
Colours where faster or slower than real life records.
Click each button to choose a colour
Results
Used to configured the colours for the different sections of Result Statistics. Click each button to change the colour. (Note P1/P2/P3 are always Gold/Silver/Bronze)
Font Colour Contrast
Slider to decide the contrast on fonts on coloured areas (ie when font switches from black to white dependent on background.
It can be seen how this is displayed by the test buttons on this screen.
Here, with the default setting, only the black background causes the font to switch to white.
When the slider is moved to the right, you can see the display changing.
Contrast tuning by colour
The contrast can be fine tuned by colour (for example blues can be darker than greens/reds)
Therefore you may want to reduce the weighting for blues
This will adjust the blue contrast without affecting reds/greens
Heatmaps
Heatmaps can be used instead of the standard schemes in certain list views (eg Circuits). Choose the slowest and fastest colours by clicking on the relevant buttons. A 3-way heatmap means that the mid point transitions through a 3rd colour.
No Heatmap
If no heatmap used, then just the faster, slower colours used.
Standard heatmap
The standard heatmap blends from a slow colour to a fast colour. Click on Slowest/Fastest buttons to adjust colours
3-way heatmap
Similar to above but blends via a midpoint colour. Click on the mid-point button to customise
Customising Columns
If you want to show or hide extra columns, right click on the column header and choose the columns you want to chow or hide.
Columns can be re-ordered by dragging the column header. You can re-size the columns widths by dragging the column edges.
In addition, you can sort by fields by left clicking the column header
Help
Help is always available by pressing F1 or the ? button
Last edited:
Hi,
I've put a post above (Changing Appearance) describing how to change colours etc. Also, there is a bit more information if you press F1 to bring up the help.
Regarding tyre wear, there was an issue prior to v1.4.3 where things like tyre wear were added to the wrong laps. Ensure you have the latest version (V1.5.1). You can update older sessions by right clicking and selecting Re-pair race/reload results file.
If you have the latest version and the above doesn't fix this, let me know and I'll look into it further
Tophattingson
New member
I am having difficulty understanding what LMU Results Companion treats as an invalid lap - I can do multiple laps in a row where the game does not even check for track limits and they can all still count as invalid. In particular I'm finding I get maybe only 1 in 5 valid laps register as actually valid when driving the LMP2 at Imola. What criteria is being used for an invalid lap?
I'm afraid it is LMU being a bit weird. If you exceed track limits, LMU reports it in the data as an invalid lap. This is the only thing I have to go on. However, in it's own in game results, it may say the lap is valid if you didn't get a penalty, so it isn't being consistent.
skywalker22
Active member
This is my understanding, so it could be completely wrong, but...
LMU reports "Lap is not valid for best" in shared memory if you exceed track limits at all - ie all 4 wheels over the white line, although some places are more lenient than others. However, the difference lies in the track limits pop-up message (green - no penalty due to no time gained or yellow/orange/red some sort of penalty). all of these will fire a "not valid for best" status and be flagged as such in LMU-RC and Crew Chief etc. For yellow/orange/red, LMU doesn't record a best time. For green, it is a little inconsistent. While still an invalid lap, LMU will sometimes treat as valid (for best laps etc) - depending on whether qualifying or race and how extreme the excursion was.
IMHO, LMU's approach is not correct - if you exceed track limits, it's best just to record as such. In terms of races, it makes no real difference - it only really makes a difference in terms of recording best laps
I didn't realise anyone was actually using this - I thought I'd disabled the option to select other languages! Did you select it in the past or did the app decide automatically to display in German (I can't remember how it works exactly)?
I never really finished the translation or got round to a mechanism to support other languages. I'll have another look and see if I can make it all fit
EDIT: OK so it only switches to German on the fuel page - I think I must have turned it off for everything else. I'm going switch the fuel page back to English. If I ever get the time to complete the translation, I'll turn it on again
Last edited:
wolke
Active member
fresh install and just browsing, didn't set anything. but i also used ACCRC. More languages would be great, i bet there are a lot who would help out with translating. oh and big thx for the tool, that i now can see and compare my old laptimes is great
Last edited:
Tophattingson
New member
Even this doesn't make sense, I have sessions where I am certain I have laps that never went over the track limits enough for the green no penalty ui to show up, and yet it still records every single lap as invalid.
Edit: Even weirder, deleting the session and then replaying it from backup completely changes what laps are treated as valid, alongside changing the number of laps including removing laps that look like duplicates. In fact, it causes it to look correct according to what I recall about which laps were and were not invalid, unlike the first time the session is created.
Edit: Even weirder, deleting the session and then replaying it from backup completely changes what laps are treated as valid, alongside changing the number of laps including removing laps that look like duplicates. In fact, it causes it to look correct according to what I recall about which laps were and were not invalid, unlike the first time the session is created.
Last edited:
Tophattingson
New member
AlanR_77
Active member
Definately something has changed since the update on 10th June.
Here are some numbers from the laps I completed at Le Mans:
Before 10th June Update:
Laps logged: 84
Valid laps: 63 (75%)
Invalid laps: 21 (25%)
After 10th June Update:
Laps logged: 278
Valid laps: 62 (22%)
Invalid laps: 216 (78%)
And at Monza:
Before 10th June Update:
Laps logged: 379
Valid laps: 295 (78%)
Invalid laps: 84 (22%)
After 10th June Update:
Laps logged: 506
Valid laps: 182 (36%)
Invalid laps: 324(64%)
**Of course some of these invalid laps are laps that I didn't complete; some are genuine invalid laps. I would estimate I drive around 90% valid completed laps, so getting a retunr of 22% or 36% is very fishy.
LUM-RC indicates that invalid laps prior to 10th June stopped recording triming data from the pojnts of the invalidation incident, so there are many laps with no sector times; i.e. invalidate a lap in sector 2 and neither S2 or S3 split times are recorded. Since 10th June all completed sectors have a split time displayed regardless of them being valid.
A line from the results xml file:
<TrackLimits Driver="Katzen Jammer" ID="0" Lap="4" WarningPoints="0.5" CurrentPoints="0.5" Resolution="3" et="1325.2">Invalid Lap Cut Track</TrackLimits>
Can it be possible for LMU-RC to read this file in a way that it will only show a lap as invalid if it sees Lap="x" WarningPonts = ">0"?
(This may be a silly or simplistic question; I have no idea on coding this kind of thing).
It would appear every off-track warning, even if it is green, plus every reported contact (with post/imoovable/vehicle etc) warning, turns up an invalid lap, and this makes this brilliant tool sadly quite ineffective.
Here are some numbers from the laps I completed at Le Mans:
Before 10th June Update:
Laps logged: 84
Valid laps: 63 (75%)
Invalid laps: 21 (25%)
After 10th June Update:
Laps logged: 278
Valid laps: 62 (22%)
Invalid laps: 216 (78%)
And at Monza:
Before 10th June Update:
Laps logged: 379
Valid laps: 295 (78%)
Invalid laps: 84 (22%)
After 10th June Update:
Laps logged: 506
Valid laps: 182 (36%)
Invalid laps: 324(64%)
**Of course some of these invalid laps are laps that I didn't complete; some are genuine invalid laps. I would estimate I drive around 90% valid completed laps, so getting a retunr of 22% or 36% is very fishy.
LUM-RC indicates that invalid laps prior to 10th June stopped recording triming data from the pojnts of the invalidation incident, so there are many laps with no sector times; i.e. invalidate a lap in sector 2 and neither S2 or S3 split times are recorded. Since 10th June all completed sectors have a split time displayed regardless of them being valid.
A line from the results xml file:
<TrackLimits Driver="Katzen Jammer" ID="0" Lap="4" WarningPoints="0.5" CurrentPoints="0.5" Resolution="3" et="1325.2">Invalid Lap Cut Track</TrackLimits>
Can it be possible for LMU-RC to read this file in a way that it will only show a lap as invalid if it sees Lap="x" WarningPonts = ">0"?
(This may be a silly or simplistic question; I have no idea on coding this kind of thing).
It would appear every off-track warning, even if it is green, plus every reported contact (with post/imoovable/vehicle etc) warning, turns up an invalid lap, and this makes this brilliant tool sadly quite ineffective.
OK - there's something odd going on here. Can you export the diagnostics (instructions here). In addition, I'll also need the LMU Results file. Right click on the session and select Open Results File. The file will be displayed in the default app (normally a browser)
Also can you get the backup file. This is a bit more painful. Go to the LMU-Results\Backup\Results folder - you should be able to identify the backup from the date and name. I'll see why there is a discrepency
Hi Alan,
Thanks for the detailed analysis.
A bit of history - previously I took the invalid lap from shared memory. This indicated an invalid lap as it happened and also if the last completed lap was invalid. The first is a bit wonky due to timing issues - although this only affects the laps widget (sometimes the lap after an invalid one is shown as invalid) but the results takes it from the previous completed lap.
Previously, the LMU Results file had no indication of invalid lap, other than posting no laptime. After June, that all changed. I think you sometimes get laptimes for invalid laps, but as you say, now the tracklimits indicators are there. At the moment, I only use these for the accident replays, but if things are going sideways, I'll probably have to move across to using these.
With the blank sector times, previously, LMU would not give a time for invalid laps from the moment the track limit occurred. I tried to fill in the gaps as in some cases I had enough information to calculate this. IIRC, that all changed after June. The good side was that more information was provided, the bad side was that a lot of invalid laps were showing as valid.
I can't remember all the details, but I will always invalid an outlap and possibly an inlap otherwise dependent on tracks you can get a ridiculously short laptime. For these purposes, invalid lap means not valid for best. I think also if a car didn't complete the last lap, I invalidate it
EDIT - I haven't run a huge amount of races since June, but if I look at the last, I ran 12 laps, 7 of which were invalid - this tallies with the track limits entries in the LMU results file. I'd have to review the replay file to see if this looks right