Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent TyreStintHistoryData compounds from Session History Packet #90

Open
gegehprast opened this issue Aug 18, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@gegehprast
Copy link

Describe the bug
The m_tyreActualCompound and m_tyreVisualCompound from TyreStintHistoryData from the Session History packet is sometimes incorrect. I'm not sure if this a bug from the typing of the client, or from the game.

To Reproduce
I was doing grand prix with medium session length. I always do soft (C4 / 18) -> medium (C3 / 19) stints. My issue is, using the m_tyreActualCompound from the Session History packet and TYRES constant from the client, I sometimes got the wrong compound, sometimes I got soft (C5 / 17) -> soft (C4 / 18) instead of soft (C4 / 18) -> medium (C3 / 19).
My telemetry settings are:
Broadcast: Off
IP: 127.0.0.1
Port: 20777
Rate: 20Hz
Format: 2022
Your Telemetry: Restricted
Show Player Names: Off

Expected behavior
I should get correct compound which is soft (C4 / 18) -> medium (C3 / 19).

Screenshots/Additional information
Here is a screenshot of the wrong stints history data from Session History packet:
image

@gegehprast gegehprast added the bug Something isn't working label Aug 18, 2022
@msansoni
Copy link
Contributor

Thanks for flagging this, it will need more investigation as the EA docs indicate that m_tyreActualCompound=17 would be a C4 and 18 would be a C3. The constants in tyres.ts match to the documentation from EA

17: {color: '#f92d29', name: 'C4'},
. It could be an indexing base issue, if the constants were 1 based rather than 0 based this would explain the issue.

@msansoni msansoni self-assigned this Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants