Irrlicht Engine

The project wasn't quite setup right, here are the details to get things working: click here.

Hmm... doesn't sound like the model then...

Another thing I discovered when playing with shadows (at least using DirectX9) is that when the attenuation values for the light are set to strange values it can cause the scene to go black. A good set of values that seems to work for most cases ...

Thanks Conquistador, that works nicely! For those of you who tend to forget things, like me, don't forget to register the event receiver in your createDevice call.

One thing that is different that I just noticed is that I'm using DirectX9, and not OpenGl.

Hey Sudi,

Well, I have stencil shadows working and the code looks similar to yours.

Maybe it's the model? What about the surface that is 'catching' the shadow? Does it have enough faces to catch the light/shadow? What version of Irrlicht are you using (I'm playing with 0.14). If you want you can ...

Nice summary of keyevents. The delay no longer occurs with bool keys and I think I figured out what I originally did wrong when implementing bool keys.

The problem, I think, occured because in the wiki 'example code' after the explanation, the key checking is placed in the event handler. When I do ...

Hey Guys,

I think you need to enable the stencil buffer on your createdevice call. The fifth parameter should be set to 'true'. Hope that helps.

Hey Bitplane,

Good point regarding the GUI. Since we know when the GUI is going to be enabled then we can re-enable the previous status of the filterkeys before the GUI is loaded. I did a quick test using the bool_keys setup, but I think the 'delay' before the keyboard repeat rate still evidences ...

I've been playing with Irrlicht a bit, specifically the Movement demo. I think I figured out how to get rid of keyboard delay if anyone is interested. If I'm missing a paradigm or concept dealing with keyboard input please let me know. This, of course, will only work in Windows:

For clarity and ...

Hmm... I had the same error and adding libs didn't solve the problem. In the end I went into CSoftwareDriver.cpp and duplicated the code near the bottom:


IVideoDriver* createSoftwareDriver(const core::dimension2d<s32>& windowSize, bool fullscreen, io::IFileSystem* io, video::IImagePresenter ...

The API doc shows each namespace, class, method and so on, so don't get me wrong - it's great and part of a design document (see section 3.2 below), but what I was looking for was a more general overview how all those relate... more like sections 1, 2 and specifically 3.1 of the design specs shown ...

Hello,

Is there a design document for Irrlicht (or failing that, any kind of general overview document)? Not specifically how to compile it, run it, modify it... rather a document explaining more the conceptual or overall design.

I'm just trying to shorten the learning curve.

Hey Pazystamo,

Yes, I think that is what is happening. I was hoping that by setting the mesh's material type to EMT_LIGHTMAP that it would use the second one as a lightmap instead of simply overlaying the two. I've started looking at the my3d importer and the x importer and it looks like the my3d ...

Hi Bitplane,

Thanks very much for the reply. After some more experimentation I've discovered that I can generate 2 UV maps in Max. I can verify this by using Map Channel Info in Max. I also checked my material for the object and I have a multi/sub-object material where material 0 is the diffuse ...

Me again. So that works fine for my3d objects. Any tips on using obj or x files? They still exhibit the same behavior.