[freezy]

Part of the logging and error reporting work. It follows the level policy from freezy/VisualPinball.Engine#590: errors are for VPE bugs, and problems the user or table author can fix are warnings. What the plugin knows goes into the session diagnostics that error reports carry.

• Unmapped coils and unknown switches are warnings, once per id; dropped frames and a full audio queue are throttled.

• A missing ROM is one clear warning naming the ROM and the folders searched; an unknown ROM name or a missing native library is a warning too, reported through IGamelogicStartupStatus.

• Native callbacks catch what they throw instead of letting it reach native code, and name their thread "PinMAME".

• The engine describes itself for error reports: ROM, libpinmame version, folders and whether the ROM is in them, run state, audio, displays, settings.

• Bumps PinMame to 1.1.1 (Forward libpinmame's log messages as a formatted event vpinball/pinmame-dotnet#47) and writes libpinmame's own messages to the log as PinMAME.Native, throttled: loading, wrong checksums, missing files. Its errors are warnings, since they're about the ROM or the setup.

Depends on freezy/VisualPinball.Engine#590 (the plugin API: IPluginLog, IDiagnosticsSource, IGamelogicStartupStatus), so merge that first.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge after its stated VPE API dependency.

Summary

The PR adds quieter logs, startup failure details, and session diagnostics for PinMAME.

• PinMAME startup reports include ROM and engine details.
• PinMAME callbacks stay contained and report their failures.
• Unmapped PinMAME outputs and switches get clear warnings.
• Repeated PinMAME messages no longer crowd out useful logs.
• The PinMAME wrapper package is updated to version 1.1.1.

_{Reviews (3) · Last reviewed commit: "pinmame: Take out csproj changes that we..." · Reviewed by Greptile}