Irrlicht Engine

Yeah, as you said. The deferred removal was made in order to not require additional driver access from the meshes, which are completely unaware of video driver stuff. I would have expected that lightvolumen is derived from IMeshscenenode and give access such that the hardware buffer can be explicitl...

Ah cool, I always wondered what it would take to support the extended WM hints. Is there a patch download link, or can you upload the patch to the tracker?

Didn't we fix this issue in the old version of OGL calls by using reference counting? Has been fixed at least once or twice for what I know, so please use the "proven solution".

Well, this image is still 51x42 px, so not even near some power-of-two. What size is the original one you use?

The problem with widget libs is often that they use their own set of flags to create the windows. And to setup OpenGL the way they need it. This can interfere with Irrlicht's requirements. But it should be possible in general. sometimes the tweaks needed are just a little more involved.

If you could dig into the sources and see if you can improve the shader handling it would be highly appreciated. This shader support was developed by only one guy who seems to have left quite some time ago (as many from the original team), so many parts of the engine are somewhat abandoned and we ne...

Yes, Irrlicht works with OpenGL on Windows Also, we have example 14, which shows how to integrate several windows with all renderers under Windows, i.e. with manually created WinAPI windows. It's part of your Irrlicht SDK.

So what's the difference to the SDL device that we already offer within Irrlicht? It should already provide all those things and should hopefully work with android as well!?

Well, depends on the cube you use I'd say. If it uses (0..1) texture coords it won't tile - why should it. But if it creates a new cube with scaled coords it will definitely tile the textures. IN the first case you could still use texture matrices (or manipulate the coords manually). But textures ar...

Just fyi, the tracker is here: http://sourceforge.net/p/irrlicht/patches/

Example 6 has an example of how to render sw cursors, just as hendu suggests.

Yeah, I know, and it should probably be the same for all systems. But I remember that several problems popped up when I tried it last time. But we will try to keep it in mind and hopefully solve it sometimes.

MAybe try to switch ton randr instead of the vidmode86 approach

That should be also documented in the drawMeshBuffer method. Basically all functions named drawSomething and doing 3d rendering use this same scheme.
Also, adding the meshbuffer to a mesh and adding that to the scene would work and makes many things much simpler.

Rendering them as separate sprites is within reach for the engine and a faster graphics card. But due to the many single draw calls it would be better to prepare some batched buffer or some textured plane to place the lights.