I think JS is talking about the problem I was having. Here's a hacky fix that worked for me. I probably should have already sent this to osg-submissions, but maybe you can validate it first or think of something better. Try changing this one line in TextBase.cpp:
http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/2011-June/052479.html -- Terry Welsh mogumbo 'at' gmail.com www.reallyslick.com > > Message: 11 > Date: Fri, 01 Jul 2011 11:31:00 -0400 > From: Jean-S?bastien Guay <jean-sebastien.g...@cm-labs.com> > To: OpenSceneGraph Users <osg-users@lists.openscenegraph.org> > Subject: Re: [osg-users] Strange osgText::Text problem while moving > from OSG2.9.8 to OSG 3.0.0 > Message-ID: <4e0de834.40...@cm-labs.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi George, Sergey, > >> We run into same issue yesterday, and as far as i can tell, this changed >> between osg 2.9.9 (all works ok) and 2.9.10(nothing visible). osgText is >> culled when it shouldnt for some reason. For temporary solution you can turn >> off culling on geode with text or add some other drawable as u did. > > I seem to remember people talking about a bug in the osgText bounds > computation that causes it to never calculate its bounds, so they always > stay at the initial value (which is an invalid bounds) and so the text > is always culled (and thus it can never calculate its bounds, and so on). > > Not much to go on but it might be the hint that helps you to fix this... > > J-S _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
