Bouncing Ninjas!

So after trying OpenGL + ODE, Irrlicht + ODE, I've finally settled on OGRE + ODE + ? for the client rendering/smoke tests.

A little history.
A little while ago, after getting the lsystem, system server, interpreter, interpreter server, and my OpenGL + ODE client all displaying lsystems that were interpreted as 3D points in space, and could be evolved (via mutations and cross-breeding), I began to run up against the limits of how much time I could put into OpenGL. So I began looking for a 3D toolkit I was happy with. OGRE is it. However, now I need to find an input system I'm happy with. OIS is not it, and SDL may be it, but the OGRE codebase has drifted ever more and accomodating OIS/CEGUI, so that's what I'm using for now. I had SDL integrated in, but pulled it.

But for now, I'm eager to get back to fixing all the bugs I've found in the other components: subtle issues with mutexes, simplifying message passing (I'm not scared of hex anymore, so I'm going to make the objects serialize themselves instead of the current mess). And I'll just be glad to see those 3D l-systems again (especially coz I can't find any screenshots to prove I did it). For now, here's some screenshots of bouncing ninjas, and 2D systems generated from a codebase that has since been pretty much re-written.

Enjoy!

Ninjas:


Trying to see how big I could make the system (something like 100K elements/spheres in this one)

Detail:

Systems with the same start state, but one has a mutation rate > 1.

Playing around with different settings:

Bouncing Ninjas Refactored!

Intro

Hello, this is my blog about my project. I noticed I kept updating the intro page, and realized one day I'd want screenshots, musings and such. So I turned to this.
Maybe I'll even get around to sketching out the design in something other than code one day, and post it ;).
For now, the current status:

Cons

• Currently broken only has some working components (servers, lsystem, some physics).And bouncing ninjas!


• Undergoing a lot of rework.


• At the very least depends on Boost, ODE.


• Client will depend on OGRE.


• Client may end up depending on GDK/SDL, but currently trying OIS instead of SDL.


• I currently don't like OIS, but I need to focus on other things.


• SDL code written but pulled out temporarily.


• Currently only works on linux. I don't have windows to do the port (but I keep it in mind).


• No Design/Overview documentation.


• Some of the design kind of sucks.

Pros

• Has had all the parts working together in the past.


• Some of the design is kind of nice.


• platform dependencies are wrapped/abstracted.


• Build system is simple and straightforward. No automake/m4 magic.


• I always kept it moving forward, albeit often slowly, with long pauses, and many rewrites, over the last few years.