Recover Rocketship flight components against original-code probes

This commit is contained in:
UnixNight committed 2026-11-03 11:09:16 -05:00
1 parent c6eb1861cd
commit a274670fe8
23 files changed
+2462 -2

No files matched your search

+97
View File
@@ -0,0 +1,97 @@
# Rocketship resources and VR02 authored data
2026-11-03. Read-only original asset inspection plus exact resource export.
No original binary executed; no original/friend-tree changes. Binary ownership,
physics, transforms, animation timing and material flags belong to
[Rocketship recovery](rocketship.md), not to geometric compatibility.
`tools/extractors/rocketship_resources.py` exposes
`export_rocketship(original, output)`. It validates all12 source hashes, ASE
sample/topology and decoded RGBA identities before writing a separate directory.
It rejects original subtrees/ancestors and existing descendant symlinks. Four
source-named animation manifests reference exact original PNG pixels; no family
action names, transforms, invented UVs, interpolation or material flags are set.
Generated data: `artifacts/rocket-assets/resources/rocketship.json`.
```bash
python3 tools/extractors/rocketship_resources.py ../Original --output artifacts/rocket-assets/resources
python3 -m unittest discover -s tests -p test_rocketship_resources.py -v
```
## Meshes and textures
Coordinates use the existing independently matched ASE conversion `(x,z,y)`,
texture `(u,-v)`; exporter preserves sample positions. Original smoothing remains
unrecovered; existing ASE exporter reconstructs flat normals.
| Source | Indexed vertices / faces | Exact source sample times | fps / ticks per frame | Texture topology |
|---|---|---|---|---|
|strato.ASE / strato01|159 /262|0|30 /160|Own497 UVs,262 texture faces|
|firestrato.ASE / Cylinder01|7 /6|0,480,960|10 /480|Own10 UVs,6 texture faces|
|jimdrive.ASE / 01jimmy|426 /814|0,480|10 /480|No UVs; original jimstop426 base|
|godrocket.ASE / point|222 /411|0,960,1920|5 /960|No UVs; original godpoint222 base|
The two morphs retain the base's faces/UVs by vertex index, matching existing
original-morph exporter semantics. This establishes renderable resource
compatibility; runtime DRIVE/ROCK selection/attachment still needs binary proof.
The three godrocket samples share bounds but contain different indexed positions;
retain all samples rather than treating identical bounds as a static clip.
| Exact PNG | Size | Decoded RGBA SHA256 |
|---|---|---|
|strato.png|256×256|`b1b18454fe0413e3ce885a61e4407c808060da0fe29ef2aec26ccd4e39437f31`|
|fire.png|100×100|`07dbbc4c6b99b6fa5fe424f2f917e03352a9c635fdc1593fc12f354be83a9a7f`|
|jimycarl.png|256×256|`5e54ccb99e9e060843cd7f80fd93ff8bf47f8779666e41d4240398354a278a3f`|
|goddard02.png|256×256|`9eb24c8fa41ddf08d2f33dd7b7513b632d4262cfc26cab3383c54258b9647a62`|
Retained REA body-init43DD10 Evidence
`ev_d7bf671456c93939ac04ab612e10181e729e078de4bfc06b22f4b5302d71da00`
(`artifacts/rocket-contract/rea-core/00.json`) verifies HIDEFAULT→Strato.ase,
strato.png, DEFAULT and game110(50.0). EXE VAs in this range map to file offset
VA−400000. The source setter110→471240 establishes50 as body radius; it is not
a visual scale. Constructor4192E0 also binds DEFAULT→firestrato.ASE/fire.png;
see the accompanying Rocketship source report for guards/Evidence. Driver/dog
resource candidates are exported without
asserting their runtime state/visibility/material bindings. Do not substitute
rocket.ASE, rocketfire.ASE or objects.omt shape26 merely because their names
sound appropriate; their topology differs from this recovered Strato binding.
## VR02 and campaign corpus
All35 supplied GAMs were parsed.32 contain one3ROC; Level3B/3E and VR08 do not.
Two independent3FLA records occur in Level2 (offset7267) and Level2b (4C20),
not VR02; this does not count constructor-owned fire children. Complete observed
placement values are retained in `artifacts/rocket-assets/placements.json`.
VR02.gam SHA256
`3be92e270bd14e6fc41db702e68c894562128d23d46704b89f7abb1914bebc5c`.
All18 entity records/ordinals/property bytes/offsets are retained in the manifest.
Its sole3ROC is ordinal1, file offset1CD; position
`(445.8588257,74.9721756,598.4440918)`, yaw9.9755859375, TaskNameLIBBY.
Authored fields: MaxHeight3900, MaxSpeed1400, AccelRate400, DecelRate1, Up650,
Down−650, MaxVertVelocity650, NewGravity0, AccelLean20, DecelLean−20. These
values do not define the flying algorithm or active Jimmy-owned rocket spawn.
PHONEBOOTH/STRT points at intro3MCA `rs`; the source intro target list is
rs1/rs2/rs3/Jim1. There are **two rs1 patrol entities**, ordinals13/15,
offsets23DE/2C09. Preserve distinct records and original lookup behavior; do not
deduplicate tags or assume which position the original resolver chooses. Seven
3PIC records use indices3101..3107; LOAD offset21B9 targets RETURN with radius400.
VR02.omt SHA256
`ab041f663cd5e68d58e590feeb7661f308a70ccc682a32c49ccd82b74bec61c0`.
One shape0 `Box01`, offset74464,93802 bytes,424 indexed vertices/880 triangle
polygons; no NC-named shape. Material counts:0→160,2→96,3→192,5→400,null→32.
Retain the32 textureless polygons in collision data; absence of special Jimmy
materials alone does not prove game-class registration or flying-body admission.
The current route camera/static-body factory also excludes VR02 pending those
source gates. Resource export does not change that factory.
## Verification and remaining boundaries
Five resource checks pass: exact pixels/source sampling and mesh indices,
base-topology UV/sample-position binding, VR02 offsets/duplicate tags/null
polygons, protected output paths and changed-source/pixel rejection before output.
Standalone CLI export succeeds. No port gameplay, Vulkan, native Windows or
full original-runtime comparison is claimed by these checks. Main owns shared
prepare/package wiring; resources are currently opt-in via the new exporter.