-
Notifications
You must be signed in to change notification settings - Fork 12
Avalon Integration
Here are some notes on how to get up and running with each host integration
Add {core}/setup/blender to BLENDER_USER_SCRIPTS environment variable.
Add {core}/setup/maya to PYTHONPATH environment variable.
Add {core}/res/houdini to HOUDINI_SCRIPT_PATH, this will make it run 123.py on startup.
Add {core}/res/houdini to HOUDINI_MENU_PATH, this will make it find the MainMenuCommon.xml
It is very important to end the environment variable with a & value in the list once, as that will have Houdini still load its default values too, e.g. {core}/res/houdini;& on Windows. See Special Characters in Path Variables.
Note that 123.py does not get triggered in Houdini Core instead you'd need to rename or copy the 123.py file to houdinicore.py. The 123.py file works fine with Houdini Indie, Houdini Apprentice, etc. as long as its the FX version of Houdini.
Add {core}/setup/nuke/nuke_path to NUKE_PATH environment variable.
Add {core}/setup/fusion so the Fusion Scripts can be picked up. TODO HOW TO?
Only a WIP integration is available
Add {core}/setup/cinema4d to g_additionalModulePath (for R19 and older use C4D_PLUGINS_DIR, see here
See: Cinema4D Integration for more details.
Only a WIP integration is available
Add {core}/setup/clarisse/startup.py to CLARISSE_STARTUP_SCRIPT environment variable to to auto-initialize the Menu and tools.
see Clarisse Integration for more details
Only a WIP integration is available
You will need to copy-paste the Krita plugin to your local install folder.
See Krita Integration for more details.
Pyblish QML runs in a separate process from the host integration and thus runs in its own Python interpreter with PyQt5. It can happen when triggering Pyblish QML by default it will find the Python or PyQt5 of the host DCC (e.g. Houdini) except for the one you intend it to. This could result in failing run Pyblish QML in the subprocess correctly.
It could result in errors like the following:
This application failed to start because it could not find or load the Qt platform plugin "windows".
To resolve these situations Pyblish QML allows you to set PYBLISH_QML_PYTHON_EXECUTABLE and PYBLISH_QML_PYQT5 environment variables to have Pyblish pick that up explicitly. It can work without setting these for some host, but notice how the Pyblish QML repository itself seems to recommend setting the environment variables in general.