State:New|TargetRelease:No Target|icon_bug|database:public|icon_mari|Resolution:Fixed|BugID:534874|
Problem summary
Sending projections from Nuke to Mari doesn't work and results in a PySide2 error in the Mari Python console.
Customer reported version
Mari 7.0v2
Customer reported platform
Rocky 9
Steps to reproduce:
1. Install Nuke<>Mari bridge and setup connection, instructions available in the pages below:
https://learn.foundry.com/mari/Content/nuke_mari_bridge/Bridge/installation.html
https://learn.foundry.com/mari/Content/nuke_mari_bridge/Bridge/connection_setup.html
In Nuke:
2. Create a Colorbars node and a Camera node (this issue occurs whether or not the new 3D system/classic Nuke Camera node is used)
3. Connect them both to a Project3D node:
4. Select all 3 nodes
5. Click Mari > Send > Projection Components (issue also occurs with Sequence Projections)
Expected behavior:
Projection components should be sent to Mari.
Alternatively, adding
Actual behavior
Nothing is sent, and an error is returned in Mari's Python console:
Traceback (most recent call last): File "", line 1, in File "/usr/local/Mari6.0v2.000012a/Media/Scripts/Mari/system/nuke_bridge.py", line 152, in createProjectors projection_ui = ProjectionSettingsUI(self.projector_data, self.geo_list) File "/usr/local/Mari6.0v2.000012a/Media/Scripts/Mari/system/nuke_bridge.py", line 416, in __init__ buttons = widgets.QDialogButtonBox(widgets.QDialogButtonBox.Ok | widgets.QDialogButtonBox.Cancel, PySide2.QtCore.Qt.Horizontal, None) NameError: name 'PySide2' is not defined
Workaround
The second time something is sent, it works.
Alternatively, adding the line import pyside2 to the nuke_bridge.py file referenced in the above error seems to prevent this error from ever occurring.
Reproduced by Support in:
Mari 7.0v2/Nuke 15.1v5- Windows 10, Rocky 9
Mari 6.0v2/Nuke 14.0v3 - Windows 10, CentOS 7 - regression
Unable to reproduce bug in:
Mari 6.0v1 - Windows 10, CentOS 7
Earliest version tested
Mari 6.0v1 - This issue doesn't appear in this version and has regressed
We're sorry to hear that
Please tell us why