The tutorial pipe-biped-plotted.fbx file will crash motionbuilder 2009 when imported to Maya 2009 and then exported back from maya to motionbuilder 2009. Motionbuilder crashes when attempting to a standard save of the project or save as. Note 1. nothing was changed in the pipe-biped-plotted.fbx tutor file provided from Autodesk.  Note 2. using standard maya 2009.3 plug ithat came with Maya 2009 and also got the same crash in motionbuilder after downloading the 2009.3 FBX from Autodesk for maya 2009 win32 from the internet.

Found out that this crash only happens when using import. The FBX plugin import does not crash and allows motionbuilder to save or saveas.

For me, Motionbuilder crashes every time I exit the program. The error box says “motionbuilder 2009 has stopped working”.
Probably it’s windows Vista. Anyone else has a crash each time when exiting the program?

I’m getting very frequent crashes at the moment during my working day, incredibly frustrating.  I get the ‘Just in time’ debug prompt, though can still rotate viewports and even save the scene (though whether that is a good idea I am not so sure!  Then as soon as you click ok on the prompt, motionbuilder crashes out for real, nice!!  You have to laugh.

I thought I’d go back to 7.5 with the same file, been working a while now and no crash!  Hmm, how much did this ‘upgrade’ cost us, lol.

chrisbull 20 May 2009 10:11 PM

I’m getting very frequent crashes at the moment during my working day, incredibly frustrating.  I get the ‘Just in time’ debug prompt, though can still rotate viewports and even save the scene (though whether that is a good idea I am not so sure!  Then as soon as you click ok on the prompt, motionbuilder crashes out for real, nice!!  You have to laugh.


I thought I’d go back to 7.5 with the same file, been working a while now and no crash!  Hmm, how much did this ‘upgrade’ cost us, lol.

Yes I have motionbuilder 2010 running on a relativity cheap new quadcore with a 516Mb nvidia card 64bit win 7. The comp has a terra of head room (no work files, they are on an extern)and the app runs like a champ! Tried it on my weekend laptop which is older with a half as powerful card and it chugs like a nancy :) plus it crashes at the slightest provocation.

Trying to fix this I notice there are very few crash complaints if one googles. The big difference in performance would suggest mb has taken advantage of new tek in this release, hence the hiccup with old crappy hardware. I am going to do exactly as you did and switch the older machine back to the previous mb version, that should fix it!

Max 2010 has the same issues, 32 bit forget it.

This is just my impression but I feel mb likes a quick processor, big headroom and a specified card. Lets face it the newest apps all do, except zbrush which runs on a calculator.

Hopes this helps.
Cheers

PS what a bloody amazing app mb is.