EQUB %00000011 \ Sign 0: 00000 011 Type 10 Chicane Section 0 EQUB %00010000 \ Sign 1: 00010 000 Type 7 Straight Section 2 EQUB %00011001 \ Sign 2: 00011 001 Type 8 Start flag Section 3 EQUB %00101100 \ Sign 3: 00101 100 Type 11 Right turn Section 5 EQUB %00111000 \ Sign 4: 00111 000 Type 7 Straight Section 7 EQUB %01001101 \ Sign 5: 01001 101 Type 12 Left turn Section 9 EQUB %01100100 \ Sign 6: 01100 100 Type 11 Right turn Section 12 EQUB %01110101 \ Sign 7: 01110 101 Type 12 Left turn Section 14 EQUB %01110000 \ Sign 8: 01110 000 Type 7 Straight Section 14 EQUB %01110000 \ Sign 9: 01110 000 Type 7 Straight Section 14 EQUB %10010100 \ Sign 10: 10010 100 Type 11 Right turn Section 18 EQUB %10011000 \ Sign 11: 10011 000 Type 7 Straight Section 19 EQUB %10100100 \ Sign 12: 10100 100 Type 11 Right turn Section 20 EQUB %10101000 \ Sign 13: 10101 000 Type 7 Straight Section 21 EQUB %10110101 \ Sign 14: 10110 101 Type 12 Left turn Section 22 EQUB %10111000 \ Sign 15: 10111 000 Type 7 Straight Section 23Name: trackSignData [Show more] Type: Variable Category: Track data Summary: Base coordinates and object types for 16 road signs Deep dive: The track data file format The Silverstone trackContext: See this variable in context in the source code References: No direct references to this variable in this source file
Object types and base coordinates for the 16 road signs. * Bits 0-2 = Object type of road sign (add 7 to get the type) * Bits 3-7 = The number of track section to use as the base coordinates for the sign (i.e. we add the scaled track sign vector to this section's start coordinates to get the sign's 3D coordinates) Note that this simply defines the sign's 3D coordinates. The mapping between track sections and the signs in those sections is defined in each section's trackSectionData byte. The last sign in this table is the one we see at the start of practice.