Drospy

I hope that this year we have access to full game, it's important for review many issue. Thank you.

Yes, in this moment I change ERS in qualifying with wheel. Thank you BR

Hi @BarryBL yes, only in Qualifying session, no issue in other session. Thank you for your support. BR

Hi @BarryBL, do you have any news for me?

Yes, "0" and "1" for ESR Mode, "2" and "3" for Mix, "4" and "5" for BB, "6" and "7" for differential. In F12019 it works fine. Thank you Walter

A detailed description of the issue. Please include any error codes here. When changing the ERS mode using Keyboard, doesn't work If changing using the mfd, there is no issue. Platform XB1 What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) 1.12 Game-mode? ALL quali session We need to be able to make your problem happen internally so we can fix the issue. Can you make the problem happen again? It happens the first time

Hi All, just a info about ERS Mode, in documentation we have: uint8 m_ersDeployMode; // ERS deployment mode, 0 = none, 1 = medium // 2 = overtake, 3 = hotlap In game on HUD, we have: 0 = none 1 = medium 2 = hotlap 3 = overtake So, i think that UDP data must be the same to game.

Are you on Xbox? F12020 V1.01 Thank you for your support

Hi @Hoo All data in Car Status packet are wrong, in final beta version all data worked correctly Are m_drsActivationDistance and m_drsFault included in main game ? Xbox F12020 v1.01 Thank you

Hi All, is there a issue on Car Status packet ? In beta it worked fine. Thanks

I am receiving wrong data for ERS Mode: in game Overtake is 3, in UDP Data is 2 in game Hotlap is 2, in UDP Data is 3 Thank you.

@Hoo In Doc, comment for ERS Mode is still wrong, Hotlap and Overtak are still reverse. Thank you

Thank you, today i will check it

Yes, 0-22, 23 bytes, but with F12020 format, other data don't start from position 23. For example : LAP Data 0-22 Packet Header 23 ? 24-27 m_lastLapTime

Hi all, I have a issue with telemetry data, with F12020 format, "Packet Header" is 23 bytes, but in the guide, "Packet Header" is 22 bytes, same of F12019 format. I have checked 100 time UDP telemetry guide.