Paingod's Passage
pain
@@ -225,7 +236,7 @@ h1 em { font-style: normal; color: var(--sys); }diff --git a/docs/tracks.html b/docs/tracks.html index cd0bd96..761baaa 100644 --- a/docs/tracks.html +++ b/docs/tracks.html @@ -108,9 +108,20 @@ h1 em { font-style: normal; color: var(--sys); } .trk { background: var(--panel); padding: 1.1rem 1.25rem 1.25rem; } .trk[hidden] { display: none; } -.plan { margin: 0 0 1rem; display: flex; justify-content: center; } +.plan { + margin: 0 0 1rem; display: flex; flex-direction: column; + align-items: center; gap: .5rem; +} +.plan__src { + font: 500 var(--step--1)/1 var(--mono); letter-spacing: .1em; + text-transform: uppercase; color: var(--ink-low); text-align: center; +} .plan__img { - display: block; width: 100%; max-width: 15rem; aspect-ratio: var(--ar); + /* The mask is drawn with contain, so clamping the box letterboxes the + art rather than stretching it - a portrait console map stays legible + beside a squat arena. */ + display: block; width: 100%; max-width: 15rem; max-height: 22rem; + aspect-ratio: var(--ar); background-color: var(--ink-mid); -webkit-mask-image: var(--art); mask-image: var(--art); -webkit-mask-size: contain; mask-size: contain; @@ -175,12 +186,12 @@ h1 em { font-style: normal; color: var(--sys); }
Red Planet 4.12 · plans drawn from RPL4.RES
There are no track maps in the game's files — the console had - pictures of them and those pictures did not survive. But the track itself knows - where it goes. Almost every one is built from a single piece repeated: a wall - thrown across the route with a gate in the middle. These plans are the - course those gates describe — every gate is a point the race passes - through, walked in the order the course visits them.
+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.
pain
@@ -225,7 +236,7 @@ h1 em { font-style: normal; color: var(--sys); }blade
@@ -241,7 +252,7 @@ h1 em { font-style: normal; color: var(--sys); }yip
@@ -257,7 +268,7 @@ h1 em { font-style: normal; color: var(--sys); }otto
@@ -273,7 +284,7 @@ h1 em { font-style: normal; color: var(--sys); }frstrm
@@ -289,7 +300,7 @@ h1 em { font-style: normal; color: var(--sys); }wise
@@ -305,7 +316,7 @@ h1 em { font-style: normal; color: var(--sys); }burnt
@@ -321,7 +332,7 @@ h1 em { font-style: normal; color: var(--sys); }brewers
@@ -337,7 +348,7 @@ h1 em { font-style: normal; color: var(--sys); }lyzlane
@@ -353,7 +364,7 @@ h1 em { font-style: normal; color: var(--sys); }headoff
@@ -369,7 +380,7 @@ h1 em { font-style: normal; color: var(--sys); }headmf
@@ -385,7 +396,7 @@ h1 em { font-style: normal; color: var(--sys); }tourdemars
@@ -401,7 +412,7 @@ h1 em { font-style: normal; color: var(--sys); }donut
@@ -417,7 +428,7 @@ h1 em { font-style: normal; color: var(--sys); }trough
@@ -433,7 +444,7 @@ h1 em { font-style: normal; color: var(--sys); }rpweekend2014
@@ -449,7 +460,7 @@ h1 em { font-style: normal; color: var(--sys); }wiserguys
@@ -465,7 +476,7 @@ h1 em { font-style: normal; color: var(--sys); }demoderb
@@ -481,7 +492,7 @@ h1 em { font-style: normal; color: var(--sys); }arena
@@ -525,6 +536,14 @@ h1 em { font-style: normal; color: var(--sys); } 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.
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
diff --git a/tools/pages/build_tracks.py b/tools/pages/build_tracks.py
index 6e0e3c2..2a6c194 100644
--- a/tools/pages/build_tracks.py
+++ b/tools/pages/build_tracks.py
@@ -7,7 +7,7 @@ stride, so the scenery placements ARE the map, seen from above.
Usage: build_tracks.py
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.
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