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

The real update I was talking about

Sign in to follow this  


One good thing about working on about juggling a bunch of different projects at once is that it gives you the chance to get some distance between you and the code. For example, today I went back to dodecahellspawn and hopefully found the problem with the old solver: I had a < when I needed a <=.

Of course, I had already ripped out the entire solver and rewrote it from scratch, but it's always good to know how you've screwed up.
Sign in to follow this  


Recommended Comments

Nope. Conditional trip that caused it to rotate left instead of right in certain instances in the aesthetic reductions pass. That particular segment of code operates at a high enough level that there's no room for a memory access error.

Share this comment

Link to comment

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!