Correlate infrastructure prelude patterns with mode families
This commit is contained in:
parent
38546f781e
commit
db789ec007
3 changed files with 158 additions and 17 deletions
|
|
@ -3080,9 +3080,19 @@ The low helper strip beneath that shared family is tighter now too: `0x0052ecd0`
|
|||
with fixed `TrackCapDT_Cap.3dp` / `TrackCapST_Cap.3dp`, mode `0x03` with
|
||||
`OverpassST_section.3dp`, mode `0x02` with decoded tunnel table stems plus zero-stem fallbacks,
|
||||
and mode `0x01` with decoded bridge table stems plus zero-stem fallbacks. So the remaining
|
||||
infrastructure problem is no longer “what does `0x00490960` build?” but “how do those grounded
|
||||
mode families collapse into the save-side compact-prefix/name-pair classes, especially the
|
||||
already-grounded bridge-only `0x0002/0xff` class and BallastCap `0x0055/0x00` class?”.
|
||||
infrastructure problem is no longer “what does `0x00490960` build?”. The current grounded
|
||||
`q.gms` name corpus now also maps directly onto most of those families:
|
||||
`BridgeSTWood_Section.3dp -> mode 0x01`, `TunnelSTBrick_* -> mode 0x02`,
|
||||
`BallastCapST_Cap.3dp -> mode 0x0a`, and `TrackCapST_Cap.3dp -> mode 0x0b`, with only
|
||||
`Overpass` still static-only in the current save corpus. The remaining problem is therefore how
|
||||
the surviving compact-prefix regimes subdivide those already-mapped families, especially inside
|
||||
bridge mode `0x01` and track-cap mode `0x0b`, rather than which family each name row belongs
|
||||
to.
|
||||
The new probe correlation now makes that residual even tighter: on grounded `q.gms`, the
|
||||
dominant mixed `0x0001/0xff` class splits as `bridge:62 / track_cap:21 / tunnel:19`, while the
|
||||
pure `0x0002/0xff` class is all bridge and the pure `0x0055/0x00` class is all ballast-cap. So
|
||||
the next infrastructure slice should focus on subdividing the mixed one-child `0x0001/0xff`
|
||||
class, not on revisiting the already-grounded pure classes.
|
||||
The smaller attach helper `0x00490a3c` is now bounded too: it conditionally allocates one
|
||||
`Infrastructure` child from a caller-supplied payload stem, attaches it to the current owner, and
|
||||
then seeds three caller-supplied position lanes through `0x00539530` and `0x0053a5b0`. The
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue