Error Opening Maya 2017 mb file in 2018

[carlmichaelk]

Hi ,

I have issues opening up my 2017 scene-files in 2018. They simply wont open. Error :

file -import -type "mayaBinary" -ignoreVersion -rpr "_SCENEFILE" -options "v=0;p=17;f=0" "C:/Users/D/Desktop/SCENEFILE.mb";
// File read in 0.0067 seconds. //
// File read in 0.0067 seconds. //
// Error: line 0: Error reading file. // 

The file works fine in 2017. 

Anyone having the same issue? 

Regards/Carl-michael

[sean.heasley]

Hi @carlmichaelk

Can you check to see if the file is corrupted?

Also can you attach the scene file here or via dropbox/google drive so I can take a look at it?

[carlmichaelk]

Hi @sean.heasley

The file is not corrupted and works fine in 2017, as does all the incremental saves of it. I cant send you the file due to confidentiality of its content. 

Sorry.

/C

[sean.heasley]

Hi @carlmichaelk

Its fine if its confidential, you can send it to me in a private message. We keep all user files on a strict confidential basis.

[mspeer]

Hi!

1. Try saving as .ma

If this doesn't work:

2. Remove some objects from the scene and try again, (repeat this step until it works to find the problem).

If the scene without confidential content still shows the problem, please upload the scene-file.

[Anonymous]

If you have nothing better to do, you could write a script that does the exporting to ".ma" after deleting one object at a time.

Delete one object. Export to ".ma" and add the name of the deleted item to the scene name.

Loop.

Then waste some more time opening each one of the ".ma" files in 2018 to "beta test" a "released and paid for software package".

I am sure your client won't mind waiting if you reduce your rates a little bit.

You may end up not making any money and wasting lots of time but we all do this because we love "making art" in Maya.

[sean.heasley]

Hi @carlmichaelk just checking in, did any of the above posts help?

If not you can still send the file to me in a pm and it will be kept confidential 🙂

[carlmichaelk]

Hi,

I do think that there is something with the new way that Maya 2018 reads geometry, due to the fact that the file complains about not being able to save in MA because Geometry-error . But the scenefile can not be repaired with Mesh-cleanup. 

You cant have any of my Geo or scene files. All is heavily protected bu confidentiallity. We have a support agreement through Volvo Cars, and that might be our channel if this issue persists. 

I just thougth it would be good to raise the problem. 

For now we will just keep the project in 2017, as we dont have time to work on this. 

Regards. C

[mspeer]

Hi!

Thanks for the details like "not to be able to save as .ma" (never seen this).

I also recognized a difference between 2017 update 4  and Maya 2018, but this seemed to be related to some history nodes (and Maya 2018 does a better job here than Maya 2017).

If you want to test this again make sure there is no history on the objects.

If you would need more help on this, also outside the forum, just ask.

Anyway i don't recommend to change Maya Version during a project, so staying with Maya 2017 will be the best (and less time-consuming) solution.

[Anonymous]

This may be completely a shot in the dark, but is your file bigger than 2GB? I remember in version 2015, or something, I could not save a scene that was bigger than 2GB. Maya would stop at exactly 2GB and I had to save in .ma (which was brutally slow over the network and a complete waste of time, as working with Maya usually is). I am pretty sure they fixed that limitation soon after that. But because with Maya you never know, as fixed bugs get broken and reintroduced to force customer to keep upgrading, you might want to check that. Perhaps Maya 2018 cannot save in .mb files larger than 2GB. Perhaps you have to pay extra for that.

[dustjoit.dj]

i have same problem. maya 2018 totally corrupt mesh and uv all of my safe file and all increment safe files then i try t safe it in .ma file.(its look like a mess of vertex then iam try to reopen this file ) .mb seems to work fine for now

[sean.heasley]

Hi @dustjoit.dj

Have you tried any of the steps mentioned above?

[dustjoit.dj]

yes,if you mean delete history nodes and parts of scene, i have one object in scene and competently deleted history even do optimize scene just to be sure.and it doesn't work. the problem is coming randomly. as long as i am working  all looks fine, problem comes after restarting and reopening .ma 

[sean.heasley]

Hi @dustjoit.dj

Can you attach the scene file here or via dropbox/google drive so I can take a look at it?

[john.paul.giancarlo]

Hello, did you try saving them as *.ma ?

MB should work but just in case try to convert them to *.ma using 2017 and retry in 2018, you could also try to import them! , if this does not work either your scenes could be corrupted !  😞 . 

lets us know how you get on with this !  🙂

[sean.heasley]

Hi @carlmichaelk

I'm just checking in to see if you need more help with this. Did the suggestions that everyone provided above work for you?

If so, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

[MannaTheBerserk]

Same problem here, and yes, I have already tried all the steps above even before reading this thread.

Result: saving in .ma from previous Maya version and opening with 2018 does indeed work.

Though this should not be the normal way to do it. Maya 2018 should be able to read mb files just fine, which it doesn't.

Another thing I would like to point out: if the file is smaller thant 2 GB Maya 2018 can read it. If it is bigger than 2 GB it just can't.

[MannaTheBerserk]

So, I tested the issue again: saved from Maya 2016.5 in .ma. Opened in Maya 2018 with no problems at all (apart from it taking ages of course). Saved from Maya 2018 in .mb.

I have then quit Maya. Opened the software again (2018), tried to open the .mb file (previously saved with Maya 2018 itself), and nothing. Maya 2018 definitely has problems with .mb files over 2 GB.

This is serious.

[mspeer]

Hi!

I don't have Maya files with more than 2GB, so i can't test this, but you should

report this problem (bug?) to Autodesk.
Help -> Speak Back -> Report a Problem

[MannaTheBerserk]

I will definitely do that, thank you.