OK so, this will take some explaining.
As you may or may not know, in bgt, you can have arrays with up to 4 dimensions. That in itself is fine.
What I'm curious to know is if bgt alone is really terrible when resizing anything above two dimensions?
This is even more noticeable when using string based arrays.
Are other languages in general really bad at this or is bgt just really horrible with resizing arrays? In truth, I'm going to say it's probably bgt, but I don't have enough experience with anything other than bgt to say.
A bit of background. I am attempting to use arrays for a map system which includes full 3d support.
The most I have been able to successfully resize this array to was about 90 elements before RAM usage skyrocketed, or bgt produced an out of memory error, and usually both at the same time. If I did the maths, that's 90 per dimension, right?
So, 90 and 90 and 90, gives me 270 units to play with. That might seem like a lot, though in reality, it gives me 90 up, and 90 for playing with for the rest of the 2d navigation.
I know a lot of bgt devs are going to say, hey, use dictionaries! But in truth those are designed extremely poorly.
So much so that referencing them causes concern for the (very real) possibility of crashes.
And when a bgt game crashes, it often crashes spectacularly.
Can anyone else confirm if this is just an issue of bgt, and most other programming languages don't do this and it is time for me to move on for real this time?
Thanks for reading if you got this far.