<!-- Wanted to avoid copying .css to each folder, so copied default .css from doxyen in here, kicked out most stuff we don't need for examples and modified some a little bit.
Target was having a single html in each example folder which is created from the main.cpp files and needs no files besides some images below media folder.
<p>This tutorial shows how to speed up rendering by use of the OcclusionQuery feature. The usual rendering tries to avoid rendering of scene nodes by culling those nodes which are outside the visible area, the view frustum. However, this technique does not cope with occluded objects which are still in the line of sight, but occluded by some larger object between the object and the eye (camera). Occlusion queries check exactly that. The queries basically measure the number of pixels that a previous render left on the screen. Since those pixels cannot be recognized at the end of a rendering anymore, the pixel count is measured directly when rendering. Thus, one needs to render the occluder (the object in front) first. This object needs to write to the z-buffer in order to become a real occluder. Then the node is rendered and in case a z-pass happens, i.e. the pixel is written to the framebuffer, the pixel is counted in the query. The result of a query is the number of pixels which got through. One can, based on this number, judge if the scene node is visible enough to be rendered, or if the node should be removed in the next round. Also note that the number of pixels is a safe over approximation in general. The pixels might be overdrawn later on, and the GPU tries to avoid inaccuracies which could lead to false negatives in the queries.</p>
<p>As you might have recognized already, we had to render the node to get the numbers. So where's the benefit, you might say. There are several ways where occlusion queries can help. It is often a good idea to just render the bbox of the node instead of the actual mesh. This is really fast and is a safe over approximation. If you need a more exact render with the actual geometry, it's a good idea to render with just basic solid material. Avoid complex shaders and state changes through textures. There's no need while just doing the occlusion query. At least if the render is not used for the actual scene. This is the third way to optimize occlusion queries. Just check the queries every 5th or 10th frame, or even less frequent. This depends on the movement speed of the objects and camera. </p><divclass="fragment"><divclass="line"><spanclass="preprocessor">#ifdef _MSC_VER</span></div><divclass="line"><spanclass="comment">// We'll also define this to stop MSVC complaining about sprintf().</span></div><divclass="line"><spanclass="preprocessor">#define _CRT_SECURE_NO_WARNINGS</span></div><divclass="line"><spanclass="preprocessor">#pragma comment(lib, "Irrlicht.lib")</span></div><divclass="line"><spanclass="preprocessor">#endif</span></div><divclass="line"></div><divclass="line"><spanclass="preprocessor">#include <irrlicht.h></span></div><divclass="line"><spanclass="preprocessor">#include "driverChoice.h"</span></div><divclass="line"><spanclass="preprocessor">#include "exampleHelper.h"</span></div><divclass="line"></div><divclass="line"><spanclass="keyword">using namespace </span>irr;</div></div><!-- fragment --><p> We need keyboard input events to switch some parameters </p><divclass="fragment"><divclass="line"><spanclass="keyword">class </span>MyEventReceiver : <spanclass="keyword">public</span> IEventReceiver</div><divclass="line">{</div><divclass="line"><spanclass="keyword">public</span>:</div><divclass="line"><spanclass="comment">// This is the one method that we have to implement</span></div><divclass="line"><spanclass="keyword">virtual</span><spanclass="keywordtype">bool</span> OnEvent(<spanclass="keyword">const</span> SEvent& event)</div><divclass="line"> {</div><divclass="line"><spanclass="comment">// Remember whether each key is down or up</span></div><divclass="line"><spanclass="keywordflow">if</span> (event.EventType == irr::EET_KEY_INPUT_EVENT)</div><divclass="line"> KeyIsDown[<spanclass="keyword">event</span>.KeyInput.Key] = <spanclass="keyword">event</span>.KeyInput.PressedDown;</div><divclass="line"></div><divclass="line"><spanclass="keywordflow">return</span><spanclass="keyword">false</span>;</div><divclass="line"> }</div><divclass="line"></div><divclass="line"><spanclass="comment">// This is used to check whether a key is being held down</span></div><divclass="line"><spanclass="keyword">virtual</span><spanclass="keywordtype">bool</span> IsKeyDown(EKEY_CODE keyCode)<spanclass="keyword"> const</span></div><divclass="line"><spanclass="keyword"></span>{</div><divclass="line"><spanclass="keywordflow">return</span> KeyIsDown[keyCode];</div><divclass="line"> }</div><divclass="line"></div><divclass="line"> MyEventReceiver()</div><divclass="line"> {</div><divclass="line"><spanclass="keywordflow">for</span> (u32 i=0; i<KEY_KEY_CODES_COUNT; ++i)</div><divclass="line"> KeyIsDown[i] = <spanclass="keyword">false</span>;</div><divclass="line"> }</div><divclass="line"></div><divclass="line"><spanclass="keyword">private</span>:</div><divclass="line"><spanclass="comment">// We use this array to store the current state of each key</span></div><divclass="line"><spanclass="keywordtype">bool</span> KeyIsDown[KEY_KEY_CODES_COUNT];</div><divclass="line">};</div></div><!-- fragment --><p> We create an irr::IrrlichtDevice and the scene nodes. One occluder, one occluded. The latter is a complex sphere, w
