Texturemanagement?
Posted: Thu Oct 21, 2010 9:28 pm
Hi there,
I recently started to work with Irrlicht, and there is one thing I'm wondering about for quite some time now: Texturemanagement. My problem is best described with a basic game example:
You are loading a level for your game, with a ton of different textures (manually loaded via getTexture()). After you have finished the level, you load another level, with a completely different set of textures.
So, what do you do with the textures loaded from the first level? The API reference states you are not supposed to "drop" the textures, but I don't think Irrlicht "deloads" them by itself does it? Thinking in big dimensions (or ressource-saving for that matter), this means you would be wasting sooner or later a lot of memory space, which could be critical in big games.
So, what am I supposed to do with my "left-over-textures"?
So long,
Kernle
I recently started to work with Irrlicht, and there is one thing I'm wondering about for quite some time now: Texturemanagement. My problem is best described with a basic game example:
You are loading a level for your game, with a ton of different textures (manually loaded via getTexture()). After you have finished the level, you load another level, with a completely different set of textures.
So, what do you do with the textures loaded from the first level? The API reference states you are not supposed to "drop" the textures, but I don't think Irrlicht "deloads" them by itself does it? Thinking in big dimensions (or ressource-saving for that matter), this means you would be wasting sooner or later a lot of memory space, which could be critical in big games.
So, what am I supposed to do with my "left-over-textures"?
So long,
Kernle