What I would like to be able to do is to get more information from the IS_AXO packet where we can see:
- Object type enum (red cone, blue cone, tyre, etc)
- Unique object ID
This would enable a system where you can give more/less custom penalties based on what object the driver hits.
Also do the IS_AXO packets get sent for any custom layout object when not in the Autocross track (ie. KY, SO or BL)?
In my case, what I would like to do is to create a custom layout on say BL2 where certain cones would reduce lap times, and tyres raise them. This way we could place a blue cone (-4 secs) in btween 2 lines of tyres (+1 sec) just wide enough for an UF1 to get through, but not an RB4. This would give an advantage to the UF1 to make up time.
Conversely, the RB4 could use a ramp to reach a red cone (+2 secs) on top of a stack of tyres. Not fast enough and he knocks the tyres down.
- Object type enum (red cone, blue cone, tyre, etc)
- Unique object ID
This would enable a system where you can give more/less custom penalties based on what object the driver hits.
Also do the IS_AXO packets get sent for any custom layout object when not in the Autocross track (ie. KY, SO or BL)?
In my case, what I would like to do is to create a custom layout on say BL2 where certain cones would reduce lap times, and tyres raise them. This way we could place a blue cone (-4 secs) in btween 2 lines of tyres (+1 sec) just wide enough for an UF1 to get through, but not an RB4. This would give an advantage to the UF1 to make up time.
Conversely, the RB4 could use a ramp to reach a red cone (+2 secs) on top of a stack of tyres. Not fast enough and he knocks the tyres down.