[freezy]

Anchor native ROM time fences to the active simulation start, preventing accelerated ROM execution after loading a table in the standalone player.

Validation: four PinMAME time-fence tests passed; coordinated Linux standalone build and T2 loading succeeded.

Part of the coordinated fix/urp-player-gpu-cache changes across the engine, player, URP/HDRP adapters, PinMAME, and URP player project.

Coordinated PRs:

• VisualPinball.Engine
• VisualPinball.Engine.Player
• VisualPinball.Unity.Urp
• VisualPinball.Unity.Hdrp
• VisualPinball.Engine.PinMAME
• VisualPinball.Engine.Player.Urp

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Anchors PinMAME time fences to the first active simulation tick instead of the application's elapsed time.

• Each ROM’s time fence starts with its simulation.

No actionable issues were found.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Start or retry] --> B[Reset clock and set fence to 0.01]
  B --> C[First active simulation tick records origin]
  C --> D[Later ticks use elapsed time plus 0.01]
  D --> E[Keep fence at least 0.01]
  F[Shutdown] --> G[Disable fence under the same lock]
  G --> H[Ignore later ticks]

Loading

_{Reviews (1) · Last reviewed commit: "Anchor PinMAME time fences to simulation..." · Reviewed by Greptile}