Hello All I thought I'd add my recent experience to this thread in case it helps get to the bottom of this strange behavior.
Like the earlier posters, I was noticing that some of my text (changed from a callback) was getting dropped (displayed as blanks). As was suggested earlier, a crude but workable hack was on the first call to setText send a string with all the displayable ASCII characters and then send a blank string. Then, all the subsequent updates displayed fine. That hack was good enough for my purposes, so I didn't investigate any further. I did have the line text->setDataVariance(osg::Object::DYNAMIC); set in case that matters. For what it's worth: Windows 8.1 Pro 64 bit Microsoft Visual Studio Enterprise 2015 Update 1 using dual monitors and 2 graphics cards: Intel HD 4000 and AMD Radeon HD 7570 I don't know if this info helps or is just noise. My hope is that if there is indeed an obscure bug with osgText that this is another clue in getting to the bottom of it. Best Regards, Bob Kiser ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=67005#67005 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
