Okay, I read somewhere that I could try and find the problem in the MA file, so I opened it in the script editor and ran the code. It flags up this error: Here is the code, it's funny that the setAttr is actually on like 3773: Could I just allow it to run up until it hits the problem? That MIGHT save me some time.
Okay, first of, i'm an idiot for not doing regular backups. Secondly, Maya is retarded - why not just save WHAT IS MADE rather than saving the STEPS IT TOOK TO GET THERE... This file is not opening in Maya 2013 that it was made in, I have loaded it into the script editor and I get this error, and that line of code is RIGHT…
You have like 3000 history nodes, its a good idea to clear history when modeling if you aren't going to be tweaking any nodes/deformers, or before unwrapping, rigging/skinning. I can't be of any help but Alias used to fix scene files on their forum when submitted, maybe Autodesk will do the same.
I can open it fine with 2013 64bit. The main structural mesh is completely screwed, though, a total mess of geo. You need to start deleting history more often as it has a tooooooon of nodes. That will often times mess things up when trying to re-open a file.
i just had a thought... if the cry engine has a plugin check your plugin editor and make sure its loaded before you try to open the file. sometimes maya will not load certain plugins. that could easily cause maya to crash on the file. as its reading nodes in the file it has no knowledge of.
" why not just save WHAT IS MADE rather than saving the STEPS IT TOOK TO GET THERE" the point of an ascii scene file is it can be parsed an written by third party apps and scripts. a ma file is essentially a mel script. so for instance you can have a compositing app write out a maya scene which has 3d lighting data that…