Fixing a Maya MA file!?

Become a member of the CGSociety

Connect, Share, and Learn with our Large Growing CG Art Community. It's Free!

THREAD CLOSED
 
Thread Tools Search this Thread Display Modes
  10 October 2012
Fixing a Maya MA file!?

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 at the top of the file, so i'm hoping the rest of the instructions will still work if this can be ignored/removed?

Quote: // Error: line 3772: setAttr: Error reading data element number 17: 4


Here is the code, it's funny that the setAttr is actually on like 3773 not 3772:
Quote: 3770: mu 0 4 482 483 484 485
3771: f 4 -1009 1070 1071 1072
3772: mu 0 4 492 486 488 493;
3773: setAttr ".fc[500:999]"
3774: f 4 -1005 1073 1074 -1071
3775: mu 0 4 486 487 489 488
3776: f 4 -1072 1075 1076 1077


Could I just allow it to run up until it hits the problem?

Mesh:
https://dl.dropbox.com/u/63494571/U...ntation/mesh.ma
 
  10 October 2012
If you want it to save "what is made" you should delete construction history or turn construction history off while you are working.

You might beable to comment out the entry that is causing the error.
__________________
blah blah blah
 
  10 October 2012
Didn't realize you had to do that, thanks.

And I will try that, tried it once and didn't work, I will try again.
 
  10 October 2012
Strange, I deleted 2 lines where the error is:

Quote: 3770: mu 0 4 482 483 484 485
3771: f 4 -1009 1070 1071 1072
3772: mu 0 4 486 487 489 488
3773: f 4 -1072 1075 1076 1077


It still came back with the following error even though the setAttr command is not there...
Quote: // Error: line 3771: setAttr: Error reading data element number 17: 4
 
  10 October 2012
If you go into Maya and save out a mesh as mayaAscii and then search for "mu", you will find an entry similar to this.

	setAttr -s 100 -ch 400 ".fc[0:99]" -type "polyFaces" 
 		f 4 0 3 -22 -2
 		mu 0 4 0 1 12 11
 		mu 1 4 0 1 12 11
 		f 4 2 5 -24 -4
 		mu 0 4 1 2 13 12
 		mu 1 4 1 2 13 12
 		f 4 4 7 -26 -6
 		mu 0 4 2 3 14 13
 		mu 1 4 2 3 14 13
 		f 4 6 9 -28 -8
 		mu 0 4 3 4 15 14
 ...


Taking that into account, it looks like the error message is actually accurate. You need to take the file into context here, not just line by line reading as the file itself is basically a MEL script with a limited set of commands at its disposal. So these lines:

3771: f 4 -1009 1070 1071 1072
  3772: mu 0 4 492 486 488 493;


are arguments to a setAttr command on a polyFaces attribute type. Have a look at the erroneous line in particular and try commenting it out. It will likely leave a hole or corrupt your mesh, but it might at least allow you to recover the rest of the scene or let you fix the issue in Maya.
 
  10 October 2012
Hmm, ive tried to delete all of the commands that look like this:

Quote: setAttr ".fc[2000:2067]"
f 4 4043 4044 -4043 -3312
mu 0 4 1942 2458 2456 1943
f 4 -3324 4045 -4044 -3315
mu 0 4 1944 1949 2458 1942
.....


As they keep on causing the errors it seems, but I still can't get it to work. Any chance you could get it working Keilun?
 
  10 October 2012
I can give it a shot if you share the file.

The real question is, after removing all those setAttrs, has the error changed? And if so, what is it complaining about now? You're basically removed all the face connectivity data from whichever meshes you removed the setAttr -type "polyFace" from.

Last edited by Keilun : 10 October 2012 at 06:52 PM.
 
  10 October 2012
I provided a link to the file in my first post, and thanks.

Also, it eventually complained about not being able to reference objects I think, but I don't think it did what you said correctly.
 
  10 October 2012
So, I don't seem to get to the point of errors. I tried this in two cuts:

Maya 2013x64
On opening the scene in this version, the file hung indefinitely. I had to kill the process after waiting about 20 minutes.

Maya 2013APx64
On opening the scene in this version, it opened without any script errors. The scene was garbled and I had a large number of warnings:

// File read in 2 seconds.
// Warning: line 0: Can't perform polySplit7 on selection // 
// Warning: line 0: Can't perform polySplit9 on selection // 
// Warning: line 0: Can't perform polySplit10 on selection // 
... [snip] ...
// Warning: line 0: Can't perform polyAppend16 on selection // 
// Warning: line 0: Can't perform polyConnectComponents35 on selection // 
// Warning: line 0: Can't perform polyConnectComponents36 on selection // 
// Warning: line 0: Can't perform polyConnectComponents38 on selection // 
// Warning: line 0: This file is from an older version of Maya.  If saved, it will not be readable by previous versions. // 


Sorry I couldn't be of more help, but I can't reproduce the errors that you're seeing.
 
  10 October 2012
Sorry I should of said that I got the errors by loading the file into the script editor as Maya also froze on me when trying to open it, I had to end the process.

I'm going to take it as something has gone really wrong with the scene and it's best to redo the work?
 
  10 October 2012
Ah I see. I should read more carefully too. Yeah I think some of these setAttr commands for setting up the mesh may be reserved for file IO and as a result may not be usable directly in the script editor. That's just a guess based on the fact that all setAttrs on type polyFace appears to spit out the same error. Once you remove one, the next one fails, etc.

I also tried removing the UI configuration script lines to see if that'd help, but that didn't pan out.

Given that it doesn't hang in 2013AP, another thing to try is grabbing the latest service pack for 2013 and see if that works. But if it opens up similar to the way 2013AP did, it will be mostly unusable.

So yeah, at this point I'd say start looking at redoing your work and backing up the scene files going forward.
 
  10 October 2012
I opened up your file and was noticing how similar your DAG network for that object looked to your model. 1200+ nodes of history on that object!
Attached Images
File Type: jpg temp.JPG (65.1 KB, 13 views)

Last edited by 3Dmonkey : 10 October 2012 at 04:55 AM.
 
  10 October 2012
Damn, yeah I didn't realize how important it was to clear the history, thanks for the help guys. I will just re-do the work, tbf it isn't that much at all, just a pain in the ass to get the proportions right.
 
  10 October 2012
Thread automatically closed

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
__________________
CGTalk Policy/Legalities
Note that as CGTalk Members, you agree to the terms and conditions of using this website.
 
Thread Closed share thread



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
CGSociety
Society of Digital Artists
www.cgsociety.org

Powered by vBulletin
Copyright 2000 - 2006,
Jelsoft Enterprises Ltd.
Minimize Ads
Forum Jump
Miscellaneous

All times are GMT. The time now is 02:52 PM.


Powered by vBulletin
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.