Just tried to send it, and it's a 0k zip file, so Gmail won't let me.

-Paul

Hi Paul, how large of an array are you trying to make?

Is it possible for you to send me the 3DM file as well so I can try to repeat the problem over here?

While you are in the middle of moving your mouse around and adjusting options in the array tools, MoI only draws a lightweight proxy object on the screen to give faster feedback. It's only when you are completing the array that the full object copies are being made. So if you are overloading things by making a large number of copies of a fairly complex object, then that's the point where you will run into problems with consuming all available memory.

- Michael

Hi Paul,

> Just tried to send it, and it's a 0k zip file,
> so Gmail won't let me.

Most likely that means that you did run out of memory - it takes some amount of memory in order to generate the crash dump file.

Can you send me the 3DM file so that I can try to repeat the problem over here?

Can you also tell me what particular array tool you are using and what number of copies you are trying to make?

But if the problem is that you are running out of memory, then the solution is to not make so many copies to avoid that from happening.

- Michael

Hi Paul, thanks for sending the file. Yeah you’re just running out of memory here – 100 copies is too many to make of a NURBS object unless it is a bit lighter than that – having the little fillets on the object like you’ve got in this case adds a lot to the object’s data size.

Doing the array in your rendering program instead is probably a better bet.

Also if you reduce the display mesh density in MoI to make it a bit rougher that can help to reduce memory consumption, see here for which settings to adjust for that:
http://moi3d.com/forum/index.php?webtag=MOI&msg=4643.4

Thanks,
- Michael