Repository navigation
DMD Player plugin integration and declarative settings - #2
Merged
Merged
Conversation
|
Without a configured library the plugin looks next to DmdDevice.ini, in VPM_HOME and next to the ROM folders, like the standalone bridge. Automatic selection prefers the newest Serum file in the game folder, then pin2dmd.pac with a key, then pin2dmd.pal, and skips macOS resource forks.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds DMD as an optional Player plugin in the existing Unity package. The integration declares global and game-specific settings, discovers available colorizations and display sources, and connects DMD runtime output through VPE's shared plugin contracts. The Player owns the configuration UI; no extra DMD Player package is required.
Field metadata supports wide inputs and paired display coordinates in the shared renderer. Package metadata and new source headers follow the VPE conventions.
Validation: exercised with the shared Player's plugin settings and runtime checks during the integration work. The plugin-contract tests and Windows Player standalone build passed; native macOS/Linux display hardware remains untested on this host.
Depends on the Core plugin contracts in freezy/VisualPinball.Engine#588 and the shared settings renderer in VisualPinball/VisualPinball.Engine.Player#1.