Maya 2023/2024 - Redshift Plugin
Quote from ParasolIsland on 8. February 2024, 9:36Hi,
If I want to load Redshift in Maya, I need to specify some ENV variables:
[spoiler title=""] "REDSHIFT_COREDATAPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23",
"REDSHIFT_PLUG_IN_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\2024\\nt-x86-64",
"REDSHIFT_SCRIPT_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts",
"REDSHIFT_XBMLANGPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\icons",
"REDSHIFT_RENDER_DESC_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\rendererDesc",
"REDSHIFT_CUSTOM_TEMPLATE_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts\\NETemplates",
"REDSHIFT_MAYAEXTENSIONSPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\2024\\nt-x86-64\\extensions",
"REDSHIFT_PROCEDURALSPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Procedurals",
"MAYA_PLUG_IN_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\2024\\nt-x86-64",
"MAYA_SCRIPT_PATH" : "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts",
"PYTHONPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts",
"XBMLANGPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\icons",
"MAYA_RENDER_DESC_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\rendererDesc",
"MAYA_CUSTOM_TEMPLATE_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts\\NETemplates",
"PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\bin"[/spoiler]
Do I do this in the launcher: then Maya crashes when loading the plugin. As a workaround, you have to save the variables in Maya.env and then load them via ENV:
"MAYA_ENV_DIR": "path to maya.env"
in maya.env : [spoiler title=""]REDSHIFT_COREDATAPATH = \\qumulo\Pipeline\Pipeline\PRISM\PSL\DCC_configs\redshift\Redshift_v3.5.23
REDSHIFT_PLUG_IN_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\2024\nt-x86-64
REDSHIFT_SCRIPT_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\scripts
REDSHIFT_XBMLANGPATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\icons
REDSHIFT_RENDER_DESC_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\rendererDesc
REDSHIFT_CUSTOM_TEMPLATE_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\scripts\NETemplates
REDSHIFT_MAYAEXTENSIONSPATH = %REDSHIFT_PLUG_IN_PATH%\extensions
REDSHIFT_PROCEDURALSPATH = %REDSHIFT_COREDATAPATH%\Procedurals
MAYA_PLUG_IN_PATH = %REDSHIFT_PLUG_IN_PATH%
MAYA_SCRIPT_PATH = %REDSHIFT_SCRIPT_PATH%
PYTHONPATH = %REDSHIFT_SCRIPT_PATH%
XBMLANGPATH = %REDSHIFT_XBMLANGPATH%
MAYA_RENDER_DESC_PATH = %REDSHIFT_RENDER_DESC_PATH%
MAYA_CUSTOM_TEMPLATE_PATH = %REDSHIFT_CUSTOM_TEMPLATE_PATH%
PATH = %REDSHIFT_COREDATAPATH%\bin[/spoiler]v2.0.3
Hi,
If I want to load Redshift in Maya, I need to specify some ENV variables:
"REDSHIFT_PLUG_IN_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\2024\\nt-x86-64",
"REDSHIFT_SCRIPT_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts",
"REDSHIFT_XBMLANGPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\icons",
"REDSHIFT_RENDER_DESC_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\rendererDesc",
"REDSHIFT_CUSTOM_TEMPLATE_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts\\NETemplates",
"REDSHIFT_MAYAEXTENSIONSPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\2024\\nt-x86-64\\extensions",
"REDSHIFT_PROCEDURALSPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Procedurals",
"MAYA_PLUG_IN_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\2024\\nt-x86-64",
"MAYA_SCRIPT_PATH" : "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts",
"PYTHONPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts",
"XBMLANGPATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\icons",
"MAYA_RENDER_DESC_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\rendererDesc",
"MAYA_CUSTOM_TEMPLATE_PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\Plugins\\Maya\\Common\\scripts\\NETemplates",
"PATH": "\\\\qumulo\\Pipeline\\Pipeline\\PRISM\\PSL\\DCC_configs\\redshift\\Redshift_v3.5.23\\bin"
Do I do this in the launcher: then Maya crashes when loading the plugin. As a workaround, you have to save the variables in Maya.env and then load them via ENV:
"MAYA_ENV_DIR": "path to maya.env"
in maya.env :
REDSHIFT_PLUG_IN_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\2024\nt-x86-64
REDSHIFT_SCRIPT_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\scripts
REDSHIFT_XBMLANGPATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\icons
REDSHIFT_RENDER_DESC_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\rendererDesc
REDSHIFT_CUSTOM_TEMPLATE_PATH = %REDSHIFT_COREDATAPATH%\Plugins\Maya\Common\scripts\NETemplates
REDSHIFT_MAYAEXTENSIONSPATH = %REDSHIFT_PLUG_IN_PATH%\extensions
REDSHIFT_PROCEDURALSPATH = %REDSHIFT_COREDATAPATH%\Procedurals
MAYA_PLUG_IN_PATH = %REDSHIFT_PLUG_IN_PATH%
MAYA_SCRIPT_PATH = %REDSHIFT_SCRIPT_PATH%
PYTHONPATH = %REDSHIFT_SCRIPT_PATH%
XBMLANGPATH = %REDSHIFT_XBMLANGPATH%
MAYA_RENDER_DESC_PATH = %REDSHIFT_RENDER_DESC_PATH%
MAYA_CUSTOM_TEMPLATE_PATH = %REDSHIFT_CUSTOM_TEMPLATE_PATH%
PATH = %REDSHIFT_COREDATAPATH%\bin
v2.0.3
Quote from RichardF on 8. February 2024, 23:59It should work fine to set up the env vars in the Launcher. I just tested it here without problems.
Eventually there is something different with network paths (I was testing with local paths).
You could try to enable the debug mode in the User Settings and then opening the Launcher from a Windows command prompt. You will see then in the console the exact variables and values which will be set when launching Maya.
But using the Maya.env be also a totally valid approach.
It should work fine to set up the env vars in the Launcher. I just tested it here without problems.
Eventually there is something different with network paths (I was testing with local paths).
You could try to enable the debug mode in the User Settings and then opening the Launcher from a Windows command prompt. You will see then in the console the exact variables and values which will be set when launching Maya.
But using the Maya.env be also a totally valid approach.