Incessant crashing in story mode

[GiantG]

I cannot confirm this.
Story Workflow is pretty stable.

Maybe check your Hardware/Driver config. (RAM Test etc...)

[Qslugs]

We've done ram testing previously, the issue has been something that is repeatable on multiple machines in the past 7.5 and 2010.

We are running 32 bit XP sp3, Processors are dual Xeon 2.53 ghz http://ark.intel.com/Product.aspx?id=33927

Ram is 3 gigs, and the task manager never says that the ram is being exceeded. Hard drives are in a raid configuration with more than enough space.

Graphics card is Quadro FX1700 with 512 mb ram.

The crash report started that the computer had 768 megs free at time of crash.

Motionbuilder 2010 works fine other than the story mode issues.

[GiantG]

With RAM Test i don't mean the capacity. Do an ECC Error check.

Check your Drivers as well. Install newest service packs and so on...

http://www.heise.de/software/download/ct_ramtest/3666

[Pedrotheartist]

I have no problems working in Story mode in 2009 or 2010... I haven't tried 2011

[eroston]

Hey Mike,

I've found the story track to be pretty unstable. It's incredibly useful for a number of tasks but it can bite you if you depend on it too much. I often find myself doing a lot of workarounds to get past the crashing.

What sort of editing are you using the story tool for?

[mlager8]

We were having this problem to in MB 2009, even though it states there is enough RAM upgrading fixed the problem. We went from 3 gigs to 8 gigs and the same scene that was crashing story mode with 1 key now works perfectly.

[Headless]

Turning ghosting on or off in the Story window has been my number one cause of crashes for the last 4 years (across multiple versions of Motionbuilder).

To my knowledge it's an issue with it running out of memory. You might need to look at both physical memory and virtual memory, cause I always seem to have enough physical memory free but my machine is constantly paging stuff out when I switch between programs.

Oh and yes, I do lots of editing in the Story window, but I'm usually dealing with a single character at a time and short takes. Interested to hear how intensive your scene is.

[Qslugs]

Scene is not all that intensive. Chopping up a single take into multipls small takes. I am trimming down the animation and centering the animation for other people to edit. Take(s) might be 1000-2000 frames in length. Character is nothing out of the ordinary, a standard biped character.

One way I have gotten around my issue is to delete the track instead of muting it right after plotting. Playing around with turning ghosting on and off causes MB to crash, as does muting and un muting the track after I have plotted it.

I did a thorough ram test through the dell diagnostic utility and nothing turned up. Even did advanced ram testing.

Unfortunately project isnt done yet, can't upgrade :(

[DruG]

I`m having problems with Story when I try to slide a key outside of time range of a clip (you know, "A" turned on). I have 100% crash chance every time :)

But nothing with plotting.

I`ve heard that MB2011 is more stable, since Story was rewritten. My collegue from work said once that he did some tests and that it confirmed that. I have to try myself tho.

[ErikSvensson]

I got to say that every new release of mobu has gotten worse, that's why I stick to 7.5 ext. 2, definitly the best release out there. Story in 2009-2010 always crashed upon me, we don't have 2011 yet so I havent tried that. It also seems like mobu suffers from the Autodesk syndrome of adding a new release every ½ year without any major features, that's another reason not to upgrade unless you badly need to. :beer:

Erik

[CGTalk Moderation]

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.