Irrlicht Engine

As long as you have any questions/ideas/whatever about Irrlicht you are always welcome. Also it's motivating for me if people still show up once in a while ;-)

You call setCurrentFrame, OnAnimate and then getMesh. The way that animation system works the original mesh is not really kept (at least not directly, it's still there in some other representation via the keys) and instead the mesh is modified each frame.

ogl-es is the special repository for Android. But it hasn't been tested with newer API's by me in a while. I try to keep it up-to-date, but the build system it uses is pretty outdated by now. Also I never used it on Windows (as I did all my Android development on Linux), so I'm even less familiar ...

Phew... bit tricky. AI is partly right. First - make sure you go over the lightscenenode and not the SLight structure when setting those (as mentioned there those are not meant to be written to directly).

And then yes - ILightSceneNode::setRadius indeed sets the attenuation (and also the radius ...

I'm not very good at this, so I hope I don't tell anythign wrong: The normal is still in modelspace (no rotations/movement/scaling applied yet). It kinda depends on what you do with it but mostly you want it in view-space (so with camera as origin as your coordinate system). As long as the model is ...

I have to admit that I still use the outdated gl_Vertex, gl_Normal, gl_Color, gl_MultiTexCoord[x]. My trick is to use #version 430 compatibility instead of core, then those are still available. Thought I probably should switch at some point. Anyway - the alternative layout looks good to me on first ...

shadowVolume is a node you can load. Maybe create one in code and write a scene - then you can see how it looks like.

You have to set the light data for your node, so assuming spotlight is an ILightSceneNode it's something like:

spotlight->getLightData().Type = irr::video::ELT_POINT;
spotlight->getLightData().OuterCone = 90.f;
spotlight->getLightData().Falloff = 1.f;


Also make sure your target material hasn't ...

I thought a bit more about it this morning and get the reason for insert before/after separate now (otherwise once you clear out all elements after a non-moving element you can't move any back in again unless start/end of list also have flags).

edit: Maybe having "sticky" sides might be more ...

Thanks! And sorry for still not applying it. I wanted to do some changes back then. First I thought amount of flags can be reduced by having a flag like "allow_drop" instead of 2 for insert before/after. So as soon as one node allows it you can drop around it. And other thing was that the line is ...

Nice suprise to suddenly see a new game made with Irrlicht :-) Gratulations!

If those in the zip don't work ... that's strange. Usually only happens if D3D9 is not installed at all on the system. Don't really remember if it was installed back then by default.

Do you get the same error when you run bin\Win32-VisualStudio\10.Shaders.exe from the official irrlicht1.8.5.zip? (with options: D3D9/high level/no Cg)

And how did you build this? You checked out svn trunk I assume. But which compiler? Code::Blocks or native gcc? Or some Visual Studio version? I ...

I haven't worked with SteamAPI yet. But maybe you can use SExposedVideoData is some way to set the handle later? Check the Win32Window example.

Render textures? You mean render target textures (in which case - why?) or just the usual textures?
Anyway, no immediate idea - it's usually around bytes per pixel times resolution. Anything beyond that I'd need an example to see what's going on.