Irrlicht Engine

have you looked at the other angles (x,z) it generates? Euler angles aren't great at defining a rotation; different values can give the same result. For example, the (0,180,0) could be done with (180,0,180) too. Also they will be looped within [0,360), hence the 360->~0.
For the 250 and 140 angles I ...

soundsnap.com has good quality stuff, but I think new accounts don't get free downloads any more.

problem case; semi-transparent black object (maybe a screen fade) in front of an additive white object (maybe a particle);
the background additive white object will not render because it sees that an object is already in front of it.
Any render order will have problems when transparency is involved ...

From what I know, this isn't possible. You *could* create a new scenenode object and (as you mentioned) change the render function to set the material's values before rendering, but really you might as well have separate materials for each object. There isn't a huge amount of overhead from doing so ...

most games do this in some kind of options page, which has very few objects to re-load. I don't know whether they work by re-creating the scene or not, but it's certainly possible to mimic this behaviour by deleting & re-making the device. For simple scenes the delay will be minimal.
RTTs are well ...

Edwart; the class uses 2 possible methods to check sun visibility. Set the quality to CRUDE and it will do bounding-box checks in the direction of the sun. NORMAL (default) will check the colour at the sun. If it's above 0.9 (i.e ~240) in brightness, the sun is visible, otherwise not.
Both have ...

directional light is what you're looking for, and as Lonesome Ducky pointed out, setting it as a child of the camera will make it behave nicely (as lights usually do in 3d editing programs) if not entirely naturally. You'll also want to play with the angle it's at relative to the camera to get a ...

is probably the culprit here - I don't know for sure, but it would make sense that the viewport is setting the world matrix. Try saving the viewport to a rect just before calling this it and setting it back after.

node->render() will apply transformations if used after a smgr->drawAll(); call, because the transformations will still be in effect.
You're right about it rendering some parts out-of-order, which could be a problem, but for simple shapes it will usually be ok (back face culling will prevent most ...

disable z-testing in the material and render the nodes manually after the scene is drawn, with node->render( );
You can also make the objects invisible so that they aren't rendered twice.

Post Processing; I'm a-working on it! :P
What I have so far is quite light-weight, and I'm working on having it auto-optimise (for speed and memory usage). Hitting a few hurdles tho so it's slow progress.
A few others seem to be working on it too. Will be interesting to see the variety of ...

just clear the back buffer with a transparent colour; SColor( 0u, 0u, 0u, 0u ); and draw with EMT_TRANSPARENT_ALPHA_CHANNEL

Each OS will have a different button mapping, this is an annoyance you have to live with, because of the various drivers. For example, while Andrei is right that the centre button is inaccessible to Windows, both Linux and OSX report it. They will also report the buttons & axes in a different order ...

the resolution of the markers is dependant on the texture size you render to, and that is limited by the hardware. You usually can't get away with more than 4096x4096, which will be low quality on large terrains. (also I wouldn't recommend using such a big texture for such a small part of the game ...

Although that would be possible, it will only work for a limited number of units and be quite slow. Instead you should use flat shapes just above the terrain for selection rings - create a flat surface for each unit and texture it with a ring with transparent centre and corners.
By making it part of ...