Hi Chris,
Did you simply try to do "nothing" in the callback?
Maybe the callback is called to often per frame.
Also I've sort of lost track how you apply the matrices to your boned
model.
If you are using visitors to retrieve the bones in the callback, it
might be simply to slow. I would use some timers or a profiler or even
simply skipping code to measure/determine which part of the
update-callback slows you down.
Hi guys thanks for the quick replies!
I am indeed testing in Release always now. (I've learnt my lesson ;)).
At the moment Im trying to get hardware skinning working by following the
osganimationhardware example.
As of now I haven't got it working as for some reason it won't load the
shaders/skinning.vert file. Not sure why I just get an error saying it didn't
load. The file path is ok as all of my other textures and models load no
problems from that directory.
Yes the update traversal is a bit ridiculous isn't it? I am hoping the
skinning might solve the issue but Im not sure.
In the updatecallback attached to the hand model is a call to our api and then
adjusting the bones position and rotation using some matrix calculations. At
first I thought it could be the way our calculations and api call were being
done that was slowing things down. However, I tested this by simply not adding
the model to the scene but still allowing the callback to perform all of its
functions and api call and the update traversal dropped down to around 2.5 per
frame. So i don't think its our api call or calculations that is sucking up so
much time.
------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=62329#62329
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
