RaptureEngine

[ppcStudios]

[ruis]

[Conan]

[ppcStudios]

[ppcStudios]

I finally came up with an object subsystem that I'm happy with so I thought I'd post a screenshot of a nice little oasis consisting of several different objects - various palm trees and cactii.

I'm going to spend the next couple of days tuning the rendering loops, putting together some basic developer documentation and making sure everything builds into a library correctly. I'll then package it all up and make it available for evaluation. Obviously not all of the features are implemented yet, but its a solid foundation to build on.

[Conan]

[ppcStudios]

[Conan]

[ppcStudios]

[Guest]

[ppcStudios]

[ppcStudios]

I thought I'd post another screenshot showing how easy it is to drop in an animated object. Here's 4 jumping fish animations that took a couple minutes to drop into the demo. The animation is 14 frames in length, with 40ms between frames, and each of the animated objects is started at a different frame to provide some randomness to the scene.



edit: you may notice the drop in framerate - this is only due to the fact that I was pressing the screenshot button repeatedly to get an image showing all the fish, not due to added animations.

[Conan]

very nice. I don't have to think hard to find 40 uses for this. Now add in the fly that the fish is jumping for & I'll be really impressed (only kidding)

[ppcStudios]

I was doing some code cleanup and thought I would post this after making some changes. This image demonstrates how the various clippers can be arranged to make life easier for the developer. In this case, the main RaptureEngine viewport is clipping both the terrain and all of the object sprites, while each sprite handler has its own clipper (in this case, the main buttons and the tool palettes). This eliminates considerable coding headaches for the developer - only one line of code is required to setup each viewport. Do it once and forget about it.

[mlepage]

How do you make all the nice graphics? (Terrain, trees, etc.)