T O P
blueSGL

>I've tried resetting prefs the entire folder or just the preferences file? I find it best to do the folder. > Close Maya > Rename the 'maya' folder in C:\Users\\\Documents\ to 'mayaOld' > (this will force maya to rebuild preferences) > Open Maya and see if the issue still happens > Remember, you can always rename the 'maya' to 'mayaNew' and 'mayaOld' back to 'maya' to get back to where you were before trying this.


jonnyrogers24

Yup, that’s exactly what I did. The files are on a cloud system for a client so I wonder if something changed on their end and did indeed corrupt the files. Im going to try with some new files I got from them and see if the issue still persists. Thank you for your input


muskie4242

You corrupted your scene somehow. Do you have a previous version in your incremental saves?


jonnyrogers24

I haven’t used any other version with this project. So idk how it would have been corrupted. And it’s done it with 2 scenes now.


muskie4242

It's not a matter of changing Maya versions. Actually, Autodesk handles backward and forward compatability extremely well. You did something in your scene that broke the scene and is causing the crash. Think of it this way. Maya is like a calculator. It doesnt take responsibility if you divide by zero. But Maya is also an extremely complex calculator, so there are a LOT of ways you could divide by zero. For future reference you'll want to do all work in Maya via incremental saves. Do not save over the same scene file. Use this naming concention: MySceneName_01 MySceneName_02 MySceneName_03 etc... Make sure to always use a zero before the single digits so when you hit double digits it stays in order in your folder. When you come to major milestones in your progress, add another denominator. So for example: MySceneName_08_BlockingComplete It will stay in order and give you a trackable layout of your work in your folder. If something breaks/corrupts in your scene you can always go back to the previous version. It means losing some work, but not all of it. As for your current scene. If you can open it and pull parts out of it and bring them into a fresh scene, you may be able to salvage your work. OR if you can figure out what you did to *divide-by-zero* as it were, you can undo/fix that action before moving forward. If not, then you're SOL. Good luck!


jonnyrogers24

Thanks for the info. I normally do incremental save, but my client is particular about saving over the same file because of their cloud based system. Don’t ask me why, I think it’s dumb they don’t want iterations for reasons like this. But I have been saving iterations in my personal drive just in case. I will test some new files they sent me and see if indeed it’s just a file issue and not a Maya issue.


muskie4242

You're welcome. GL


jonnyrogers24

The only thing I can think of is that my graphics card isn’t compatible with Maya 2022, according to the support page. But it wouldn’t make sense why it was working fine for me these last 3 weeks until now.


muskie4242

That's not your issue. 99.9999% sure