Feature: "C" telemetry format discovered
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 181
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
I’ve discovered a new 368 byte telemetry packet that can now be accessed by sending the "C" heartbeat.
The XOR constant is the same as Packet B (0xDEADBEEF).
• [0:4] SurfaceType (char): Indicates the surface in contact with each tyre.
• T = tarmac
• D = dirt
• [4:8] Current Lap (uint32): Current lap time (milliseconds).
• [20:24] Car Category (null-terminated string I think): Examples include GR3, GRB, GRX, etc.
The bytes in between are highly sporadic, I'm still looking into what exactly they are.
I’ll continue to reverse-engineer the packet and update this issue as more fields are identified.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by locating the existing Packet B decoder and the entry point handling the "C" heartbeat. Compare the 368-byte response against Packet B, verifying the XOR constant and the documented offsets for SurfaceType, Current Lap, and Car Category. Done means the identified fields are represented and the remaining sporadic bytes are clearly left unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100