Hi Andreas,
On 6/13/06, Andreas Goebel <[EMAIL PROTECTED]> wrote:
> What hardware are you having problems with?
Uh, it´s customers hardware. I will have to look again. I can´t really
test there.
Knowing what the hardware will help significantly in tracking down
what the problem might be.
> Have you stepped through the src/osgText/Text.cpp to see if its
> disabling the mipmapping or not?
I have read through it now front to back and back to front and can´t see
any place where there is a check for any environtmentvariable.
Its in src/osgText/Font.cpp, the relevant code :
const Extensions* extensions = getExtensions(contextID,true);
bool generateMipMapSupported = extensions->isGenerateMipMapSupported();
On the other hand I don´t know how to see if there is mipmapping going
on or not. I just thought so, because an older post of you said that
osgText::Text uses mipmapping.
One debug technique is to enable the verbose debug output from the OSG
via the env var:
set OSG_NOTIFY_LEVEL=DEBUG
And then catch all the output to the console. It'll mention the
detected hardware/driver type as well as what extensions are being
tested for and used.
Maybe I am looking at the wrong place, I see the texture coordinates
being computed, but I don´t seem to find the actual rendering of the
characters to the textures, hm.
The characters are rendered as texture mapped quads, osgText::Font
manages the state/textures, with the FreeType plugin provided the
imagery that is downloaded to textures.
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
