Hey @Utkarsh_Agnihotri,
I am using Prism with Maya 2022 too, but not on mGear4 yet. I think thatâs pretty much like Chris said about the Environment Variables before.
When loading Maya (or other DCC) from Prismâs Project Browser, it adds your current Project path in the environment variables.
So it may be wiping your default environment (which is odd, usually it doesnât mess with settings of things you already have installed).
Try this: copy the mGear folder from your userâs Maya script path (normally found at \Users\your-username\Documents\maya\scriptsâŠ) and paste it inside your active Prismâs Project Custom Modules (if using default settings, it should be something like â00_PipelineâŠCustomModules\Maya\scriptsâ). Reload Prism and see if that works.
Not just mGear, you should put there any other scripts or modules which will be used on your project. It is like that to help everyone in same project to have access to allowed/required plugins per project.
If same error occurs maybe thereâs another reason causing it, because when I started working with Maya 2022 a couple weeks ago got similar errors and noticed having a bunch of â_ _ pycache _ _â folders added to plugins inside that Custom Modules path.
Didnât quite investigated further, just deleted those Pycache folders, wrote a custom launcher adding âPYTHONDONTWRITEBYTECODE=1â environment variable and pointed Prism to load Maya from it on Prismâs Project Settings menu.
Got no more errors after that but also still donât know what was causing it.
Could be something Python 2 vs. Python 3 related but I am just guessing about.
I hope it helps you to figure out a solution though.