ImportError: No module named asgvisInit

[Fredrik Averpil]

Hi,

I've installed Maya 2015 Extension 1 SP5 as well as V-Ray 3.0 for Maya on the network (so called "Thin Client"). And perhaps this is why I cannot launch the vrmat editor (from within the vrmatMtl attribute editor; button "Show VRMat Editor").

When I click that button I get:

# Traceback (most recent call last):
#   File "<string>", line 1, in <module>
# ImportError: No module named asgvisInit

So, I thought that this would be fairly easy to fix. I'd just have to locate "asgvisInit" and append its location to sys.path (PYTHONPATH) before launching Maya. But I can't find this anywhere in the V-Ray 3 installation. I installed V-Ray 3 using the ZIP file bundles.

Do you know where it could be located?

[t.petrov]

Have you found the asgvisInit.py file? It should be located in the vray/scripts/ folder.

What is the exact version you're trying to use and what kind of package are you using (zip or executable) to install V-Ray?

Can you try if the python post translate scripts work?

/Teodor

[Fredrik Averpil]

Hi Teodor,

I installed from zip, the V-Ray 3.00.01 version from the download area for Maya 2015 64-bit.

No I can't find the asgvisInit.py file in the /maya_vray/scripts forlder. Could it be missing from the zip?

[Fredrik Averpil]

Hm.

There seems to be a pretty big discrepancy between the 3.00.01 release and the latest stable nightly...

This is from the stable build 25208 zip, maya_vray/scripts/vray:

2014-11-14  09:44    <DIR>          .
2014-11-14  09:44    <DIR>          ..
2014-11-07  09:10             6*970 acolor.py
2014-11-14  09:44    <DIR>          ASGVIS
2014-11-07  09:10            12*778 asgvisInit.py
2014-11-07  09:10             9*366 color.py
2014-11-07  09:10               274 helperfunctions.py
2014-11-07  09:10             3*474 hostvrayplugman.py
2014-11-07  09:10           107*000 MaterialPreviewScene.xml
2014-11-07  09:10            11*623 matrix.py
2014-11-07  09:10             6*637 mayahostapp.py
2014-11-07  09:10             6*422 plugin.py
2014-11-07  09:10           243*712 pluginmodifier.pyd
2014-11-07  09:10             2*778 pluginoutput.py
2014-11-07  09:10         1*257*472 PyBin2Xml.pyd
2014-11-07  09:10            63*994 pyCallbacks.py
2014-11-07  09:10             3*282 PyProcMsg.py
2014-11-14  09:44    <DIR>          PyQt4
2014-11-07  09:10         7*999*488 PyVRay.pyd
2014-11-07  09:10            75*776 sip.pyd
2014-11-07  09:10            64*364 TexturePreviewScene.xml
2014-11-07  09:10               194 toolTipStyle.css
2014-11-07  09:10             6*760 transform.py
2014-11-07  09:10             4*271 utils.py
2014-11-07  09:10             8*704 vector.py
2014-11-07  09:10             2*751 VRayPluginChanges.xml
2014-11-07  09:10           797*645 VRayPlugins.xml
2014-11-07  09:10             1*539 vraytype.py
2014-11-07  09:10             7*132 xgen.py
2014-11-07  09:10             6*983 xgenVRayUI.py
2014-11-07  09:10               255 __init__.py

and this is from the official 3.00.01 zip release, maya_vray/scripts/vray:

2014-11-13  11:42    <DIR>          .
2014-11-13  11:42    <DIR>          ..
2014-10-16  23:41             6*970 acolor.py
2014-10-16  23:41             9*366 color.py
2014-10-16  23:41               274 helperfunctions.py
2014-10-16  23:41            11*623 matrix.py
2014-10-16  23:41             6*422 plugin.py
2014-10-16  23:41           243*712 pluginmodifier.pyd
2014-10-16  23:41             2*778 pluginoutput.py
2014-10-16  23:41             6*760 transform.py
2014-10-16  23:41             4*271 utils.py
2014-10-16  23:41             8*704 vector.py
2014-10-16  23:41             1*539 vraytype.py
2014-10-16  23:41             7*132 xgen.py
2014-10-16  23:41             6*983 xgenVRayUI.py
2014-10-16  23:41               255 __init__.py

EDIT: I can confirm that I can successfully load the VRMat editor when running the stable nightly. So I'm just going to remove the official build alltogether here.

[t.petrov]

Yes, it seems there are problems with the zip installer.

A temporary work around is to use the exe installer and tell it to install in a custom location.
Then you can apply the same procedure as using the zip installer.

Thanks for reporting it and sorry for the inconvenience.

[Fredrik Averpil]

Ok, thanks. I think we will be fine with the stable build 25208 so I'll just use that.