Forum Discussion

Codemasters Team

4 years ago

F1 22 UDP Specification

Here is the current specification for the UDP telemetry output system for F1 22. To report any bugs with the UDP system, please add a new topic into the bug reporting section of this forum and ou...

Data Output from F1 22 v16.docx144 KB

f1 22

Hoobiechoobie

Codemasters Team

4 years ago

@Kafumanto wrote:

@Hoobiechoobie Hi. Any comment on #90: https://answers.ea.com/t5/General-Discussion/F1-22-UDP-Specification/m-p/11615700/highlight/true#M5972 ? Thanks.

It sounds like you want and additional parameter that records the total elapsed number of frames since launching the session in addition to the current frame counter (which is rewound when using flashbacks). Is this correct?

EDIT: Sorry, I see that you wanted the behaviour of m_frameIdentifier changed to be continuous, but was concerned that this might cause other issues where people are expecting to align data or interpolates based on the frame value. I'll discuss with the dev team to see what they would suggest here.

Kafumanto

Rising Rookie

4 years ago

@Hoobiechoobie wrote:
@Kafumanto wrote:
@Hoobiechoobie Hi. Any comment on #90: https://answers.ea.com/t5/General-Discussion/F1-22-UDP-Specification/m-p/11615700/highlight/true#M5972 ? Thanks.
It sounds like you want and additional parameter that records the total elapsed number of frames since launching the session in addition to the current frame counter (which is rewound when using flashbacks). Is this correct?

Yes, having a separate "total elapsed number of frames" is a valid option. It would allow us to correctly detect and process flashbacks.

Another viable option - not requiring changes to the current packet structure - is to make the "current frame counter" to not rewind when using flashbacks. I'm not sure its current "rewind" behaviour is useful to any third-party application (keeping in mind that the "session time" parameter is already correctly rewinding).

Thanks.