It looks like you’re new here. To join in the discussion, click the register link below to get started.
Thank you, thing is though one would think it would read what the pressure was set to in the set up, default in most cases is around 23.4 on the fronts and 21.9 or something on the rears. It should also change a bit as the tyres heat up and cool down.So tyre pressure data is possibly not being output in the UDP data correctly. But yes the false readings are most likely a EKSim implementation error.
Thank you, thing is though one would think it would read what the pressure was set to in the set up, default in most cases is around 23.4 on the fronts and 21.9 or something on the rears. It should also change a bit as the tyres heat up and cool down.
So tyre pressure data is possibly not being output in the UDP data correctly. But yes the false readings are most likely a EKSim implementation error.
we may need to do a more significant re-write / re-organisation of our data to allow us to better control what data is sent when. This amount of work wouldn't happen before release though...I'll let you know if this is something we can get into the current title.
There are a few changes that will be in an initial update for the game. I need to sort out what changes will be available when and will update this thread.
Hello All. Here is a summary of the various UDP issues raised
by you in this thread. There have been some changes to the structure, so apps
using the older structure may need updating. I’ve updated the specs on page 1
of this thread, with the newly added fields marked with NEW in the comment. I’ve
also updated track, car and driver IDs to include the classic content.
Changes in release
build (version 1.3):
Allow UDP output to be set from the hardware
config file (done – see new notes in the first post on this thread)
Add penalty info into UDP data (added as m_penalties)
Display engine RPM as a % of maximum RPM (added as
UDP output uses m_trackPosition and
m_car_position for same info (now uses m_carPosition in CarUDPData
Best lap in UDP output data uses invalid laps (fixed
– this now only uses the best valid lap)
Add a field in UDP output to indicate when a
player is spectating (added as m_is_spectating)
Have currently viewed driver index in UDP output
when spectating (added as m_spectator_car_index)
Add session time remaining into UDP output for P
/ Q sessions (added as m_session_time_left)
Pits value stays on after the car exits the pits
(behaviour is now: 0 = Car in on track, 1 = Car enters the pit lane (limiter
on), 2 = Car enters pit box, 1 = Car exits pit box, 0 = Car passes pit wall
Add raw motion data to give greater accuracy on motion
Add unique session ID to help correlate UDP
Ignore the SLI-PRO device when the SLI-PRO
setting is set to OFF
Tyre Pressure readings always show 18psi in UDP
Won’t fix this year:
Fuel load only updates when going to track
Add support for showing car setups in the UDP
Output player names via UDP output
Continue to broadcast CarUDPData after player
has finished the race
Latency when receiving UDP results for other
players in online sessions
Please be aware that we are still looking at two potential changes
that will affect the data structure if implemented. I’ll give you notice on
this thread before these additional changes drop into the build.
v1.3 is the day 1 patch version. Users installing from a disc will have v1.0 which will use the previous specification.
Is anyone having audio problems on pc game?
My G27 isn't at all recognized by the game. I have tried all recommendations including re-installing the logitech profiler and relevant drivers but nothing seems to work. When I downloaded a G27 control profile from the steam workshop, it shows in the control menus, however it also reads that the required devices (G27) are not connected. The wheel works perfectly fine with other games, it's only F1 2017 where it isn't being recognised.
@Hoo - Do you think we might be able to get a forum section dedicated to 3rd party apps using your telemetry api?I was thinking that a category called "F1 Games - Companion Apps"Inside that you could have a stickied "readme first" that clearly informs everyone that the 3rd party apps listed are not made by Codemasters and that any support queries relating to those apps must be directed to the developer of the app.Each app developer could have 1 thread inside this category specifically for their app, where they can detail what their app does, provide some screenshots and provide support for their apps via questions posted by users into that thread. CheersCraig