OctTreeTriangleSelector : wrong collision before first frame

You discovered a bug in the engine, and you are sure that it is not a problem of your code? Just post it in here. Please read the bug posting guidelines first.
Post Reply
Kayl
Posts: 14
Joined: Wed Jun 08, 2005 7:17 am

OctTreeTriangleSelector : wrong collision before first frame

Post by Kayl »

Hey,

I have noticed a small bug "user-side" (I am not into hacking into irrlicht and stuffs).

- Create a terrain
- Change its position
- Create an octreetriangleselector
- make some ray/mesh collision detection

>> the collision returned doesn't consider the new position

As soon as the first frame has been displayed (meaning real positions have been computed or i don't know what) it works fine

So, if i want to do collision detection even before the first frame, i have to do :
terrain->updateAbsolutePosition();

and it will work fine.

Maybe real node position should be updated each time a collision test is done.
Post Reply