I exported the diagnostics for the latest hotlap session at Brands Hatch. My user ID was Al1gbBaI3MwYQU5dltrLHeJccVwyeFSxlDmXAQ69K08Can you export the diagnostics (instructions here) then I'll have a look.
Be sure to let me know the generated userid so I know which is yours
Cheers
Doug
Thanks - this will be fixed in the next releaseHi Doug,
very small bug in Settings UI. Tooltip on max CPU value is wrong. It's the one from broadcast retry.View attachment 533810
I think it is because you were showing the average timesI exported the diagnostics for the latest hotlap session at Brands Hatch. My user ID was Al1gbBaI3MwYQU5dltrLHeJccVwyeFSxlDmXAQ69K08
Oops lol. Yup, that fixed it! Thank you so much!I think it is because you were showing the average times
View attachment 533889
View attachment 533890
Can you give me a bit more detail about the issue. Where is the time not showing? Is it not showing on the Sessions, Circuits, Leaderboards or the Car/Track History pages, or on results summary dialog?Hi, I really like the app, but there is major issue: it is not able to capture the last lap time you do when the session is already over.
I have been watching it for a while, as I often do my PB at the very end. The session time is already over and it just waits for the last drivers to finish their lap. This time never shows up in the statistics.
I run SimHub in parallel and the lap is recorded there.
The tooltips in the overlays section are also wrong:
View attachment 534437
Also a small advice for tooltip, make them as small as possible or at least use carriage return into it to avoid a very long line.Thanks for spotting the incorrect tooltips. They will be fixed in the next release.
The lap time is not displayed in the session.Can you give me a bit more detail about the issue. Where is the time not showing? Is it not showing on the Sessions, Circuits, Leaderboards or the Car/Track History pages, or on results summary dialog?
Or do you mean that you put in a lap after the chequered flag (when ACC says press escape or whatever to finish)? If you mean this, then this is probably something that won't be changing. It is tricky enough trying to determine when a new session starts or one finishes and the end of session is one such cue. I'm attempting to save a valid session record (where laps after the chequered flag would be discounted anyway).
Thanks for spotting the incorrect tooltips. They will be fixed in the next release.
I can't reproduce this at the moment. Can you export the diagnostics (instructions here) and I'll see what is going on. Also, can you point me at which races had the problemThe lap time is not displayed in the session.
If a session lasts 30 minutes and you cross the start-finish line at 29 minutes and start another lap, the session will continue until you complete the lap or invalidate it before. This last lap is always missing for me.
The sceenshot shows the ACC Results Companion on the left and SimHub from the same session on the right. The green arrows show the matching lap times from the beginning to the end of the session. I don't know why SimHub starts counting at lap #2.
At the bottom, there is another time in SimHub (#29), which I achieved when the official session duration was over, but I had started the lap before it ended. This lap time is missing on the left.
View attachment 534795
- Widget appearance shows all selected widgets rather than a test widget
- Optimal time added to lap times widget
- Race lap 1 no longer eligible for best lap (an attempt is made to adjust for ACC random offset, and this is not reliable)
- Damage widget added
- Only allow one instance of widget appearance dialog
- All tooltips now wrap rather than being one long line
- ARC CPU now reported to 1 decimal place
- BUGFIX: CPU widget not initialised correctly until appearance...
Hi,Morning! I’ve returned to ACC after some time away and run an online race every Tuesday. Was hoping results companion would help capture the results for me but it doesn’t seem to update the main page or recognise any online/server led races - is that a known limitation or am I doing something wrong?
{
"updListenerPort": 9000,
"connectionPassword": "asd",
"commandPassword": ""
}
I've got an idea why that might be. I'm trying to support spectator sessions but I have to use an alternate method to detect and save sessions. This has probably caused some regression.Hi Doug,
With the latest version (1.14.1) , very often a hotstint session appears twice in sessions result. One session is complete, the other showing only one lap, the last one. This evening, three out of four sessions comes with this extra session record.
Version 1.14.0 was ok (and didn't see it since a long time).
Could you check on your side if it happens ?
Diagnostic uploaded. FYI, I have deleted the 'extra' session but I think you will be able to get the content in backup json file.I've got an idea why that might be. I'm trying to support spectator sessions but I have to use an alternate method to detect and save sessions. This has probably caused some regression.
Can I ask you to export the diagnostics. This should help me to identify how to address this
Thanks
Thanks for the information - that looks like it will help me to reproduce.If it could help you, I have a workflow that is generating the double session record.
After a first hotstint, I quit ACC and see correctly recorded session in ACC manager. But the footer still display the following "Hotstint PostSession RaceMode'
Then I restart ACC and do another hotstint then quit again.
Second hotstint is correctly recorded but from the previous hotstint, a new record is in the list, containing last lap of first hotstint. And footer still display "Hotstint PostSession RaceMode"
@unpierrot - I think I found it. For hotstints particularly, when a connection is made to UDP, ACC will spit out the last lap, despite that session being over. I've just got to do some testing on a fix before releasingThanks for the information - that looks like it will help me to reproduce.
Just to explain what I can see so far. Your hotstint is saved when you finish. If you are not currently in a session according to shared memory, then ARC will still poll ACC on broadcast as you might have joined a multidriver race where you aren't the first driver. It looks like some residual information might be being picked up. I'll have to see if it is intermittent (in which case it is probably a timing issue and not everything has been cleaned up) or it can be reliably reproduced, in which case I just need to make sure everything is cleaned down properly.
I'll see if I can get some testing done at the weekend