Codemasters TeamCodemasters Team
@IkoRein wrote:
I see there is now registration for the beta testing. Will there be something like this also available for content creators? I have registered for the beta, but I don't know how does the approval process work...
If you are an app developer and can help test UDP then we might be able to support your beta application. Please send me a DM if you've applied for the beta AND have previously been active in the UDP forum threads and we'll see if we can assist (it's a new process though, so can't make any promises).
In terms of development, we will have limited options to change the structure, but might be able to accommodate one or two requests as well as looking into any bugs raised. Feel free to post any thoughts or suggestions for the UDP system in here until we can get a new thread set up for the next game.
Codemasters TeamThis thread is nearly on 30 pages long, so it would be great if you could summarise any new requests again and I'll scour the new posts at least. 🙂
@HoobiechoobieHi, it would be nice to have these bug fixed:
- In Q 'm_driverStatus' has been broken since a while ( it was working well when the game was released). It works as expected for the driver sending the data and the first driver attempt. But then it never goes again to flying lap ( value 1)
- SpeedTrap event is not reliable. We get only a couple of events per race
- 'm_tractionControl' is 2 even for drivers having medium TC.
Improvements:
- something similar to 'm_warnings' but only for corner cutting, so we can know if the user will get a penalty the next infringement
- it would be nice that assists are taken from player setting. Right now when AI takes control of the car in pit lane, end of race or when the driver goes to menu, UDP sends all assists on.
If UDP is enabled in the beta I'd like to help testing it. I recall that in 2020 and 2021 the beta did not have UDP enabled.
I've registered to "EA PLAYTESTING" but there is nothing open for F1
As referred to with your last message, here I would also repeat following question asked last November (never seen any answer to it) :
I have a question regarding UDP data output documentation which is essential from my point of view to know, but concrete declaration completely missing even in most recent doc :
- unit definition for all "m_localVelocity" (assuming it should also be "m/sec")
- polarity for those velocity values missing (like positive to right / front / up direction or vice versa) also those may be still possible to evaluate
- polarity for all angular velocity components which is from my point of view most important since it is hard to evaluate
Also it would be for sure helping everybody who wants to involve in some application using this telemetry to define which direction in world space / local space should be meant (like e.g. X corresponding to lateral movement / sway, Z = longitudinal etc.).
I know this from other racing simulation's telemetry API where those direction (if different from standard definition) are clearly reported from the start. Makes it really much easier :-)
Just to explain where such question comes from : I have translated telemetry provider (software plugin) for a DIY motion simulator project (existing one for previous F1 sim already existing) to F1 20022 and it is working well yet for all standard effects (which can directly be derived from standard telemetry data values), but to add more sophisticated effects like traction loss etc. it is necessary to dig much deeper into existing tm to be able to proceed further motion calculation on parameter not offered in UDP output data.
Thanks in advance for your help :-)
Ok. Here is from the earlier posts
1) As the game is now sending out UDP data in many formats (legacy 2017, 2018, 2019, 2020, 2021 and 2022), could it be possible to add in the future (e.g. in F1 23) another field to the header identifying, for which game the data is for. Now one can play F1 22 game, but use one of the many data formats, and there is no way to automatically detect the game just from the feed. This causes issues, when people play newer game with old data formats and then the new game data gets mixed with old game data.
2) Is it possible to increase the frequency of the Damage packets. Now it is 2 times/per second, but if it could be increased to e.g. 10 times/second, that would be super and allow more accurate analytics.
3) Would it be possible to send out the speed as float instead of int? That would also allow more accurate analytics.
4) As the GamerID publication is still opt-in for the players, would it be possible to add a field to the ParticipantData to denote, if player name is public or not. Now we still need to check for 'Player', 'Joueur', 'Spieler' etc. in the name to detect, if the player name is real or not.
Cheers.
Codemasters Team
@IkoRein wrote:
Ok. Here is from the earlier posts
1) As the game is now sending out UDP data in many formats (legacy 2017, 2018, 2019, 2020, 2021 and 2022), could it be possible to add in the future (e.g. in F1 23) another field to the header identifying, for which game the data is for. Now one can play F1 22 game, but use one of the many data formats, and there is no way to automatically detect the game just from the feed. This causes issues, when people play newer game with old data formats and then the new game data gets mixed with old game data.
2) Is it possible to increase the frequency of the Damage packets. Now it is 2 times/per second, but if it could be increased to e.g. 10 times/second, that would be super and allow more accurate analytics.
3) Would it be possible to send out the speed as float instead of int? That would also allow more accurate analytics.
4) As the GamerID publication is still opt-in for the players, would it be possible to add a field to the ParticipantData to denote, if player name is public or not. Now we still need to check for 'Player', 'Joueur', 'Spieler' etc. in the name to detect, if the player name is real or not.
Cheers.
These should all be done, apart from one remaining query with the speed that we are looking into now.
