Irrlicht Engine

Thanks, but seriously, no need. I totally selfishly work on Irrlicht because I actually use the engine myself.

Ah thanks for the video. I didn't realize when browsing quickly over the code earlier what m_windowIsActive really was (I thought it was some wxWidget variable if the window is active...). Too late here right now to really test things, but on another quick view at sources I notice you also render in...

Thanks. Code looks actually pretty similar to code in my current project (except we use WTL instead of wxWidgets in our project). Using timers should on Windows allow ~65 FPS. No idea really about wxWidgets on Linux and timers, thought I would have expected it to be rather a better resolution (usual...

Link gives me a 404, maybe not public?

Easiest is to use the functions in coreutil.h like irr::core::hasFileExtension or irr::core::isFileExtension
You can also take a look how it's implemented.

@Noiecity: Yeah - it's about Windows timer in general which are used for example in Windows sleep(). Irrlicht uses those for it's device->sleep(). Which I don't recommend using anymore therefore. Up to (including) Irrlicht 1.8 we also used sleep(1) for device->yield(), so that was just as bad. But t...

On OpenGL you can do it by rendering the model 3 times. First time as usual. Second time with a material which has material.Wireframe true and a bigger has material.Thickness. And third time with material.PointCloud true and even bigger Thickness. But it's unlikely to work well on other renderers as...

Another very old thing... I've looked on this a few times over the years without knowing what to do with it. svn trunk [r6602] (Irrlicht 1.9) has now some changes related to this: The bump textures in robmars example which start with a number were messed up in Irrlicht as the number was assumed to b...

OK, just noticed I still had this one on my todo. This got fixed recently in svn [r6599], so will work be in Irrlicht 1.9 Was actually rather trivial to fix - hardware buffers don't have to wait 20.000 frames when they keep the last reference to a meshbuffer. This won't release hw-buffers in all cas...

Ah, yes - mixture of animation and movement. Always a challenge. And can get super complicated once you have crazy stuff like walk into water and start swimming ;-)

I wouldn't worry too much about speed of camera calculations. You don't run many of those, so it's unlikely to ever be a bottleneck.

X can animate (there is an animated dwarf.x model in Irrlicht media), but there's hardly any support for that format out there anymore. I have unfortunately no examples for non-working animated .x models, so not sure what problem there was with the one there.

Note about sleep and yield in Irrlicht. Basically sleep() on Window is really a bad idea for games as it always is around 15ms minimum. So one call and you limit your game to ~65 FPS which people with 144hz screens these days won't like. Yield in Irrlicht 1.8 was just as bad as it used sleep(1) so i...

Noiecity recently made a tutorial video about that, maybe it helps? viewtopic.php?p=307310

Hm, mip-maps are usually good. Try setting AnisotropicFilter to 16 and enable TrilinearFilter for your texture layer in SMaterial. Both are off by default.