1.4 -> FPSCamera->SetPosition

Wyszo · Post by **Wyszo** » Mon Oct 08, 2007 12:22 pm

Irrlicht 1.4 beta (linux)

Function SetPosition in FPS camera class produces strange results. I tell it to place the camera in the given position and it place it in a completely different point (like - a semi-random one). I am 100% sure, that I know where the given position is (I draw a box there ;P), and that the camera lands somewhere else. So - basically it's probably not the engine bug, but my lack of knowledge. Do I have to call some other function before changing position in real time? Any ideas?

JP · Post by JP » Mon Oct 08, 2007 12:25 pm

Did it work in previous irrlicht versions?

Are you using any collision detection?

Wyszo · Post by **Wyszo** » Mon Oct 08, 2007 5:30 pm

JP wrote:Did it work in previous irrlicht versions?

I don't know. I've never been using FPS Camera in previous versions. I'll check it when I have some spare time [yeah, this sentence probably has nothing to do with English grammar

].

JP wrote:Are you using any collision detection?

Yes, but I "teleport" camera much above the ground, so that collision ellipsoid doesn't touch the level mesh.

Wyszo · Post by **Wyszo** » Wed Oct 10, 2007 6:53 pm

Ok, you may safely disregard this toppic. I tested my code under 1.3.1 and it worked exactly the same way. So I used the template from one of the tutorials to check whether setPosition works as we all expect. Of course - it does. So I must have put this function with other argument somewhere else in my code (and forgot about that), there is no other explanation. Sorry for being troublesome

EDIT:

Ok, I found it - heh, stupid of me. Like JP suggested I use collision response animator and that causes a problem. Of course I don't know how to change position of a mesh controlled by this animator...

christianclavet · Post by **christianclavet** » Thu Nov 15, 2007 7:57 pm

Perhaps, you could remove the animator, do your teleport move, then reapply the animator?