2022 nightly issues thread

[snivlem]

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

[snivlem]

loading the plugin manually;

// Warning: file: C:/Program Files/Autodesk/Maya2022/scripts/others/pluginWin.mel line 937: Could not load C:/Program Files/Autodesk/Maya2022/vray/plug-ins/vrayformaya.mll as a plug-in //

Env looks ok too

[doppelgaengerdigital]

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

[yolov]

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

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?

[yolov]

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)

Yes, we've already logged this. We'll look into it.

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

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.

[doppelgaengerdigital]

thank you! I am really looking forward to the new updates! Looks really promising!

[snivlem]

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?

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.

[Karol.Osinski]

Hi everybody,
Great to see the update yolov , we all appreciate the hard work you guys put into it. Though, I wonder was update 1 for 3ds max also in BETA initially? I just don't wanna get used to the whole world working this way now, more and more feature we pay for are BETA and we become free BETA testers

Please don't get me wrong, I enjoy trying new things and experimenting with new features and I know this is the way things are nowadays, I just hope it won't escalate too much in V-Ray (now we have OUT OF CORE - BETA and GPU LC - BETA).

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!


Back to the topic.

I just tried LC GPU on one of my scenes and I got the following error.

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.

[Karol.Osinski]

Just installed the recommended driver and I am not getting error anymore, but VFB is empty...
My VRAM spiked up to 19Gb so I presume the scene got fitted into GPU memory but nothing happens, I can't even stop the rendering process.

[Karol.Osinski]

Restarted Maya and relunched the render, now VRAM went up to pretty much 24GB. Does it mean some sort of memory leak?

[Muhammed_Hamed]

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

[snivlem]

I don't understand how everyone got V-Ray to work in 2022, which build are you guys using?

[Muhammed_Hamed]

5.1 Beta, check the announcement section snivlem

[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) //

[snivlem]

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??