Codemasters TeamAbout 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
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.
@cjorgens79I must check the by myself but some people said to be that m_warnings now shows the total number of warnings accumulated, no matter it's kind.
This is not the way this works since the very beginning of this value and I am sure no one player or spectator is interested in how many warnings has a driver, only how many of them are the one that could ends in a penalty.
This are the one related to track limits during the race. Or I am a complete dumb since I am playing this game (2017)
So I am starting to realize that my info was wrong and the last patch does not change that, only fixes some issues in the event packet that do not affect the Lap Data packet m_warnings performance.
@Hoobiechoobie @cjorgens79
I check the UDP data in the game related to WARNINGS and Lap Data packet m_warnings are now counting some infringements that the game never did before.
In fact, if you select 2021 UDP format inside this game, m_warnings could have a different value that if you use 22 UDP mode.
So, I do not have any doubt that before the patch must be some issue with the Penalty Types, but right now we have a problem with m_warnings.
As a player and as a spectator of championships of this game, I ask you to use the 2021 m_warnings system also in F1 22 UDP mode, which has major relevance for drivers and spectators. How many warnings a driver has related to collisions is pointless. The 2021 system only takes into account the one that precede a penalty. Those are the significant one
@navarreitor wrote:@Hoobiechoobie @cjorgens79
As a player and as a spectator of championships of this game, I ask you to use the 2021 m_warnings system also in F1 22 UDP mode, which has major relevance for drivers and spectators. How many warnings a driver has related to collisions is pointless. The 2021 system only takes into account the one that precede a penalty. Those are the significant one
Got to agree with this. Especially since the most used dash and udp reader SimHub does not support the EventDataDetails packet as it conflicts with it.
I have already had 4 different leagues and multiple users complain to me as now the stewards/commentary/players cannot count the correct number of warnings anymore, as its only track limits that are important
A new category for track limits needs to be created especially as the e-sports season has started in the big leagues
Codemasters Team
@navarreitor wrote:
@Hoobiechoobie @cjorgens79
...
So, I do not have any doubt that before the patch must be some issue with the Penalty Types, but right now we have a problem with m_warnings.
...
Ok, I think I understand the problem now. You are using m_warnings in the LapData packet to work out corner cutting warnings received in that lap. However, since we fixed the warning replication issue, the m_warnings value now contains ALL warnings so it is no longer possible to work out only the corner cutting warnings from this value alone. The possible solutions seem to be:
I suspect the third option is not possible as it would change the packet structure, but I'll go and see what the dev team think.
@Hoobiechoobie wrote:
@navarreitor wrote:@Hoobiechoobie @cjorgens79
...
So, I do not have any doubt that before the patch must be some issue with the Penalty Types, but right now we have a problem with m_warnings.
...Ok, I think I understand the problem now. You are using m_warnings in the LapData packet to work out corner cutting warnings received in that lap. However, since we fixed the warning replication issue, the m_warnings value now contains ALL warnings so it is no longer possible to work out only the corner cutting warnings from this value alone. The possible solutions seem to be:
- Make m_warnings only show corner cutting warnings.
- Have the apps filter using the penalty event instead.
- Add a second warning value to store info about corner cutting warnings.
I suspect the third option is not possible as it would change the packet structure, but I'll go and see what the dev team think.
The first option making m_warnings only show corner cut warnings would be the most preferable since the most used application for these systems is 'SimHub' and doing this would make it work like it has been and how people are used to it. I would think if people wanted the infringements types etc they could still get all that stuff from the infringement types etc,
@navarreitor wrote:
I think m_warnings was a great tool in F1 2021 and remains working in the same way, if I am not wrong, in F1 22 using the 2021 data structure.
As it works now, counting ALL the warnings it has only an statistic value, not a real interest for the races.
In the F1 22 game using the F1 2021 data structure, m_warnings no longer works as it did, it now shows ALL warnings after the update.
@FG44141You are right, I just test it and I was completely wrong. My bad. I had a race last Friday and I use the 2021 format and have two incidents with 2 different cars that I thought were 'noted by the marshals'...but were not
Excuse me for this bad info.
Must test the 2021 game, but I delete it in my PC, so I must wait I haven't heard of any new patches for that edition though, so I guess it's business as usual.
@Hoobiechoobie ha escrito:
@navarreitor wrote:@Hoobiechoobie @cjorgens79
...
So, I do not have any doubt that before the patch must be some issue with the Penalty Types, but right now we have a problem with m_warnings.
...Ok, I think I understand the problem now. You are using m_warnings in the LapData packet to work out corner cutting warnings received in that lap. However, since we fixed the warning replication issue, the m_warnings value now contains ALL warnings so it is no longer possible to work out only the corner cutting warnings from this value alone. The possible solutions seem to be:
- Make m_warnings only show corner cutting warnings.
- Have the apps filter using the penalty event instead.
- Add a second warning value to store info about corner cutting warnings.
I suspect the third option is not possible as it would change the packet structure, but I'll go and see what the dev team think.
@Hoobiechoobie can you let us know what the dev team thinks?
I still think 1st option is the right one because even I can be wrong -I am not an app developer- I think no one app needs to know how many warnings a driver has and I doubt an increase of this value can trigger something valuable now.
Now, because before, when m_warnings only increase the value when cornering cuttings, was an simple and effective way to point out the risk of being penalized.
Hi,
How can I filter lane cutting warnings in the m_warnings attribute? There is no warnings type attribute in the lap data package.
Maybe a dumb/rookie question.
But can/does telemetry settings have any impact on gameplay performance in online racing?
basically wondering if telemetry settings can help or hurt how smooth online gameplay runs.
For example, would udp send rate 60 Hz risk a loss off performance by demanding more of the bandwidth with more frequent updates. Or would it be the other way round, 20 Hz would demand more because of more info being bunched up in less frequent updates.
Also, does UDP telemetry on/off have any relationship to how FFB is comunicated/sent to my wheelbase? (fanatec csl elite + lc setup)
If I don’t use any external telemetry app or don’t need data sent to any other machine, would telemetry on/off make any difference in online gameplay stability? Kinda wondered if it can impact how I recieve info from opponents on screen and/or how info on my position is sent?
And does broadcast mode On mean a heavier workload for my router recieving and sending packets vs. Off sending it all through an open port?
I suspect I might be making a problem out of things completly unrelated or simply missunderstood. But as I was trying learn how telemetry settings work and what they do, my logic got knocked out, for everytime I thought I understood something, the next thing always seemed to contradict and make me doubt what I previously thought was understood.
Tldr: If I don’t need to send telemtry data to any external app or machine, is there any telemtry settings that can improve online performance/smoothness?
