Hi Ethan, On 30 May 2013 18:49, Ethan Fahy <[email protected]> wrote: > I notice that my index values can be slightly off if the angle between the > terrain texture normal and the line from the camera-to-terrain is close to 90 > degrees. I figured out that this goes away if I force Anisotropic Filtering > to be off in my NVidia control panel, so it's definitely an effect of AF. > However, I checked the VPB source and see that the default maxAnisotropy > value is set to 1.0, and in the osg::Texture::setMaxAnisotropy() function I > see a note saying that if maxAnisotropy is set to 1.0 that AF will be "off". > Am I missing something? Is there any way to make sure that the effects of AF > do not interfere with my indexing scheme without turning off AF in the > graphics card driver settings?
I believe those osgdem anisotropy settings will be just affecting the old osg::Geometry based pathway, the modern and default usage of osgTerrain will be using the GeometryTechnique's implementation that does set the anisotropy to 16.0, have a look at OpenSceneGraph/src/osgTerrain/GeometryTechnique.cpp. Again this is down to design and implementation assuming that it's working with colour data that is best to using filters that generate the best visual result. The way to address this would be to extend osgTerrain::Layer to contain a MaxAnisotropy property alongside the existing Layer::MinFileter and MagFiler properties, once this exists it would be easy to wire up VPB to set this property and for GeometryTechnique.cpp to read it. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
