Topics

Hi Piboso. 

I've been helping run race leagues for a while now, and it became evident very quickly that most riders try to stay within the rules, specifically valid track areas. However a small minority were more than happy to flaunt track limits and this soured the experience for me, which lead to monitoring the situation and applying penalties. I feel this makes the racing much better in that those playing fairly are no longer at a disadvantage.

The downside to this is that it takes a lot of time no matter how I approach it. On average 2-3 hours per race for track limits alone, plus other things I have to do for each event.  Apart from the obvious negative aspect of that, it disuades me from hosting more elaborate events. Whilst we have hosted Sprint/GP races and Superpole/Race1/Race2 events, I am reluctant to do it often as the toll and amount of free-time it consumes can be overwhelming.

What I am leading up to is whether you would consider some productivity tools/enhancements to enable this to be mostly handled 'in-game'.
What I have in mind is the ability to apply specific invisible, non-collidable objects to the track layout for the purpose of recording when a tyre has come into contact. Ideally detectable from one direction only to avoid triggering in the event of a rejoin. These boundary objects to trace the edge between permitted and non-permitted areas. The entire circuit would likely be unneccesary and perhaps undesireable if no advantage is gained, but def the entirety of corners plus some overlap to corner entry/exit.  Perhaps even existing terrain types could cover this.

I imagine GPB recording this in the same way it does with rider contact, so it can be reviewed and jump to those specific points in a replay. The time that would save alone would be immense.

Another possibility would be to optionally have dashboard/HUD warnings for when these events have been triggered.

To take it further, maybe even configurable parms in the GUI to enable/disable the Long Lap Penalty, and for how many infractions trigger a LLP, with a similar boundary box at the penalty lane with LL-entry and LL-exit boundaries to determine a valid lap being taken etc.

Thanks for your consideration.

Cheers,
Mark.

I have my 21b dedicated server exporting html results and replay files.

When accessing a b21 replay for the first time of a 20 rider grid there was no rider data present. No bikes visible and under the rider pull-down there were no entries.
Track conditions, race duration, smoke off the start line, dust particles etc were picked up.

I figured it was me but having tested this now with the M2 at Victoria, on two different dedicated servers I am of the conclusion this is a beta21b problem.

Has anyone else seen this or could possibly shed any light?

Cheers.

Afternoon Mr PiBoSo and all.

I've been onboard with GPB for a few months now, absolutely loving it and genuinely impressed at the thought and detail that I can see has gone into this software.

My own eye for detail however has been twitching every time I access the bike and track Mod lists. I fully understand in being community supported that any level of consistency is quite unlikely, but seeing such entries as M?, Moto?, Moto ?, Moto? 17, Moto ? 2018 etc etc and throwing the list into chaos is quite irritating. I appreciate the time and effort that everyone goes to in creating anything for this great game, so version control is not something I would advocate.

Instead, does the functionality exist for a category alias within the mod ini file to be specified, that purely affects the visual name in the list if present, and have zero effect on the other ini files that reference the cat name ?

I would welcome this ability with open arms, and sleep better at night. :-)