with today’s build (and also with builds from end of feb) we get the following error messages on startup
VFH * Python evaluation error: “No module named vray”
VFH * Traceback (most recent call last):
VFH * File “<stdin>”, line 1, in <module>
VFH * ImportError: No module named vray
everything seems to work though.
Same here, and nothing special in my config, using the json file coming with the nightly build archive…
I posted about this. No suggestions helped my case though.
Please, check this post - Chaos Forums
I have checked it and double checked it. For some reason I still get the errors.
I will remove the vray folder and remove the entry in the *.env and then try an installer
yep, that fixed it, thanks!
Jim Meston, this post is related only to “import vray” error.
Those Python import errors are somehow caused by qLib (or may be just any other plugin that is setup through .env, but I have only this one installed) along with VFH and seems to be related to .391 build since I haven’t noticed those messages earlier.
we tried with the previous houdini production build and a version from end of feb and had the same issue (but didn’t know about the fix).. just updated to 391 with todays VFH build. by adding
“{ “PYTHONPATH” : “${INSTALL_ROOT}/appsdk/python27” },” to the json or the env file (in the appropriate format of course) made all errors go away
Old Thread, but same here.
Houdini 19.0.455 with Vray 52002 threw the “No module named vray” error even when rendering Redshift jobs.
Editing C:\Program Files\Side Effects Software\Houdini 19.0.455\packages\vray_for_houdini.json solved the problem.
Not sure how is it related to Redshift, but yes, wrong vray_for_houdini.json contents are causing loading fail… and yes, fixing the .json contents is the only way to fix this…
We’re making a different Houdini build for each renderer, they don’t like being in the same build 
Not sure how is it related to Redshift
Just to confuse TDs and artists? 
Locally, it renders fine, but the error throws Deadline of its rail.