2022 nightly issues thread

[yolov]

I can't think of any reason why this wouldn't work. It works locally, so the build is OK.
Are you by any chance submitting to the farm with a render manager like deadline?
If yes - are there any options set to the queue to alter settings (f.e. to set the denoiser to vdenoise?)
Or are there any options set in the submitter to alter such settings?

If you try and run the same scene (for just one frame) on the farm by logging on the farm machine and starting batch manually - will it work? If it works, I would start searching for the cause somewhere in the submitter/queue.

[yolov]

Btw, just a warning, that using an AI denoiser (like nvidia or intel) will likely flicker in animation.

[seandunderdale]

Whats the Maya 2022 consensus? Is it safe to upgrade from 2020? Or is it buggy as hell? Im finding Ive got some issues with Vr scans that are Maya 2020 related apparently, so Im considering switching up to 2022.

[oglu]

Wait for Maya2022.1 it should be there in some weeks. And be sure you are ready for Python3.

[AntonioMilo]

Hi everyone, thinking of upgrading from maya 2018.7, to maya 2022.1 - what's the general mood, is it reliable, are there loads of bugs? We're in between jobs and looking to upgrade software and review pipeline.

[francomanko]

im on 2022, seems pretty stable to me, be aware that its now python 3 so not all your scripts may work...you can start it in legacy python2 mode though, which is what ive done by having this in the properties of the maya shortcut

""C:\Program Files\Autodesk\Maya2022\bin\maya.exe" -pythonver 2"

[Muhammed_Hamed]

Maya 2022.1 feels great honestly, I think it is worth upgrading to

[seandunderdale]

im on 2022, seems pretty stable to me, be aware that its now python 3 so not all your scripts may work...you can start it in legacy python2 mode though, which is what ive done by having this in the properties of the maya shortcut

""C:\Program Files\Autodesk\Maya2022\bin\maya.exe" -pythonver 2"

Does this have any impact on any new tools or Maya functionality? Or is it just purely related to python being input into the script editor / code added by the user?

[francomanko]

i havent found any issues with having it set to legacy, but i couldnt guarantee it

[AntonioMilo]

Thanks, everyone! I will probably run it in python legacy mode, to begin with. Ok, Maya 2022, here we go!

[mschreck]

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.

Hello,unfortunately I have the same error message with maya 2022.1 & Vray 5 when trying to load in the vray plugin - I understand that this would related to ENV/PATH settings. But what paths exactly do I need to add to the user? system? env. for vray to properly load?

[yolov]

Hey, sorry, the thread has become quite long, so apologies if I'll suggest something that was already posted before.

Usually, when you have an error that vrayformaya.mll can't load, it's because something in the installation or the environment setup isn't right.
There's different reasons for this and the easiest thing to try is re-install V-Ray.

If that doesn't work, there's a good chance that something in your environment setup is wrong - an environment variable is holding a wrong value. This can happen because an old installation didn't properly clean up during uninstall, or something similar.
--> You can check your system and user environments on windows and make sure that there's no weird values for VRAY_FOR_MAYA<version>_PLUGINS, VRAY_FOR_MAYA<version>_MAIN, PATH, PYTHONPATH, MAYA_PLUGIN_PATH or another variable (I've listed the ones that I'd check first).

Then there's a chance you have a wrong environment variable value in either C:\Users\<username>\Documents\maya\<version>\Maya. env or in a module file somewhere.

If you get to this point and there's still issues - it's best to start maya, don't load vray and just print the entire environment that has reached Maya. You can do this in a Python tab in the script editor with a few lines like this:

import os

for k, v in os.environ.items():
print(f'{k}={v}')

This will give you all environment variables and given you know where V-Ray is installed (by default it's C:\Program FIles\Autodesk\Maya<version) you can check if something points to a weird location.
I would go in and manually delete the faulty variable, re-install V-Ray and it should be fixed.

In case you're using our zip builds - make sure you've updated your bat/shell script / .env file with the environment variables and their values for V-Ray 5.1 (there were a few changes in 5.1). You can check the correct environment here: https://docs.chaosgroup.com/display/...p-SetupforMaya

Finally, there's a small chance that you have installed the V-Ray AppSDK seperately (there was a known issue that AppSDK could prevent vrayformaya.mll from loading, which is fixed in the latest AppSDK versions).