Ah-ha!
That explains why I had such a tough time of it.
It's some kind of weird memory allocation bug inherent in T2D, I think. The system crashes if I dispose of these menu tiles within a short time span, but works fine if I dispose of them one every 1/100 second. The thing is, I don't think this isn't an error on my side: if I dispose of them all simultaneously ten seconds after they're clicked on, rather than instantly, I still get the error. So it's not like I'm trying to access deallocated memory. (Even if I was, I'm using a function of theirs which is supposed to inherently protect me from that.)
Geez. What a nightmare. This must be a bug specific to the newest version, since I've never had this kind of problem with the older versions. It's actually pretty standard fare in many of my games. I'll have to be careful of this in the future.
Honestly, the "slow deallocation" actually looks kind of snappy. All's well that ends well.
Now I'm back on track. Bleargh, what a waste of a week.
It's some kind of weird memory allocation bug inherent in T2D, I think. The system crashes if I dispose of these menu tiles within a short time span, but works fine if I dispose of them one every 1/100 second. The thing is, I don't think this isn't an error on my side: if I dispose of them all simultaneously ten seconds after they're clicked on, rather than instantly, I still get the error. So it's not like I'm trying to access deallocated memory. (Even if I was, I'm using a function of theirs which is supposed to inherently protect me from that.)
Geez. What a nightmare. This must be a bug specific to the newest version, since I've never had this kind of problem with the older versions. It's actually pretty standard fare in many of my games. I'll have to be careful of this in the future.
Honestly, the "slow deallocation" actually looks kind of snappy. All's well that ends well.
Now I'm back on track. Bleargh, what a waste of a week.
posted by Craig Perko at 11:59 AM
0 Comments:
Post a Comment
<< Home