Community ManagerCommunity ManagerHey,
I'm the developer of Pitbox, a real-time telemetry companion app for F1 games that just launched today on the App Store.
Two things that would make a huge difference for third-party developers like me:
1. Native delta to leader right now we calculate this from m_totalDistance which works but it's a workaround. A native delta in the packet would be cleaner and more accurate for everyone. It would also allow apps like mine to correctly reconstruct the delta even when connecting mid-session, which currently isn't possible reliably.
2. Consistent lap numbering currentLapNum starts at 0 on the out lap and only becomes 1 when you cross the start/finish line. But SessionHistoryPacket uses 1-based lap numbers. This mismatch causes real headaches and forces every UDP developer to add special case handling. Just making it consistent across all packets would save a lot of pain.
These two things alone would meaningfully improve every third-party UDP app out there.
Thanks for opening this thread really glad EA is actively listening to the community on this.
Hey Pitboxapp
Native deltas were added in the F1 23 format to the lap data packet. Is this insufficient?
You are referring to a lap-numbering problem. Can you supply more information about it? Specific game modes, tracks?
-Groguet
Pitboxapp Sorry to "high-jack" this partially.
As Groquet said, the "Native Delta to Leader", the delta to leader is already in the lapdata for F1 23, F1 24 and F1 25.
On the lap numbering
The lap number is bit odd, when comparing with all other sims.
Here is how I would like it to be (and how it is in all the other games my Tool supports)
On P/Q/freeroam etc. (ie. non-Race)
- Session starts, current lap for all cars 1, when all cars are in pit
- After that, always when a cars passes start-finish line (on pitlane or on track), the current lap is increased by one. (One exception: If the start-finish is crossed on first outlap on pitlane, i.e. before driving out, then there is no +1 to current lap.
For Race Control, in typical Q session (with 1 + 2 fast laps) the data would be shown:
LAP 1 (outlap)
LAP 2 1:35.34
LAP 3 (inlap)
LAP 4 (outlap)
LAP 5 1:35.13
LAP 6 1:35.35
LAP 7 (inlap)
For a P session, the same would apply, i.e.
LAP 1 (outlap)
LAP 2 1:36.34
LAP 3 1:36.12
LAP 4 1:35.55
LAP 5 (inlap)
LAP 6 (outlap)
LAP 7 1:36.25
Now in P/Q during the outlap/inlap the lapnumber is "all over the place", i.e. after quali lap, it can show 2, but when you enter/leave the pits, it jumps to 1 etc.
For R, the lap numbering is ok as it is now.
Cheers
