Hi,
Yes. I am using the .zip method. Well, actually, ive been experimenting with two.
1. The standard .zip method (while still trying to invoke Modules, rather than just env. variables)
2. I did local install of Vray, then copied the entire Vray dir to a network place, and use modules/variables that way. I tried this method, because all our other module plugins all have a standard dir structure. The .zip method, breaks everything into 3 sub dir's -
maya_root
maya_vray
vray
Some of these have other duplicate sub dir's with different contents - like maya_root and maya_vray both have bin dir's each contain different items.
Then deleted the local install after retreiving the folder contents
So, if we focus on just one of my methods - the .zip method, here is my set up so far...
Windows Env Variables in use:
MAYA_MODULE_PATH = C:\USERS\MIKE\DESKTOP\MODULES(This is just a testing location, once its ready for real world use, this path will change)
MAYA_RENDER_DESC_PATH=R:\Pipeline\packages\V-Ray\36003\maya_root\bin\rendererDesc
VRAY_FOR_MAYA2018_MAIN_x64=R:\Pipeline\packages\V-Ray\36003\maya_vray
VRAY_FOR_MAYA2018_PLUGINS_x64=R:\Pipeline\packages\V-Ray\36003\maya_vray\vrayplugins
My Maya Module file, located in above path (C:\USERS\MIKE\DESKTOP\MODULES)
+ MAYAVERSION:2018 V-Ray any R:\Pipeline\packages\V-Ray\36003\maya_vray plug-ins: R:\Pipeline\packages\V-Ray\36003\maya_vray\plug-ins icons: R:\Pipeline\packages\V-Ray\36003\maya_vray\icons scripts: R:\Pipeline\packages\V-Ray\36003\maya_vray\scripts PYTHONPATH: R:\Pipeline\packages\V-Ray\36003\maya_vray\scripts PATH +:= bin
The V-ray network location of files hasnt been changed with standard contents in each of the 3 main directories...
maya_root
maya_vray
vray
|