[BUG] Cargo Not Compatible when Blender is configured with OpenColorIO
in progress
M
Michael Quigley
Cargo is currently not compatible when the user has configured to run Blender with OpenColorIO.
The problem isn't my extensions... Cargo doesn't seem to work properly
when Blender is configured to use ACES via OCIO. A screenshot showing
the Python error is attached. Disabling OCIO/ACES makes Cargo work.
Maxx Burman
in progress
Maxx Burman
Merged in a post:
Cargo Python "101" error of not finding the software
L
Larry Weaver
Cargo DID find Blender, showing the path and version of the software matched and it was installed correctly. It found Blender --
the first time
-- the import button was clicked and produced a Python error, as shown in the screenshot I sent. As I stated, the second time the button was clicked, it presented your "101" error of not finding the software.Upon further research, and also looking into the Python error in Blender after clicking the Import button in Cargo, we were able to determine that the issue was colour management. We have been using AGX and changing the colour managment folder back to stock vanilla Blender filmic solved the import issue.
Mitchell tharp
im getting this issue today after downloading the newest blender and cargo
Maxx Burman
Hi Larry, we've made some updates to the software setup process in v1.0.4. This should resolve the issues you ran into. Can you let us know if you're still hitting a 101 error?
Maxx Burman
planned