Search and replace your text file, replace #QNAN with 0 and it should load up after that. QNAN is programmer geek for something like "Not A Number" - maybe out of range or infinity, etc.
Two more problems that are usually easy to fix: search for QNAN and #INF and replace with a 0. Sometimes Maya gets an infinite number (the second one) - and the first is not a number. You'll see a camera transform in the .ma file that's like: 23.QNAN so if you replace it with a zero it will work.
Sorry for the double post but I thought I should mention that I opened up the .ma in a text editor to check for the #QNAN and #INF issue and didn't fine any instances of either, so that doesn't seem to be the problem...
Sometimes you can do a search for "-1.#QNAN" or "-1.#IND" (without the quotes of course) and just replace with 0.0. It won't bring back stuff, but if you're file is so bad that it crashes on load it can get it back to a point where it'll load back up.
Are you using maya ascii? You should since sometimes things like this can be saved. If you are, load in up in a text editor and do a search for "-1.#QNAN" or "-1.#IND" and if you find and replace the each with "0.0". That's not always the problem but it's pretty common in scenes that crash on loading.
OMG. I saw a bunch of posts about the QNAN and NAN, but my file still wasn't working after changing those. I legit signed up for this forum just to thank you for pointing out how to look for IND and how to fix it. That just saved my artist's ass who would have otherwise lost a full day of work.
Try this on... Open the .ma/.mb in wordpad and doing a find & replace on the value below. Find: #QNAN Replace with: 0 (thats a zero) then... Save as .ma/.mb I cant guarantee that this will work, but it worked for me twice in two times this has happened to me. Maya (or a goblin :poly122:) corrupts vertex data and maya…