Codemasters Team
@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,
Hi,
How can I filter lane cutting warnings in the m_warnings attribute? There is no warnings type attribute in the lap data package.
