Hi Sanat, There's so much there, including functions that I have no idea what they do, that it'll be hard to figure out. There is definitely some unnecessary bits that make it even harder for people who aren't you to figure out what is going on - for example,
Code: backhoeGroundPosition = backhoePosition->getPosition(); backhoeGroundPosition = getCurrentPosition(backhoeGroundPosition); It appears that the argument to getCurrentPosition is never used within the function, so the first call (backhoePosition->getPosition(); ) is pointless. Not necessarily a killer problem, but the more tangled your code is, the harder it is for both you and us to figure anything out. Regardless... have you tried printing the results of various computations/calls to the screen? I'm thinking for example the value of the Vec3 returned by getCurrentPosition. Debugging messages that you add to your own code are invaluable in determining how things are working - you'll get much further that way than we will by looking at the code. If backhoeGroundPosition is always (0,0,0) after your function, that's a very different problem than if that value is changing but your model always appears in the same place on the terrain. Cheers, Tom ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=30205#30205 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
