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

Back to it....

Sign in to follow this  


Take 2...

Haven't updated the journal in a few days. Spent a while chasing down a bug that arose as a result of possible overlap in my octtree nodes. Something was defined as inside the node if it's centre position was => minimum and <= maximum for x, y and z. This led to the uncommon (but still possible) situation where a position was on the maximum for one side of a node and the minimum for it's adjacent node, etc. This resulted in some references to objects floating around and not being removed when they should be.

I switched this to the centre position needing to be => minimum and < maximum so now it works fine.

I should be able to get down-and-dirty with my algorithm change now. Yay!
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!