Red Planet 4.12 · plans drawn from RPL4.RES
There are no track maps in the game's files. Nine of these are the - next best thing: the setup console's own pictures, score zones and - drop zone labelled, recovered and shown here as they were drawn. The other nine - never had one — so their plan comes from the track itself. Almost every track - is a single piece repeated, a wall thrown across the route with a gate in the - middle, and every gate is a point the race passes through.
+There are no track maps in the game's files, but the game draws + one every race: the map screen renders the track from above. These plans + are that same drawing, reconstructed outside the game — the same + models, the same placements, the same palette, straight down. Nine tracks also + have the picture the setup console showed, and those are here too.
pain
ARCADE 4.10DEATH RACE
137 of 255 placements are drawn; the rest carry no map art or stand alone off the course
+138 of 255 placements are drawn; the rest are models with no map art, which the map screen skips too
blade
ARCADE 4.10DEATH RACEFOOTBALL
159 of 216 placements are drawn; the rest carry no map art or stand alone off the course
+141 of 216 placements are drawn; the rest are models with no map art, which the map screen skips too
yip
ARCADE 4.10DEATH RACEFOOTBALL
82 of 127 placements are drawn; the rest carry no map art or stand alone off the course
+77 of 127 placements are drawn; the rest are models with no map art, which the map screen skips too
otto
ARCADE 4.10DEATH RACEFOOTBALL
163 of 203 placements are drawn; the rest carry no map art or stand alone off the course
+132 of 203 placements are drawn; the rest are models with no map art, which the map screen skips too
frstrm
ARCADE 4.10DEATH RACEFOOTBALL
119 of 325 placements are drawn; the rest carry no map art or stand alone off the course
+117 of 325 placements are drawn; the rest are models with no map art, which the map screen skips too
wise
ARCADE 4.10DEATH RACEFOOTBALL
Same footprint and instance count as -- Wiserguy's --
81 of 133 placements are drawn; the rest carry no map art or stand alone off the course
+Same footprint and instance count as -- Wiserguy's --
78 of 133 placements are drawn; the rest are models with no map art, which the map screen skips too
burnt
ARCADE 4.10DEATH RACEFOOTBALL
118 of 251 placements are drawn; the rest carry no map art or stand alone off the course
+97 of 251 placements are drawn; the rest are models with no map art, which the map screen skips too
brewers
ARCADE 4.10DEATH RACEFOOTBALL
220 of 607 placements are drawn; the rest carry no map art or stand alone off the course
+201 of 607 placements are drawn; the rest are models with no map art, which the map screen skips too
lyzlane
ARCADE 4.10DEATH RACEFOOTBALL
84 of 105 placements are drawn; the rest carry no map art or stand alone off the course
+82 of 105 placements are drawn; the rest are models with no map art, which the map screen skips too
headoff
ADDED 4.11DEATH RACE
113 of 264 placements are drawn; the rest carry no map art or stand alone off the course
+87 of 264 placements are drawn; the rest are models with no map art, which the map screen skips too
headmf
ADDED 4.11FOOTBALL
107 of 274 placements are drawn; the rest carry no map art or stand alone off the course
+83 of 274 placements are drawn; the rest are models with no map art, which the map screen skips too
tourdemars
COMMUNITYDEATH RACE
391 of 607 placements are drawn; the rest carry no map art or stand alone off the course
+351 of 607 placements are drawn; the rest are models with no map art, which the map screen skips too
trough
COMMUNITYDEATH RACE
417 of 633 placements are drawn; the rest carry no map art or stand alone off the course
-wiserguys
-COMMUNITYDEATH RACE
-Same footprint and instance count as Wiseguy's Wake
86 of 133 placements are drawn; the rest carry no map art or stand alone off the course
+320 of 633 placements are drawn; the rest are models with no map art, which the map screen skips too
rpweekend2014
COMMUNITYDEATH RACE
164 of 695 placements are drawn; the rest carry no map art or stand alone off the course
+134 of 695 placements are drawn; the rest are models with no map art, which the map screen skips too
+
wiserguys
+COMMUNITYDEATH RACE
+Same footprint and instance count as Wiseguy's Wake
82 of 133 placements are drawn; the rest are models with no map art, which the map screen skips too
donut
COMMUNITYDEATH RACE
96 of 325 placements are drawn; the rest carry no map art or stand alone off the course
+98 of 325 placements are drawn; the rest are models with no map art, which the map screen skips too
demoderb
COMMUNITYDEATH RACE
4 of 455 placements are drawn; the rest carry no map art or stand alone off the course
+4 of 455 placements are drawn; the rest are models with no map art, which the map screen skips too
arena
COMMUNITYDEATH RACE
128 of 695 placements are drawn; the rest carry no map art or stand alone off the course
+130 of 695 placements are drawn; the rest are models with no map art, which the map screen skips too
No track matches that.
18 tracks: 9 shipped in the 4.10 arcade cabinets, 2 added
- in 4.11, 7 built by the community afterwards. Drawing what the pod's map screen
- draws turns out not to give a map. That screen follows
- NavDisplay::DrawStatic, laying down each placement's
- GaugeImage, and nearly every placement in every track is the same
- piece: cn3, whose image is two 25×5 bars at x 19.5–44.5
- and -44.5–-19.5. That is not a wall running along the route, it is a wall thrown
- across it with a 39 unit gate in the middle, and the piece's collision solid says the
- same. A few hundred of those is a row of ticks, not a course.
But the gate is the point: cn3's own origin sits in the
- opening, so every placement marks somewhere the race passes through. Walk the gates in
- the order the course visits them — nearest to nearest, starting from the end
- furthest out, beginning a new line rather than reaching when the next gate is too far
- — and the track draws itself. Walls stacked for height repeat the same opening
- and count once. Placements standing alone more than 200 units from any other are
- dropped: fourteen tracks park a single piece at (1200, 0, 0) well off the
- course, and one stray placement stretches the frame to twelve times the width of the
- track. A real branch keeps its neighbours and stays — Paingod's second canyon is
- sixty pieces out at x = -400.
One track is drawn the other way. Chaining nearest neighbours across a - regular grid invents a maze-like path out of nothing but the order the points happened - to be visited in, and a plan has no business inventing a track layout. So each track is - tested first: count how many neighbours a gate has within 1.6× the typical - spacing. A corridor gives each gate the one ahead and the one behind; a floor of - obstacles gives it four or more. Seventeen tracks score 1 or 2 and are drawn as a - course. The large arena scores 8 on an exact 100 unit grid, so it keeps its wall blocks - instead — and the small arena, which scores 2, really is the maze it looks like.
-The console's nine pictures also check the other nine. Brewer's Bane is - the one track with a shape distinctive enough to be wrong in an obvious way, and the - reconstruction matches the picture turn for turn — long leg up one side to Score - Zone 1, the corner, the run out to Score Zone 2, junction chambers spaced along it. It - matched mirrored, which is how the projection came to be corrected: seen from above - with +Z up the page the engine's +X runs to the left, and every plan here had - been drawn the other way round. The tracks with no picture are now drawn the same way - round as the tracks with one.
+ in 4.11, 7 built by the community afterwards. Each plan follows +NavDisplay::DrawStatic: for every placement in the track's instance
+ stream, look up that model's GaugeImage and lay it down rotated and
+ positioned, at the LOD the engine would choose for this scale. Colours are palette
+ indices resolved through secpal.pcc, the palette the pod's secondary
+ port is configured with, on the display's own black — so the walls really are
+ grey, the score zones really are amber, and nothing here is a styling choice.
+ A record is an Entity::MakeMessage
+ (MUNGA/ENTITY3.h), read by InterestManager::LoadMapStream,
+ and it carries its own length — most placements are 76 bytes but every track
+ has eight of 140, two of 80 and one of 336. It names the model's Model List,
+ whose GaugeImage is filed under the same model name, so the name is the
+ join. Models with no gauge image — oao, snAwork,
+ pz1 — are skipped here exactly as the map screen skips them, which
+ is why a card can draw fewer placements than the track contains.
Seen from above the engine's +X runs right and +Z up:
+ L4GaugeImagePrimitive::Draw plots (x, z) and the graphics
+ view's origin is bottom left. The console's own pictures are mirrored
+ against that — they are illustrations, not screenshots — so where a card
+ shows both, the two are handed differently and each is right for what it is.
There is still no driving surface anywhere in the file: the track is - walls and gates, never tarmac. Extent and relief are the span of the placed geometry in - world units, so a long thin plan is a point-to-point canyon run — most of the - arcade tracks are exactly that, a few hundred units wide and several thousand long - — and a squat one is a circuit or an arena. Tracks marked NOT IN THE MENU exist - in the resource file but the setup screen does not offer them.
+ walls, zones and markers, never tarmac. Extent is the span of the placements in world + units, so a long thin plan is a point-to-point canyon run and a squat one a circuit + or an arena. Tracks marked NOT IN THE MENU exist in the resource file but the setup + screen does not offer them.