Render original lab and Jimmy with native Vulkan and SDL3 on .NET 10

This commit is contained in:
UnixNight committed 2026-10-23 17:36:04 -04:00
1 parent 3df20ac19a
commit 008c0e16da
41 files changed
+2125 -68

No files matched your search

+30 -2
View File
@@ -70,5 +70,33 @@ 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.
Physics, jumping, collision, AI, RNG, combat, progression and cutscene execution
remain under investigation. No original gameplay session has been captured yet.
## 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 acceleration*dt and
gravity*dt, 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.