Hi Paul, On Fri, Jun 6, 2008 at 8:36 AM, Paul Melis <[EMAIL PROTECTED]> wrote: > When an osgText::Text3D drawable is read from a .osg file its character > depth does not get applied, as its glyph representation isn't recomputed. > The osgtext3D example doesn't reveal this, as other methods are called after > applying the character depth which do force a glyph update. I've submitted a > patch^H^H^H^H^H an updated header files to osg-submissions for this one.
Yep, spotted the submissions patch, I'll be doing a submission work today so should merge this fix then. > The other problem I found was that with the osgtext3D example the bounds of > one of the text object isn't taken into account to update the clipping > planes. Simply running the osgtext3D example and rotating the scene so that > the string "CharacterSize..." is pointing away should reveal the problem. The Text3D has a bug in the bounding box computation. I spotted this on shortly after merging the submission and notified the author of it, but as yet no fix has come forward. I haven't had yet had a chance to take the code apart myself yet to fix it. > Btw, I notice a lot of lines "Doing release context" output by > osgthirdpersonview in a recent svn version and noticed the log message where > the responsible notify() was introduced. Are the messages a sign of > something bad happening or is their log level set too high? Nothing bad happening, just zealous debug messages I've added to monitoring single threaded makeCurrent/releaseContext support - I've just checked in quietening down of the code. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
