Files
Neutron/docs/analysis/gameplay.md
T

5.0 KiB

Gameplay evidence

Verified data reconstruction

tools/levels/gam.py parses all 35 supplied GAM files and accounts for every byte; re-encoding each parsed file reproduces its original bytes. Corpus: 3,299 entities, 93 class FourCCs, 84,044 properties (22,505 string, 26,965 float, 31,275 integer, 3,295 opaque type 2, four opaque type 4). Entity type names are inferred from matching object tags/properties, not universally proven class implementations.

All integer metadata and float32 values in GAM are big endian despite the little endian x86 executable. World positions are large unscaled coordinates; the Y coordinate is consistent with height, pending binary confirmation.

Initial scene

Original/NewGame.tsk begins with LV1B and float32 20.0. This supports LV1B as the new-game scene; it does not prove all save fields. gam/level1b.gam has 129 objects. Its player record at file offset 0x8:

Property Value
kind 3JIM
ObjectTag JIM1
PositionX 5071.93310546875
PositionY 26.661895751953125
PositionZ 824.1039428710938
RotationY 155 degrees
StartPoint STARTEXP

The matching STRT record starts at 0x5b0e. It agrees on player position/yaw; camera position is (4873.83642578125, 235.64761352539062, 373.21588134765625), camera rotations are zero, music is musicsecretlab.omt index 0, and StartTrigger is LABEXP. Camera look-at behavior and the introductory trigger require code analysis; do not treat zero stored rotation as proof of a zero effective rotation.

Small validation scene

gam/VR01.gam: 16 entities, one trophy, four pickups, two phone booths and two LOAD return triggers. Player at 0x8: (-2678.0380859375, 87.33218383789062, -2783.401123046875), yaw 290 degrees. STRT at 0x45c stores camera (-2709.25634765625, 287.3321838378906, -2390.133056640625), music musicvr01.omt index 0 and start trigger bu. Pickups use radius 100.0 and PointValue 5.

Controls documented by original readme

Source: Original/readme.txt, section V.

Input Original action
Up / Down Forward / backup (rearview in scooter mode)
Left / Right Turn left / right
Enter / Ctrl / left mouse Primary fire
Shift / Insert / right mouse Jump or jet-pack burst
M / O / H / I Menu / objectives / help / item inventory
G Call Goddard
Tab / Space Gadget screen
Escape Quit / main menu / skip cutscene
Mouse movement Forward, backward, turn

Data is not an algorithm

LOAD exposes LevelName, StartPoint, RequiredTask, RequiredLevel, ExactLevel, Radius, SoundIndex, FadeType and FadeTime. PIC exposes prerequisite fields, PointValue and pickup index. These are faithfully recoverable inputs; exact trigger conditions, distance metric, timing, task comparison and state updates must be established from executable code or observation before implementation is called faithful. Negative integers commonly act as flags/sentinels; their exact meaning depends on each property.

Save data has a fixed-looking region followed by Pascal task names and big endian values (NewGame.tsk tail includes SCENE = 30). Save writing is not yet recovered.

Recovered arithmetic fragments

Binary analysis has now resolved actual game gravity, jump impulse and basic integration order. src/GamePort/Game/RecoveredMotion.cs implements those narrow fragments independently of the still-unrecovered full controller/collision system.

  • CJimmyGame setup 0x44D414 overrides generic engine gravity to (0,-800,0).
  • Jump branch 0x4383B3 queues a one-frame (0,550,0) impulse.
  • Player airborne logic additionally changes acceleration: state<3 at 0x438148 uses gravity*1.33-gravity, producing roughly -1064 effective vertical acceleration. Other states/jetpack gates remain unresolved. Therefore the tested -800 free-motion fragment is not a complete normal-jump controller.
  • Physics 0x479EBB..0x479FC0 consumes/clears impulse, adds accelerationdt and gravitydt, then computes displacement from the updated velocity (semi-implicit Euler). Subsequent collision resolution and activation flags remain unresolved.
  • Player speed increment 30, idle decay 35 and maximum 600 are per invocation, without dt. Constructor fields and branch addresses are in binary.md. Rendering frame rate must not silently become the simulation invocation rate.
  • The original uint32 RNG at 0x438D52 wraps state*1664525+32767 and returns state>>16. A System.Random replacement would produce different sequences.
  • The -350 value originally suspected during investigation is a camera offset, not gravity. Follow offset (0,200,-350), look target offset (0,80,0).

C# regressions exercise impulse consumption/order, limits, initial original data, and RNG overflow. These establish the reconstructed arithmetic, without claiming bit-identical x87 behavior or a complete faithful controller.

Physics gating, collisions, AI, combat, progression, cutscene execution and simulation cadence remain under investigation. No original gameplay session has been captured yet.