denreaper
07-06-2006 03:47:53
I've been working on a test project... It is sort of a test of player movement using Ogre3D+OgreNewt. Working with it thus far has been extremely enjoyable. One problem I came across was translating my playerSceneNode while applying setStandardForceCallback() to it's OgreNewt body. My workaround was to translate the body itself by updating setPositionOrientation() with the playerSceneNode's getPosition() followed by where I wanted to move it. This worked fine with the physics, however, once my playerSceneNode had rested on the ground, it seemed as if freeze() was called for the playerBody. So, I attempted to add unFreeze() to the frameStarted() boolean in order to keep the playerBody() from freezing so the physics would always effect the player. This resulted in the following unresolved external symbol:
I have tried using the command playerBody->unFreeze(); outside of the main frame loop, but it does the same thing. The only thing that it seems it could be is a missing library. I haven't gotten any errors with the SDK up to this point, so it seems wierd for it to do it now.
Another issue I had was with the camera following the playerSceneNode. I have set it up so every time the frame updates, the camera's position updates to a position relative to the playerSceneNode. This seems to work, but the camera is glitching when physics effect the playerBody. It seems as if the physics are updating the position of the playerBody more than every frame, which doesn't seem logical. If you need more information, please say so. I can send you a zipped up package of the project so you can see what I mean by the camera issue. I can also paste of my coding on here if that helps as well.
Thanks,
Denny
error LNK2019: unresolved external symbol __imp__NewtonWorldUnfreezeBody referenced in function "public: void __thiscall OgreNewt::Body::unFreeze(void)" (?unFreeze@Body@OgreNewt@@QAEXXZ)
I have tried using the command playerBody->unFreeze(); outside of the main frame loop, but it does the same thing. The only thing that it seems it could be is a missing library. I haven't gotten any errors with the SDK up to this point, so it seems wierd for it to do it now.
Another issue I had was with the camera following the playerSceneNode. I have set it up so every time the frame updates, the camera's position updates to a position relative to the playerSceneNode. This seems to work, but the camera is glitching when physics effect the playerBody. It seems as if the physics are updating the position of the playerBody more than every frame, which doesn't seem logical. If you need more information, please say so. I can send you a zipped up package of the project so you can see what I mean by the camera issue. I can also paste of my coding on here if that helps as well.
Thanks,
Denny