iTorque2d - Tilemap editing eating memory up?
by Christopher Asche · in Technical Issues · 01/21/2012 (12:46 pm) · 5 replies
Ok so I think I've hit upon a bit of an annoying bug in iT2D. This project I'm playing around with is using a tilemap that's 30x20 tiles, 32pixels each. 600 tiles. I noticed as I go to edit a tilemap using this tileset, every time I click to bring up the tile sheet and select my next tile, it takes longer and longer to load. It started off at maybe a second to load, and then after only playing about 10 different tiles, I'm left waiting 15-20 seconds just for the sprite sheet to pop up.
To help remedy the issue I simply went back and cleaned up my tileset a lot (was really only prototyping with it) and cut the size down to 340 tiles. Initially it's a lot faster, but still after time it just gradually bogs down until I might as well go get a coffee between placing a single tile. I'm assuming that this is an editor issue and that iT2D is simply not letting go of the memory it uses to load the tileset, and instead just loads it into memory again and again? Memory leak?
So essentially does anyone know a work around for this? (preferably something simple) or a fix? I'm not exactly happy to run into something like this, at this early of the stage of development. It cripples my ability to use tilemaps.
Upon shutting down iT2d and reloading it I regain my speed, but it's not very user-friendly for me to have to shutdown and reload my project every couple of minutes, you know?
I am running iT2D 1.5 and developing on a Mac if that's useful information.
To help remedy the issue I simply went back and cleaned up my tileset a lot (was really only prototyping with it) and cut the size down to 340 tiles. Initially it's a lot faster, but still after time it just gradually bogs down until I might as well go get a coffee between placing a single tile. I'm assuming that this is an editor issue and that iT2D is simply not letting go of the memory it uses to load the tileset, and instead just loads it into memory again and again? Memory leak?
So essentially does anyone know a work around for this? (preferably something simple) or a fix? I'm not exactly happy to run into something like this, at this early of the stage of development. It cripples my ability to use tilemaps.
Upon shutting down iT2d and reloading it I regain my speed, but it's not very user-friendly for me to have to shutdown and reload my project every couple of minutes, you know?
I am running iT2D 1.5 and developing on a Mac if that's useful information.
About the author
#2
1. Using Windows 7
2. 2-3 different image maps
01/23/2012 (3:01 pm)
Hey Michael, I can attest to this. I've had this issue multiple times with TGB as well although I'm running an older version of TGB v1.7.5. I haven't made a case by case scenario so I'm not sure about what is actually triggering it, but when it was happening to me, I had 3 different layers of tiles and as I was midway through my second one it started bogging down and doing exactly what Christopher described above. I've since moved to another program to make the tile layers and then save the entire picture to a file which I can then import into TGB as an ImageMap.1. Using Windows 7
2. 2-3 different image maps
#3
As for my Mac OS version, I'm on 10.6.8. I believe the trendy Mac people are calling it Snow Leopard.
I do plan on updating to the latest OS version (Lion) a bit later today though after I finish work. I can try it again then and see if anything changes. (Unless updating to Lion will cause some kind of issues with T2D or iT2D in which case SOMEONE STOP MEEEEEEEEeeee!) Will post an update after that.
I can't say I've tried it out on my Windows machine though. I don't have T2D on it. I've turned my Mac into a single-minded development machine.
01/23/2012 (10:19 pm)
In my case I'm only using a single imagemap. Just a little playing around/prototyping.As for my Mac OS version, I'm on 10.6.8. I believe the trendy Mac people are calling it Snow Leopard.
I do plan on updating to the latest OS version (Lion) a bit later today though after I finish work. I can try it again then and see if anything changes. (Unless updating to Lion will cause some kind of issues with T2D or iT2D in which case SOMEONE STOP MEEEEEEEEeeee!) Will post an update after that.
I can't say I've tried it out on my Windows machine though. I don't have T2D on it. I've turned my Mac into a single-minded development machine.
#4
01/24/2012 (5:38 am)
Ok running on the latest OSX Lion, and I can confirm the problem still very much exists.
Employee Michael Perry
ZombieShortbus
1. What is your OS X version?
2. How many ImageMaps are involved?
3. Have you run into this issue on Windows (if you have tried)?