I assumed that it would be in poor form to have every single object in need of collision detection on a frame-by-frame basis to have collision tests performed against every object in the scene aside from itself I figured that now would be the time to add some form of spatial partitioning to my XNA engine/library/framework (Rawr).
With that in mind I looked around for some articles on writing an octree component and stumbled upon a really rad demo by Fabio Policarpo. I then adapted that to my codebase, edited the code as I, in my infinite ignorance, saw fit to do, and then added some rudimentary rendering functionality to the octree to provide what I assume will be a much-needed graphical visualization (in the future).
Anyway, it looks like a squishy death array of lasers.
For the record, working on Asplode! was so much easier. Anyone who says that 2D is harder than 3D is a dirty, blasphemous liar. No one says that, though. Because they are smarter than me. Not that I said that either. I think.
2 Comments
I do have to agree that saying 2d is harder than 3d is blasphemy but with engines like Irrlicht I think that will change soon.
Well, 3D will always be more difficult than 2D. Engines just make everything a little bit easier.
I had a hard time finding a decent engine for the kinds of projects I like to make when I was done with Asplode! and looking to do something new. A number of otherwise decent engines seem to suffer from a pretty hardcore lack of documentation while others appeal to a certain scripting-heavy mindset (which isn’t bad, but I don’t want to be forced to take that route).