UDP telemetry broken with patch 1.19?

Im on xbox.

Is 1.20 for PC only? I'm on PS, the latest is 1.19

The latest update 1.20 but have seen NO info on it anywhere.

Thanks 🙂

Thanks a lot for the info. This was really useful. I'll pass the info over to the dev team to take a look.

Hoobiechoobiefurther investigation:

• PS5 switched off and restarted --> same issue
• using another PS account --> same issue
• UDP 2023 --> confirmed same issue as 2024

• what I have just found out is that the bug looks related to TIME TRIAL ONLY

In fact if I run e.g. GP mode, I tested it with a Race, "history data" is updated as soon as a lap ends, and not only when the whole session ends (both UDP 2024 and 2023)

Last Lap / Best Lap code (in the center) is the same as in the previous TT dashboard (same result if I directly use the TT dashboard during the race). All is fine, sectors are correctly shown.

Hoobiechoobieyes I switched it to test both UDP, btw I have the issue with both :-(

Trying to investigate this is what I did and found out:

• restarted the game, UDP set to F1 24
•  started Time Trial session
• new report code below:

• during the session this is what my dashboard shows (set to receive F1 24 UDP data):

so 'current' data is right, same as track/car etc., same about throttle/brake, All Time Best and Delta (and my be Last Data from previous session), what is always 0 is "history data"

• and this is how 'history data' look like while running

• as soon as I click "End Session", so I get this screen

• immediately I get all the data from the ended session! This is how the dashboard is immediately loaded

• and here the 'history data' (as you can see data is changed and I have sector times)

• it looks like the update of 'history data' is not live anymore. Never had this issue before till 1.18 or previous games.
• There are some info I cannot understand, and I don't know if they may help, e.g. the sessionUID is a long number while running which becomes 0 with session ended.
• Or FrameIdentifier which is 22 while running, 6284 with session ended
• what is sure is that sector times are always 0 while running and they are loaded all of a sudden at the session end

Any ideas from this information?
Thanks again 

Thanks for the report code. Looking at the data, we can see the UDP format being switched between F1 24 and F1 23. Can you confirm what format you are using in the game and what format the app you are using is expecting?

Don't know if may be useful, Time Trial in Shanghai with Report Code JXKK-DRDG-HKHC-BASC

Hi, first of all thank you for reply :-)
F1 World -- Time Trial