Jump to content
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views


Sign in to follow this  


From the Previous Entry
And, I think if you unload a set currently being used shit will break.

Yep! I think I'll just remove the ability to unload loaded component sets for now, because there isn't any easy way to detect whether or not a specific component is being used. The sets themselves take up barely any space in memory anyway, so I doubt this is a big issue.

The bigger issue is that the texture is still loaded even after the component set is unloaded... that is an issue.

Also, I don't know why it did that mipmapping when it broke. As this is the only time it occurs, I'm figuring its just an artifact of passing garbage values to the renderer. I think.

UPDATE: Fixed the textures-not-unloading bug. Apparently I had written a function, ComponentSet::_freeTextures but forgot to actually write a destructor. DUR DUR.
Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!