Irrlicht Engine

Hybrid, Thanks for the hint ! Indeed the getMesh(0) was the right hint. Let me recap for others running in the same problems. The correct working code is... scene::IAnimatedMesh *mesh_animated = engine.scene->addHillPlaneMesh( (const irr::c8 *) "myHill_spikes", a, b, 0, 0, c, d ); CERR << ...

Autsch, JA, 1.5 has maybe everything - and the other comment was rather spam-kind of. I dont understand why addHillPlaneMesh is not creating a "proper" mesh ? Technically, and logically ! Lets take you through the irrlicht engine code IAnimatedMesh* CSceneManager::addHillPlaneMesh(..) { //...

addHillPlaneMesh creates a Node where I am not able to access/animate the underlying mesh. My main aim is that I just want to generate a terrain/hillplane where i can randomly animate the hills heights using the vertex indices. Obviously I progressed to get things right, but I have trouble to access...

Hey, I decided to use the physics stuff in a separate thread for the moment. And indeed it works very well. Obviously everything is possible with irrlicht, even so you don't have canonical multithreaded support. May be one day I will also use the GetForegroundWindow() hint. Thanks a lot for the comm...

Followed the threads and tested the code. Just to paste the working code with the latest irrlicht: #ifndef __POST_PROCESS_EFFECT_MOTION_BLUR__ #define __POST_PROCESS_EFFECT_MOTION_BLUR__ #include "irrlicht.h" using namespace irr; using namespace core; using namespace scene; using namespace...

i came up with the idea to have irrlicht rendering and physics in separate threads. I use irrlicht for displaying custom physical simulations. As the physics solver is heavy, it always hangs when I integrated it into the main loop rendering. My attempt to seperate it into thread (code below) failed ...

I just came across fences when a have a separate irrlicht render thread. The window was not painting any more if the while(-run()) loop is in another thread (boost thread).

Does this mean irrlicht was not capable of these things, *BUT* this modification shall fix it ?