Is MAYA_MODULE_PATH supposed to take one or multiple paths?

[mail]

Can someone confirm whether MAYA_MODULE_PATH can take more than one path? 

I thought we could simply add plugin paths to the MAYA_MODULE_PATH but a recent problem with getting Arnold working this way suggests that the MAYA_MODULE_PATH must only have a single path defined (which itself can contain multiple .mod files pointing to the different plugins). 

Is that right? 

If not, can someone confirm whether Arnold's inability to support a MAYA_MODULE_PATH with multiple paths is in fact a bug? 

I discovered this behaviour on Maya 2018.2, MtoA 3.0.0.1, Windows 7 Professional.

Thanks

p.

[Stephen.Blair]

MAYA_MODULE_PATH is a list of paths.

In my current instance of Maya, here's the MAYA_MODULE_PATH:

MAYA_MODULE_PATH=D:/solidangle/mtoadeploy;;C:/solidangle/yeti/Yeti-v2.2.1_Maya2018-windows64/Yeti-v2.2.1_Maya2018-windows64;D:/Program Files/Autodesk/Maya2018/modules;C:/Users/blairs/Documents/maya/2018/modules;C:/Users/blairs/Documents/maya/modules;C:/Program Files/Common Files/Autodesk Shared/Modules/maya/2018

[mail]

Thanks Stephen,

Is that your module path before or after Maya is launched? 

For me, my MAYA_MODULE_PATH is similar to yours after maya has launched. 

What does your MAYA_MODULE_PATH have assigned prior to Maya launch, and/or how and where are you adding paths during the maya load sequence?

Thanks again

Patrick 

[Stephen.Blair]

Hi Patrick

I start Maya with a batch file, and in that batch file I add the MtoA and Yeti paths to MAYA_MODULE:

set MAYA_MODULE_PATH=C:\solidangle\yeti\Yeti-v2.2.1_Maya2018-windows64\Yeti-v2.2.1_Maya2018-windows64;%MAYA_MODULE_PATH%

set MAYA_MODULE_PATH=D:\solidangle\mtoadeploy;%MAYA_MODULE_PATH%

[mail]

Right, so it is definitely something I am doing that is wrong. What a surprise!
I'm assigning the paths in python like this :
os.environ['MAYA_MODULE_PATH'] = studio_module_path + os.pathsep + arnold_path + os.pathsep + os.environ.get('MAYA_MODULE_PATH')

The paths are all UNC; eg '\\mount\dev\path'
Perhaps there's some string-type issue I'm introducing by the way I'm building the env var string?