Player plugin resources and native outputs

[freezy]

Lets plugins in the Player use PinMAME games. Requires the VPE plugin system (VisualPinball.Engine, feat/player-plugins).

• Game identity, and the original display and audio streams, are exposed as plugin resources.
• A PinMAME settings plugin controls ROM playback volume and shows up on the Player's global volume mixer.
• Native outputs (IGamelogicNativeOutputs): every lamp, GI string, solenoid and mech is reported by its PinMAME number, mapped or not, once per poll. Backglass-only lamps reach plugins such as B2S this way.
• Value semantics are fixed per hardware generation, following libpinmame:
  • Lamps are physical on Pinball 2000 and for SAM LEDs above 80.
  • Solenoids are physical where PinMAME forces PWM integration: SAM, Capcom, PinHeck and Pinball 2000.
  • GI uses levels 0..8 on WPC, and 0 or 9 elsewhere.
• Segment display layouts are reported per display (seg7, seg9, seg14, seg16), with an upright hint for Gottlieb System 80.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge, with no outstanding findings.

Summary

This PR exposes PinMAME game identity, display and audio resources, and numbered hardware outputs to Player plugins.

• Plugins receive PinMAME outputs with hardware-specific values and display layouts.
• PinMAME shares game identity and original media with Player plugins.
• Player settings let people change PinMAME ROM playback volume.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  ROM[PinMAME ROM] --> Engine[PinMAME engine]
  Engine --> Resources[Identity, displays and raw audio]
  Resources --> Plugins[Player plugins]
  Engine --> Outputs[Numbered hardware outputs]
  Outputs --> Plugins
  Settings[Player volume setting] --> Gain[Playback gain]
  Engine --> Gain
  Gain --> Unity[Unity audio]

Loading

_{Reviews (3) · Last reviewed commit: "engine: stop replaying every GI change o..." · Reviewed by Greptile}