Forum Discussion

Re: [UDP] stage_current_distance increases when driving to the opposite direction.

Hi there, as read from the UDP Telemetry Guide v1.3:

The title sends packets at specific times over the lifetime of a packet “scope”

and there're scopes like "session_start", "session_end", "session_pause", "session_resume" and "session_update". I tried them and found only they differed on ip/ports, channels inside, frequency etc. but the packets I recieved are during the whole lifetime of the session, not "specific times". 

for example, "session_start" send me packets from the beginning when the car is on the track, and to the end when the car pass the finish line. there's no difference with "session_update" scope. From what I understand, the "session_start" should only send packets when the session begins?, and "session_end" only send packets when session ends?

It is really confusing.. and from "session_update", I cannot tell difference from the packet's data on when the track session paused or ended. since the UDP data behaves the same (data stopped recieved when paused and session end).

Thanks.

2 Replies

  • strawhat_6666's avatar
    strawhat_6666
    2 years ago

    And one more thing... The data "stage_current_distance" seems to behave inconsistently with previous titles "DR1, DR2".

    In DR1/2, such value will decrease if you're driving the car to the opposite direction. But in EA Sports WRC, the "stage_current_distance" is recording the total distance the car runs, no matter the direction or even out of the track or wrong way. BTW, in the game Richard Burns Rally, the value behaves exactly like that in DR1/2...

    And... the issue mentioned in this thread was not fixed in patch 1.3, while it should be according to the patch 1.3 release note.

    Thanks.