The thing about the normal MMF array is that it doesn't seem to care if you exceed its preset dimensions... and nobody really cares if you use less of the array than its dimensions. So it's pretty dynamic already.
Is it the "Dynamic Array" object that's crashing, then?
Go Moon!
Assault Andy Administrator
I make other people create vaporware
Registered 29/07/2002
Points 5686
7th August, 2008 at 10:28:53 -
The MMF array is already dynamic as Fifth mentioned. You can exceed the limits you set in its properties and it just extends the array.
Yes, it is the Dynamic Array which is causing the crash.
I'm slightly astounded. I just tried using points that should have been way outside the bounds of the array (normal array) and it worked fine, like you said. I may still use the dynamic array object, as it has more options for manipulating arrays, but at least it means it'll be possible to export normal arrays (with a few fastloops).
This is for my array editor project, so it was important that it could create arrays of any size. If it weren't possible to exceed the preset dimensions, it would mean having to use a huge array all the time, which would take up far too much disk space and memory (just incase you actually needed the extra array space).
I'm a little curious - what's the point of setting array dimensions at all? Are they just a relic from MMF1? Did it even matter if you exceeded them then?
Anyway, Huge thankyou Fifth
and Assault Andy
Edited by the Author.
n/a
Assault Andy Administrator
I make other people create vaporware
Registered 29/07/2002
Points 5686
7th August, 2008 at 10:47:31 -
I'm not quite sure, I came across the array resizing in MMF 1.5, so it was still present then. I have no idea where it came from!
HAHAHA awhile back i tried making an array with dimensions 10,000x10,000 and a warning popped up saying "THAT ARRAY WOULD CONSUME MORE THAN 256gb OF MEMORY!" and automatically set it to 10,000x1000 lol.