Beta#171
Merged
Merged
Conversation
…ort-to-Display Feature/adding ratio support to display
lib CRI implementation
ref and autorc added
update release file
First step - adding new WheelSlot params
Collaborator
|
@petrvanekrobe check please my last comment. Width, Height, IsCurved for display geometry and Duration, Width, Height, FPS for Wheel Slot are first in next branch of GDTF specification. Do we want to have those changes already in a master branch of a library and in a fixture builder? |
Contributor
|
Hi @AndriiVoitenko , we have discussed this today and yes, it is OK to have this in the library before the DIN spec is pushed, but we need to make sure to have it all in the next branch of GDTF/MVR: https://github.com/mvrdevelopment/spec/blob/next/ @ILane-VW @klinzey |
petrvanekrobe
approved these changes
Jul 6, 2026
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
4 participants
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.
Request for the new FB release.
step 1 -> merge beta branch into master branch (libMVRgdtf repo)
step 2 -> create libMVRgdtf release
step 3 -> merge beta branch into master branch (nodeVectorworksMvrGdtf repo)
step 4 -> create nodeVectorworksMvrGdtf release with new libMVRgdtf version
step 5 -> merge beta branch into master branch (GDTFFixtureBuilder repo)
step 6 -> create GDTFFixtureBuilder release with new nodeVectorworksMvrGdtf version
step 7 -> deploy