Weird error...

#1

o.k. so I’ve been having this weird error happeninig to me on and off for a few weeks and I thought it might have been MB flipping out, but it’s becoming an issue now. It usually happens when when plotting data from the character to a clip or to the current take, here’s the error:

Out of memory, an allocation failed

exit ? continue anyway

then it gives the dreaded… C++ Runtime error… blah blah blah
So i’m wondering if anyone else has had this problem and might have a solution or can direct me to another resource where i can find out whats going on ? Thanks !
If it helps here are my pc specs:

Windows XP SP2
Intel Duo Core
4300 @ 1.80 GHz
2.70 GHz
2.0 GB RAM

#2

Hi Favian001,

What version of MB do U use? I can advise U to try extension 1

#3

Thanks for the help! I am using MB 7.5.1 … I’m thinking it might be the length of the data…it averages from 500 to 3000 frames…seems to have a tough time with the larger files.

#4

Hey Favian,

This is MotionBuilder’s way of saying “I’m out of memory and things may get bumpy ahead”. My suggestion would be to load up 7.5 Ext2 64bit on WinXP-64bit, on a mahcine with more than 2GB of RAM.

Cheers!

Curtis Garton

#5

Cool, thanks alot!! I thought this might have been a dead thread within a couple of days…I really appreciate this! :thumbsup:

#6

Windows caps out its memory at 2.32 GB even if you have 4GB on your machine. You can change your boot.inf file to support up to a maximum of 3GB (I’m not going to show you how because there are risks associated with changing this file!! I recommend leaving it alone)

Motion Builder has had memory leak problem and does not deal with Heap files very well for as long as I can remember, 7.5 ext1 included, I know they did a lot of optimization in 7.5 ext2 but I’ve only just started using it I can’t comment on how much it has improved.

If you have had MB and your PC on for a while try shutting everything down and restarting, you may get a little farther before it caps out again. If the problem persists try reducing the amount of takes in your scene.

One other thing, Motion Builder is essentially a game engine and does not like textures that are larger than 512x512. textures that are 1024x1024 will impact performance, try reducing there size or removing them completely. You likely won’t be rendering in MB and your exclucive merge through your FBX import plugin into you 3d package will work for bringing them back.

Hope that helps.

#7

yes this is very helpful thanks alot for taking the time to answer my questions. unfortunately we will be doing some realtime rendering so i have to have the highest quality texture maps as possible. thanks again…all of you guys rock!! :buttrock:

#8

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.