mirror of
https://github.com/IAmTomShaw/f1-race-replay.git
synced 2026-05-09 08:25:56 +02:00
[GH-ISSUE #57] Feature request. Telemetry data F1 2025 game #14
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/f1-race-replay#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bart2004 on GitHub (Dec 16, 2025).
Original GitHub issue: https://github.com/IAmTomShaw/f1-race-replay/issues/57
Being able to use telemetry data from the F1 2025 game
@IAmTomShaw commented on GitHub (Dec 16, 2025):
This is a great idea and something that I'd love to add. I don't actually play the game so I'm not sure what telemetry can be accessed. We can look into this though :)
@Keshav02-rk commented on GitHub (Dec 16, 2025):
This sounds like a really interesting idea! While I haven’t explored telemetry from the F1 2025 game yet, it could be a valuable addition for replay and analysis features. I’d be happy to help investigate what telemetry data is accessible and potentially contribute to integrating it if needed.
@ImGoomes commented on GitHub (Dec 17, 2025):
This idea sounds amazing! I have the game and I can take a look on this as well.
@Yeshwant-Kasa commented on GitHub (Dec 17, 2025):
Basically if anyone can explain what telemetry are you guys exactly talking about?
I didnt quite get you.
@xhemals commented on GitHub (Dec 17, 2025):
You have to use a third party app and enable the UDP telemetry in the game settings. Unfortunately not a native thing that you can just export. It seems like SRT is an option to get the telemtry and also Team Telemtry but both of these tools don't seem like they have an export function, and the former has a cost associated.
It would probably be best to create a bespoke telemetry parser that will then save the data to load up again........
@IAmTomShaw commented on GitHub (Dec 18, 2025):
I've actually done this for iRacing in the past (so slightly different, but definitely something we can look at adding). I created a live pitwall for iRacing simulators for a tech conference last year :)
@xhemals commented on GitHub (Dec 18, 2025):
@IAmTomShaw there's a pre-built python package for getting the telemetry: https://pypi.org/project/f1-telemetry/. Seems like a good foundation to build a custom parser to get the data in the same way fast-f1 does so integrating is simple. Or at a minimum remove the unnessecary features (like the web gui for live telem).
I can start having a look. Thoughts?
@bart2004 commented on GitHub (Dec 23, 2025):
@IAmTomShaw @xhemals this is something I wanted to develop for over a while now. Just time is the issue for me but would be happy to help. So if I could help with anything then let me know. Thanks a lot for the enthusiasm.
@xhemals commented on GitHub (Dec 23, 2025):
@bart2004 I have started looking into the python package f1-packets. Let me know if you want to help me parse the data into the same format as fast-f1 so the race replay can show the data like real races
@bart2004 commented on GitHub (Dec 23, 2025):
Wouldnt it be better to make Dto's to map both data sources into and use those? Just to make sure we can maintain functionality in the future. Because there are quite a bit of data attributtes to be retrieved and that can get messy quite quick. But im am always open for suggestions.
@xhemals commented on GitHub (Dec 23, 2025):
@bart2004 It's a good shout tbh, but also feel like that would mean the whole original script would have to be rewritten to take in the fast-f1 data? Unless I am misunderstanding you.
@bart2004 commented on GitHub (Dec 27, 2025):
I am not saying it is bad. But creating one universal dto might improve maintain ability.
@bart2004 commented on GitHub (Dec 27, 2025):
I am going to look into this in 2 weeks time. My goal is to build it part of it myself.
@Theo-Tsang commented on GitHub (Jan 25, 2026):
I’ve already pulled the UDP data from F1 24 and parsed the motion packets. Do you have an implementation that parses the data into the same format as fast-f1?