Implement Baseball aiming, pooled projectiles and VR07 targets

This commit is contained in:
UnixNight committed 2026-11-02 22:54:19 -05:00
1 parent 50fcb87d90
commit d6ca417e9e
50 files changed
+3149 -32

No files matched your search

+145
View File
@@ -0,0 +1,145 @@
# Baseball original resources and VR07 fixture
2026-11-02. Original serialized resources and decoded pixels were read locally;
originals were not modified or executed. Binary activation/projectile/target
behavior belongs to the separate Baseball contract investigation. This report
records asset identity and a resource interface suitable for integration.
`tools/extractors/baseball_resources.py` exposes `export_baseball(original, output)`
and writes schema1 `baseball.json`. It preserves five exact canvases from
RetainedSprites.omt and the authored VR07 start/target/intro properties, including
every property source offset/raw bytes and duplicate target tags. It rejects
original subtree/ancestor outputs and existing descendant symlinks, checks both
archive and GAM identities before writing, and guards dimensions/pixel hashes.
```bash
python3 tools/extractors/baseball_resources.py ../Original --output artifacts/vehicle-assets/baseball
python3 -m unittest discover -s tests -p test_baseball_resources.py -v
```
Six regression checks pass: exact RGBA/PNG/provenance, original aim/glyph pixels,
six distinct target
records with authored property bytes, protected output paths, changed decoded
pixels and changed archive identity. Local output and test log are
`artifacts/vehicle-assets/baseball/` and `artifacts/vehicle-assets/baseball-tests.log`.
No shared prepare/runtime/build files were changed by this investigator.
## Port visual implementation and tested limits
`Application/BaseballVisuals.cs` appends20 hidden world alpha quads to a supplied
Mesh, preserving its collision metadata and existing draws/textures. `Update`
uses the caller's pool visibility/position, exact Canv2 and25×25 world dimensions.
It does not animate frames2..5 or invent a lifetime. Camera-facing centered
billboard orientation is a declared modern policy pending exact inherited sprite
render recovery. Degenerate straight-up/down cameras use a finite orthonormal
basis. Resource paths are bounded to the prepared Baseball directory, input
size/depth/dimensions and exact original pixel hashes are validated.
`Application/BaseballAimOverlay.cs` uses exact screens.omt Canv253 CrossHairs
15×210 pixels, SHA256
`2e16e11b151c8474ba68fd5017d1a3a6304a594a7f34c3b423f3417c7edfb453`.
The complete strip stays stationary at logical(315,100), without frame cropping.
Visibility follows AimVisible; text reads the separate prior-capture DisplayPitch,
not the newly captured SavedPitch. Source numeric position is
`y=trunc((45-DisplayPitch)*4.3+100)`, source text anchorx286, with positive-space
plus two zero-padded decimal digits from `% .2d`.
The subsequent [TIME font recovery](baseball-font.md) closes that binding:
set5 digits use alpha.omt118,127,120..126,119, all16×16. A null positive-space
glyph has zero advance; visible digits begin286 and302. Exact green pixels are
preserved with white vertex tint. Runtime/exporter/tests now use that source
mapping; the temporary SMAL policy is superseded.
The exporter writes these plus the source strip into `aimTextures`, each with
its source database key, byte range and decoded hash. `aimArchiveSha256` guards
screens.omt and alpha.omt. Source table, formatting and advance Evidence is in
baseball-font.md.
UiViewport retains uniform scale and centered640×480 placement at widescreen
and portrait sizes. Screen/world quads use alpha blending with unmodified source
texture alpha. Six standalone checks pass in
`artifacts/vehicle-assets/baseball-visual-tests.log`:20-slot/pixel/source metadata,
billboard bounds/camera degeneracies, stationary aim/number/selected glyphs,
widescreen and portrait scaling, combined world/overlay isolation and rejection
of altered pixels/dimensions/path traversal. Invocation:
```bash
source scripts/env.sh
dotnet run --project tests/GamePort.BaseballVisualTests
```
These are compiled port-side deterministic mesh/pixel checks. They do not verify
a displayed Vulkan frame, original source execution or native Windows behavior.
## Projectile and retained target artwork
Archive `omt/RetainedSprites.omt` SHA256
`b584ffa4a38f4bc809b3ea8f4321e0c08f2719e22df41a3fb4cd143ed89b3bef`.
This archive contains Canv resources, not 3D shapes.
| Canv / name | Offset / bytes | Dimensions | Decoded RGBA SHA256 |
| --- | --- | --- | --- |
|2 ball0000|72372 /3786|32×32|`68904b758e69139de0b01329b2a9844ecd2a466f31598c24324affaccfa2cab9`|
|3 ball0001|68582 /3790|32×32|`005def070e18111fbdb067e75285dad8ec677c1608020f55c3db7a4b9745205c`|
|4 ball0002|64788 /3794|32×32|`c368a59d5d7a57824c1c6b56b617cf058f5d5d53e18e5e48989710413490c536`|
|5 ball0003|58830 /3794|32×32|`e5da21c359d3215759e5c3c238107f526f7109203c0ff9fa391a3c8bc40c17ed`|
|8 target|48796 /10034|64×64|`8d31014cb9b9661ebed902c864bf740f562460e74da3f6b86ed3d2be4d10f0ec`|
Manifest `textures` records id/name/width/height/path/png/sourceOffset/sourceBytes/
sourceSha256/rgbaSha256. `ballCanvasIds` lists source IDs2..5 in source-number
order, without assigning animation cadence. `retainedTargetCanvasId:8` names
the literal retained artwork only; it is not the six VR07 target actors' artwork.
Pixels are neither recolored nor resized. The source target8 image visibly has
a four-corner frame/cross pattern; inspected original pixels are available as
`artifacts/vehicle-assets/retained_8.png`.
The contract investigator corrected an early interpretation of constructor40FC50:
its complete57C=25 is the inherited sprite dimension, complete580=2 the initial
canvas ID, and complete5F8..604 retain IDs2..5. It is not shape25. Exact REA
Evidence, frame selection, billboarding, size and render-state policy belong in
that investigator's source report; this exporter embeds no unverified cadence.
## Actual VR07 target visuals
All six authored `3TAR` records explicitly serialize `SpriteDatabase=sprites.omt`,
`SpriteIndex=135`, `SpriteSize=150`. The source resource is Canv135 **star**,
128×128 at offset2750568/35394 bytes. It is a pale purple jagged starburst with
8,016 alpha255 and8,368 alpha0 pixels. Exact RGBA SHA256:
`42bbea6c33fc2889cad0cd659af2274f936be10643254af233779c44f1e41e07`.
Archive SHA256:
`c8e016ea73e6104b9b672139b1d0b0ac83afc4feff6cc744a7fa4f6ba919e2a2`.
Inspected pixels: `artifacts/vehicle-assets/sprites_135.png`.
The existing `prepare_entities` exporter already follows this explicit sprite
database/index and can supply the exact texture; no duplicate sprite export is
necessary. Primary independently traced actual factory45CA06 to430220, inheriting
the sprite base441980; it is distinct from the Jimmy-owned retained target actor
and from the other class constructor4453B0 sharing a FourCC. That factory/default
recovery is separate from the serialized values verified here. The integration
must establish that the source loader respects the serialized overrides before
claiming runtime target appearance parity.
## Authored tutorial instances
VR07.gam SHA256
`1260b75d82ec794f9375ada30e186424746bc1dd4e4b0540c9b69bb7ad12d0b1`.
Six target offsets are0x885,0xAD6,0xD27,0xF78,0x11C9,0x141C. Every target uses
the same tag `C3DMOVINGTARGET`; identify instances by source offset/ordinal.
All serialize Speed100, HitsRequired3, NumPoints10, RespawnTime15 and
ActivateObject=`none`. These are data values, not reconstructed hit/motion rules.
| Offsets | Authored start | Authored destination |
| --- | --- | --- |
|885,AD6,D27|(-755,188,277)|(815,188,277)|
|F78,11C9,141C|(815,333,1520)|(-755,333,1520)|
Do not silently replace each instance's serialized Position with StartPos; both
are retained in the manifest. Constructor/postload/frame behavior determines how
these fields interact. PHONEBOOTH is STRT0x48C, authored position
(7.5705023,216.7101440,-1525.1119385), yaw0, StartTrigger=`bb1`.
Intro3MCA0x1892 serializes PlayerControlled=`NULL`, DeactivateInv1,
NextTrigger=`default` and source voicepractice IDs36,19,35,33,34.
This fixture has authored visuals sufficient for projectile and six target
rendering using the current sprite infrastructure. Source targeting, motion,
contacts, inventory/intro state, score, respawn and original/native Windows
execution comparison remain independent implementation/verification gates.