I am experiencing problems rendering osgText::Text and osgText::Text3D
in the same scene. I have boiled it down to a nice bite-size chunk of
code which I have attached. I am running version 2.8.
Is this a bug?
Frank
_______________________________________________
osg-users mailing list
osg-...@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Thanks for looking into this problem.
On Thu, Feb 19, 2009 at 1:08 PM, David Callu <led...@gmail.com> wrote:
> Text3D case:
> Delegate the cache coherence of font file in osgText to the user
> is not a good idea. So to fix this I think to 2 solution:
> - never use the cache when load a font for a Text3D. Just because
> to load a Font3D, we use option in osgDB::readObjectFile()
> - move osgText::Font3D implementation in osgText::Font,
> suffix ex-Font3D method with "3D" in osgText::Font
> (so osgText::Font3D::getGlyph() become osgText::Font::getGlyph3D()
> )
> And so Text and Text3D use the same osgText::Font object which
> contain
> 2D and 3D glyph.
I think merging the osgText::Font and Fon3D implementations would be
the cleanest approach.
Another, more hacky approach would be to postfix the font file name by
.Text3D or something similar and then have the freetype plugin return
Font3D when it detects this.
Robert.
Robert.
I think merging the osgText::Font and Font3D implementations would be
the cleanest approach.
Another, more hacky approach would be to postfix the font file name by
.Text3D or something similar and then have the freetype plugin return
Font3D when it detects this.