I would imagine freeing a texture, will get rid of it from memory and remove it from the entity. However, if it's not getting rid of it from the entity, then it still exists and there is no point in freeing it :o)
Another point with freeing resources i have found. For instance, if i copy entity CUBE mesh. Then i free the cube mesh, i would need to free every other instance of that to regain any memory. IE. copied entities don't take anymore memory up, and by freeing the entity that was used for copying, it still doesn't free the memory.
Any, that's besides the point. If you free a texture it won't exist anymore. Pretty pointless unless you don't want to use that texture anymore.
Regarding brushes, i'm not entirely sure whether blitz will retain the texture. I would imagine it would destroy all properties coupled with the brush.
Only reason to free a brush i have found, is after GetSurfaceBrush() and GetBrushTexture(). These commands create new brushes and textures, and should be freed when your finished working with them. The originals still exist though, it's just a way of accessing them.
|