Previously, fixture names relied on Blender’s structural Name property, which requires all names to be unique. While this is useful in other contexts, it is not suitable for device naming. This has now been resolved by introducing a dedicated fixture-name property within BlenderDMX.
Full Changelog: https://github.com/open-stage/blender-dmx/compare/v2.1.2…v2.1.3
Full Changelog: https://github.com/open-stage/blender-dmx/compare/v2.1.1…v2.1.2
Full Changelog: https://github.com/open-stage/blender-dmx/compare/v2.1.0…v2.1.1
Both pymvr and pygdtf libraries have been much worked on in the past several weeks, resulting in the possibility to finally implement an initial Full Scene MVR Export to BlenderDMX (previously, only fixtures had been exported).
Full Changelog: https://github.com/open-stage/blender-dmx/compare/v2.0.18…v2.0.19
Full Changelog: https://github.com/open-stage/blender-dmx/compare/v2.0.17…v2.0.18
Only a few small missed touch ups were required for Blender 5 compatibility. Btw, Blender’s new Color Temperature for light objects is not utilized in BlenderDMX, we rather use our own Color Temperature calculation which is working for both Eevee and Cycles.
Full Changelog: https://github.com/open-stage/blender-dmx/compare/v2.0.15…v2.0.16
When recording DMX as key-frames, it is useful to start the recording in Blender based on cue timing in the DMX console. The new BlenderControl GDTF device and support in BlenderDMX allows to trigger the auto-keyframe and the animation/timeline play state from DMX. See details in the documentation.