Jump to content
Want to report an issue? Have a bug to report? Please look here first!!!! Read more... ×

UDP Telemetry: GForce values broken

Recommended Posts

Hello,

Wrote on the UDP specifications, but also writing this here. Found this bug, when testing new version of my Telemetry tool. I haven't really done any driving on the game for few months, but got back now and noticed this issue.

Platform: PC/Win 7

Version: Latest 1.21

Tested: All frequencies, broadcast and non-broadcast feed

The GForce values (Lat,Lon,Vert) in the UDP Telemetry data are mostly 0 and there are short blips with value. There was similar bug in F1 2018 at some point, but it got fixed. My last good "data" is from early November, where the saved lap data still has proper values from the Telemetry feed.

Image of "erroneous data".

v121_gLat_bad.png.a820691e340a8ed80922ce082463d771.png

 

What it should look like

v1x_gLat.png.9ff7d568bed4a7e94471f04740b54f4e.png

I hope this can still be fixed in the game.

Cheers.

 

Share this post


Link to post
Share on other sites

Very interesting find! The telemetry should get the attention it deserves too.
Also the 2nd sector times of other people usually don't get sent (hence, why you often have a purple 2nd sector) this is even the case for spectators (you can see the minimap get purple) 
And a huge downgrade from last year's game is that the driver names are also not sent... requiring race engineers to manually enter the names....
 

This game would benefit from being taken seriously a lot!

Share this post


Link to post
Share on other sites
17 hours ago, LonelyRacer said:

@Hoo  Any news on this?

Not yet. This is currently with the team to test.

Can I ask: where did you get the data for the second graph that shows how the G-Force data is supposed to look?

Share this post


Link to post
Share on other sites
48 minutes ago, Hoo said:

Not yet. This is currently with the team to test.

Can I ask: where did you get the data for the second graph that shows how the G-Force data is supposed to look?

That is from a saved lap data from prior November 2nd. The first version I have with bad data seems to be from Nov 5th. (I have 5GB saved data trace from October 15th, which still had the proper Gforce data).

The bug was not there in the beta or in the early releases.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×