Codemasters Team
Codemasters Team
@navarreitor wrote:
About warnings
This could be a bug but for all the people that uses Simhub right now your solution is the proble
Simhub does not access the event packet, so we can't read penalization codes.
Moreover, what is the point to count warnings if it's not as a prelude to penalties.
The bug you think you had was the best way to approach this matter. No one cares how many other warnings have, only the ones that precede a penalty.
Please, reconsider this point
The change we made was a bug fix that applied to multiplayer sessions where some warnings were not coming through correctly. The underlying event system and warning types are basically unchanged from last year, and the functionality for local players is also the same, so this only affects certain infringement types that were not being recorded correctly in multiplayer sessions.
To understand the issue with specific apps, we'd need the developers to confirm what the issue is and what support they might need from us. Given the nature of the bug that we fixed, it doesn't seem appropriate to unfix this problem as it was a genuine bug that caused inconsistencies in the penalty data for remote players.
@Hoobiechoobie Could I propose that at some point the UDP data is updated with a new track limit warning code
Right now the standard warning is 'm_warnings' could a new line be added such as 'm_limitwarnings'
Maybe in a future update, as thats the most simple and efficient way to code it in on multiple applications, and track limit warnings are the only one Leagues care about when making info for them.
Many thanks
Codemasters Team
@FG44141 wrote:
@Hoobiechoobie Could I propose that at some point the UDP data is updated with a new track limit warning code
Right now the standard warning is 'm_warnings' could a new line be added such as 'm_limitwarnings'
Maybe in a future update, as thats the most simple and efficient way to code it in on multiple applications, and track limit warnings are the only one Leagues care about when making info for them.
Many thanks
The track limits were used strictly in Time Trial about 10 years ago, but we moved away from this to use a time-based system where this would only count as a warning or penalty if a time advatange was gained when exceeding the track limits. This prevents excessive and unnecessary penalisation of players. In terms of league moderation, the different current corner-cutting infringement types should cover this more effectively than trying to expose a new parameter solely looking at track limits.
As we no longer track the track limits themselves as a reason for allocating a penalty, this would require a chunk of bespoke work to do, so we'd want some proper use-cases to underhand what you need and how we can support that.
My application provide dashboard for commentator and dashboard for racer (he ask a buddy to check the live, and he give him his dashboard link where there are data about his car, lap time etc).
The track limit warning is usefull and his used a lot of time by commentator. And the engineer can also know how many warnings have others racers and told to his racer to be careful and wait the third error from the guy in front of him.
I like the idea to put it on lapdata because sometime, the packet 3 event is lost and i have "problem" like 6s penalty and 5 warnings.
