Hi @Borrer0
That's an interesting suggestion. I think that would be at least a different widget though. I've added it to the TODO list, but I cannot guarantee any release.
Hi @Borrer0
In the video on the front page you can see all necessary steps. I am not aware of any other setting in Content Manager or CSP that could disable these kind of apps. At least not in the default configuration.Where in Content manager is the option to turn on this app please?
First off, THANK YOU for all of your work. I am immensely appreciated and use both of your apps religiously, there are no substitutes! I came here to post the same question/issue as MaxFrames and to shed a little more light on it - In the F1 league I partake in, there is a looping practice up all week until race day (server link https://acstuff.ru/s/q:race/online/join?httpPort=8081&ip=108.48.84.222), and I always appear as position 1. Using the old/original Map Display, the positions update correctly, but the extended one doesn't update the positions in any of the practice sessions and possibly in Quali as well, I don't exactly remember. They do update in the race! I can run multiple successive laps on a circuit in practice and my position is always 1 despite others in the session posting faster laps, and anyone else in the server does not get a different position either. Interestingly (or not?) is the other drivers in the server do not go sequentially. What I mean is that if I am in the server (and thus showing 1) and someone else joins, they are not number 2, last night the other person was position 14 and a third person who joined was position 6. I am running CSP 1.80-346, but I've had this issue with the MDE prior to this CSP.Thanks for the info. I've tested it there (joined into existing sessions) and at least the laps that were completed after I joined didn't show up. Neither with 0.1.80-p346 nor with p218. So I guess both are bugged in these regards.
The app is using this field
View attachment 684455
and the value just never changes for any car (it has a different default in the 2 preview versions, but still it doesn't change, when someone has a new lap).
So maybe it only counts full laps without starting from the pits (so not Nordschleife Tourist) or there is simply a bug with that property in CSP. I currently have no other property I could use, so for now, that's just the way it is...
Thankyou for your reply! I will try this out, cheersIn the video on the front page you can see all necessary steps. I am not aware of any other setting in Content Manager or CSP that could disable these kind of apps. At least not in the default configuration.
See
- implement workaround for missing online properties (best laps) to calculate positions in time based sessions correctly
- will only use laps started and completed while being connected
Thanks for reporting to @FinnishFish, @MaxFrames and @Meatfraiche
I can't get the app to show position correctly in practice mode, I am always P1. I think for everyone else they order correctly, just my place is wrong so everyone elses is +1. The positions shown next to drivers names above their cars are correct. I'd really like to see who is faster and slower by looking at the map. Color modes and text modes are set to position, and it works correctly in race.
I have the same issue and IIRC I didn't have it initially, maybe it's to do with CSP preview 346?
First off, THANK YOU for all of your work. I am immensely appreciated and use both of your apps religiously, there are no substitutes! I came here to post the same question/issue as MaxFrames and to shed a little more light on it - In the F1 league I partake in, there is a looping practice up all week until race day (server link https://acstuff.ru/s/q:race/online/join?httpPort=8081&ip=108.48.84.222), and I always appear as position 1. Using the old/original Map Display, the positions update correctly, but the extended one doesn't update the positions in any of the practice sessions and possibly in Quali as well, I don't exactly remember. They do update in the race! I can run multiple successive laps on a circuit in practice and my position is always 1 despite others in the session posting faster laps, and anyone else in the server does not get a different position either. Interestingly (or not?) is the other drivers in the server do not go sequentially. What I mean is that if I am in the server (and thus showing 1) and someone else joins, they are not number 2, last night the other person was position 14 and a third person who joined was position 6. I am running CSP 1.80-346, but I've had this issue with the MDE prior to this CSP.
No te olvidé de ti o más bien de la solicitud de función. Hay un pequeño adelanto disponible ahora, ya que actualmente estoy finalizando la implementación.
View attachment 695915
Mostrará las líneas del sector, así como los bloques de inicio/final que se colorearán según las banderas (blanco/amarillo/azul) para tener también un indicador de color allí. Actualmente estamos trabajando en la configuración, pero se puede esperar que sea similar a los otros 2 widgets en términos de configuración.
Espero que esto sea lo que tenías en mente.
- implement MapDisplay Progress widget (similar to RaceLab's FlatMap)
- detect cars in pit lane and allow to hide them or scale them relatively to the marker size
- make position marker image configurable
- pin (default)
- circle
- flat circle (no gradient background, similar to circles in v2.X and v3.X)
- Fix: make position marker size independent from car rotation (driving up- or downwards was previously...
can i get a better explanation of what this is? is it sector 1 sector 2 and sector 3 or its just a display of the start of the pitlane and the end of the pitlane with the drivers inside of it, showing where they are at inside the pit lane.AW939 submitted a new resource:
Track Map Display (Extended) - Full map visualization
Read more about this resource...
The lines are dividing the sectors. I thought with the related settings names this might be self explanatory, but I'll add a small paragraph in the overview.can i get a better explanation of what this is? is it sector 1 sector 2 and sector 3 or its just a display of the start of the pitlane and the end of the pitlane with the drivers inside of it, showing where they are at inside the pit lane.
View attachment 696180
- implement replacement for function missing in csp versions before 0.1.80-p346
This might fix the bugs reported by @Juppek-S and @Shane Pitkin
Sorry for the inconvenience, I didn't test with older CSP versions for compatibility.
I've pushed an update. Please test again. It wouldn't work correctly with non-preview CSP versions.Hi -- I've always loved your app, but for some reason, just having v4.7 installed reduces my frame rate to 17 or 18 fps. Any idea why that would happen?
Yes, that was it! Works beautifully now, just as before. Thanks for the lightning-fast response. I am indeed on an older CSP version -- 1.80 preview 1, which is where I plan to stay -- so I appreciate the fix!I've pushed an update. Please test again. It wouldn't work correctly with non-preview CSP versions.
Otherwise I couldn't reproduce any slower processing. For me 4.7 is as fast and light on FSP as 4.6.
So if it's still not better I'd be interested in what CSP version you use, and maybe a screenshot of the LUA Debug app as mentioned in the FAQ. I can see the calculation durations in there, to maybe get a hint on the issue.
Neither, the positions are calculated internally because with the currently available CSP versions the leaderboard values are not available online. So the calculation ist done as similar as possible (based on best lap times in practice/quali or the race position in races)Very nice app!
Question: which positions are shown? From leaderboard or live time?
Are these still correct after a rejoin?
Thanks for the answer!Neither, the positions are calculated internally because with the currently available CSP versions the leaderboard values are not available online. So the calculation ist done as similar as possible (based on best lap times in practice/quali or the race position in races)
They will not be correct after a rejoin, because the used values for the calculation will get reset. So it's only based on what happened while you were connected.
That's sadly currently a limitation for LUA apps. Thoug they are also for the older python apps not correct when rejoining, as far as I am aware.