Irrlicht Engine

Just wanted to update you real quick, Xterm, that I've changed the code up a bit for my own use so that this class no longer has to live inside of irr::scene and can be compiled __entirely__ outside of Irrlicht. My own engine is built on top of Irrlicht, and makes no modifications to Irrlicht's core ...

Klasker provided the source for me and I can confirm that the code build and works on Linux w/out a hitch using -W and -Wall. My vote is for it to be tested a bit and added to Irrlicht TRUNK.

(Using Dapper Drake, GCC4, and Cal3D from apt)

OMG! DRAGON WARRIOR! Nice work...

I remember that game being impossible! I also remember trying to find some mythical gold slime or something...

Anyways--because that's such a cool rendition of DW, I put a copy of that video on my own website so you don't have to go through that horrible dance on ...

I just wanted to post real quick and say I really love this camera class. Nice work! I had been using v1 for a while and just noticed you've made some nice changes. :)

I wonder if--with a little adherance to coding style--if this camera could be added into Irrlicht CVS HEAD? It's certainly ...

The answer is to call XAutoRepeatOff using the Display pointer Irrlicht sets up in the IrrlichtDevice. The question now is--what's the best way to do that? :/

After a little more investigation on my part it turns out that this is a "feature" of your window manager; X is actually propagating events exactly as I'm interpreting them in irrlicht. Apparently, when you hold down a key your window manager simulates you pressing it over and over at some user ...

I'm pretty sure that what I'm experiencing isn't the "norm" in terms of what is supposed to be happening and what is actually happening. I'm using Ubuntu Breezy, Xorg 6.8.2, a 2.6.15.2 kernel and the latest version of Irrlicht compiled from source.

If I press and hold a certain key I get a constant ...

Okay, well, now that I've shown off my obvious newbness, what is the standard workaround? Create a bunch of lights and only "enable" the ones that are within "range" as you move through your scene or do usually end up having a few large white lights and just being creative w/ materials? I know there ...

My video card reports being able to support ~3300 dynamic lights. However, after adding my 8th light, no other lights from then on are shown (though smgr->getDynamicLights() reports the right amount). I've been searching through the source and the forums (which is mad more difficult by the fact that ...

I just had a quick question about style. Let's say I want to write a custom Camera scene node, Foobar. Obviously I can't do:


class Foobar : public scene::ICameraSceneNode {
// ...stuff...
};


...without also defining every pure virtual function (which is just impractical). What I'd like to do ...