Hi, after installing;
// Error: file: C:/Program Files/Autodesk/Maya2022/scripts/others/pluginWin.mel line 316: The specified procedure could not be found.
(vrayformaya) //
When loading via plugin manager. vrayvolumegrid + xenVRay load ok
Hi, after installing;
// Error: file: C:/Program Files/Autodesk/Maya2022/scripts/others/pluginWin.mel line 316: The specified procedure could not be found.
(vrayformaya) //
When loading via plugin manager. vrayvolumegrid + xenVRay load ok
I posted this one already in another thread. but just to have it all in one place:
Maya 2022 seems to have a problem with OCIO configuration.
I set the environment variable and enabled the legacy syncolor color management. the two pictures show the problem I have with Maya 2022 and OCIO. Purple fringing all over the place. (see attachements)
EDIT:
Just tested again and double checked the VRay Version. I can now say that the VRay 5 Update 1 Version on both Maya 2020 and 2022 seem to have the same OCIO Issue with fringing.
Same Maya Version 2020.4 with Vray5 Hotfix 3 is working just fine.
From New features:
(*) Viewport 2.0: VRayLayeredTex basic viewport preview;
Also I tried the VRayLayeredTex. Should this be previewing in Viewport now? I don’t get visual feedback there, I can only see the top layer. But rendering is fine.
used the latest build from 30.04. on Maya 2022, Windows 10
Does V-Ray work OK after that (I assume it would)?
Do you have mtoa (arnold) loaded? Can you try setting it to not autoload, restart Maya and see if the same error appears again?
Yes, we’ve already logged this. We’ll look into it.
This is how far we can take it for now - we can only show the top layer, so this is working as expected in the viewport.
thank you! I am really looking forward to the new updates! Looks really promising! ![]()
No, V-Ray does not load on vanilla maya 2022 install.
Just this when loading;
// Error: file: C:/Program Files/Autodesk/Maya2022/scripts/others/pluginWin.mel line 316: Unable to dynamically load : C:/Program Files/Autodesk/Maya2022/vray/plug-ins/vrayformaya.mll
The specified procedure could not be found.
No arnold either and default vray installation settings.
I’m having issues with GPU LC in production mode as well
It stops on building LC most of the time, then I cannot close the render like you
If you turn GPU LC off, everything works fine in production rendering..
And yeah LC GPU uses a lot of VRAM, nearly double the amount that the IPR uses.. I’m testing this now, and will report soon
I don’t understand how everyone got V-Ray to work in 2022, which build are you guys using?
5.1 Beta, check the announcement section @snivlem
Yeah I did, have 5.1 installed from 30th of April, but none of the builds load on a vanilla Maya 2022.
Even not using plugin manager, and using the ‘loadPlugin’ MEL command
loadPlugin “C:\\/Program Files\\/Autodesk\\/Maya2022\\/vray\\/plug-ins\\/vrayformaya.mll”
I get this:
loadPlugin “C:\\/Program Files\\/Autodesk\\/Maya2022\\/vray\\/plug-ins\\/vrayformaya.mll”;
// Error: line 1: Unable to dynamically load : C:/Program Files/Autodesk/Maya2022/vray/plug-ins/vrayformaya.mll
The specified procedure could not be found.
//
// Error: line 1: The specified procedure could not be found.
(vrayformaya) //
@yolov , is there something I can send in to help diagnose?
Looking online, people have the same 316 issue with renderman and Maya 2022, but it seems the solution was the plugin needed to be updated??
So I cant use the GPU lightcache because its pushes over the memory limit of my 2080ti. Without it turned on its fine with scene using about 9.3 gig. Turn on the lightcache gpu wip and it shoots up over the limit. This isnt going to be the case when normally is it? If so, it defeats the point.
Is Chaos support around? The beta site doesnt log in either for the day.
"Oops…
We are having technical difficulties. Please try later.
"
To update on the Maya 2022 situation
Rebuilt windows, installed a fresh copy of Maya 2022, fresh beta of VRay 5.1 and V-Ray does not load with Maya 2022.
I’ve installed polytrans which works with 2022 and a few other plugins. Just V-Ray refuses to load and I have no idea why it’s working for others
Hey, sorry for the delay here, thanks for being patient. I’ll try and get answers to all questions in this thread. See my posts below.
Hi Karol,
This beta in particular is more of an exception, than a rule.
We usually launch betas for major versions, but this time around we wanted to get people on board with our progress, especially with USD support, so we decided to open up the builds to all existing users before the official launch. We actually have never done this before and it’s interesting to know if people will welcome it, both in terms of getting feedback on the features and on the fact that we have a point-release-beta.
Update 1 for 3ds Max was not in beta, it never was. We just decided to do this for Maya and Houdini specifically.
As for features like GPU LC and Out-of-core - those features themselves are initial implementations and we put a ‘WIP’ label next to them just to make sure people know this and we are working on making them more stable and robust - once that’s done we’ll remove the ‘WIP’ label, but this is completely outside of the scope of any betas or releases.
Having said that - I noticed that there’s lots of VRAM issues with GPU LC and I’ll make a separate post about it.
I hope that this helps clear things up. Any further thoughts are more than welcome.
Anyway I am so excited to see some progress in displaying V-Ray materials in Maya’s viewport. You guys said many times that it is really challenging to make it work in Maya.
Progressive caustics - can’t wait to try it!
We’re working on the viewport preview, I hope it was easier than it is, but I’m sure we’ll get there soon. I’ll be making posts on the forums for any updates we have on our progress.
I got to mention that I am on NVIDIA driver version of 462.31 which is newer than recommended. In the meantime , I will rollback the driver to the recommended one and hope that most of my GPU IPR fatal errors will disappear.
I saw your other post that even the recommended driver doesn’t help. Can you tell me what’s in the scene roughly? And what’s the video card? For example, are there a lot of proxy objects in the scene? Or lots of displacement/subdivision?
Thanks in advance.
I think that was a temporary problem that was resolved quickly. It should be working fine now.
"
To update on the Maya 2022 situation
Rebuilt windows, installed a fresh copy of Maya 2022, fresh beta of VRay 5.1 and V-Ray does not load with Maya 2022.
I’ve installed polytrans which works with 2022 and a few other plugins. Just V-Ray refuses to load and I have no idea why it’s working for others
Is this with the zip builds or with the regular installer ?
Can you tell me what’s in the scene (roughtly)? For example: are there proxy objects, maybe lots of them? Lots of displacement and/or subdivision?
Hi Yolov,
Proxies yeah, i wouldnt say that many, some grass a few trees, nothing that heavy for scenes these days. No subdivisions or displacements. If it ends up using an extra 1.5gig of ram..probably going to be an issue ![]()
For anyone else that got error in line 316 with Maya and where V-Ray will not load,
You’ll have to modify the Path “user variable” in windows’ environment variables.
If you have a previous version of Maya installed (in my case Maya 2020) just remove the “C:\Program Files\Autodesk\Maya2020\bin” entry and keep the “C:\Program Files\Autodesk\Maya2022\bin” entry.
Haven’t seen this occur before but it seems that will fix Maya’s issue in not loading V-Ray.
I’m not sure why other 3rd party plugins loaded with the old Maya path in there but definitely fixed it for me
@yolov , it happened with the regular installer