Were you working on a PC then trying to open the file on a MAC or vice versa? RE: why not just save WHAT IS MADE rather than saving the STEPS IT TOOK TO GET THERE As far as I know this is one of the main differences b/t saving as a .ma vs .mb. .ma saves all your steps in a text file and .mb saves only your current state.…
I can't help you out, don't have Maya. But maybe a few quick reminders if you haven't tried these already.. Have any auto backups around? Do you save your files in increments? Have you tried importing/merging this file into a new scene? Good luck, losing work always sucks. But learn from your mistakes if you can (ie, turn…
" 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…
Yeah, I have tried importing into a new scene, and I could not find the settings to turn on auto-save so never bothered (im new to Maya) Got afew OLD backups :(
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…
Hey, could someone please try and open this scene file. It is saved with Maya 2013 64bit. My maya will only load 99% then it just freezes, it's only a small mesh, but I don't have time to remake most of it :( https://dl.dropbox.com/u/63494571/University/VFX/Semester%201/Digital%20Presentation/mesh.ma
+1 on JMYoung's suggestion. Delete history is essential when working with Maya. Especially before saving your scene upon closing Maya/New Scene/Opening another scene. Delete history is under Edit > Delete by type / Delete all by type > History
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.
Let's say your mesh at start looked like a cube. You apply a gazillion history states and afterward it looks like a sphere. When you save that scene and open it again Maya starts from a cube and goes through each history state one by one to try to recreate that sphere looking model. But... it fails somewhere along all…