StateAttributes issue OpenGL commands to affect the appearance of rendered geometry. OSG uses StateAttributes to sort your geometry during cull and draw. My understanding of your FLT material codes is that they are application data that don't map directly to OpenGL commands. (Perhaps indirectly: your app would interpret the material codes and replace them with StateAttributes.) If you store your material codes as StateAttributes, OSG will sort your geometry accordingly, but for no purpose, as it would do nothing to minimize OpenGL state changes, and could in fact interfere with the process, which would handicap performance.
You mentioned you are a newcomer to OSG. Can I recommend that you obtain one or both of the OpenSceneGraph intro books (if you haven't already).
-Paul
-------- Original Message --------
Subject: Re: [osg-users] [osgPlugins] How to read/write/access
OpenFlight Surface Material Code (SMC) and Feature ID (FID) ?
From: "Robert Ioiart" <rioi...@gmail.com>
Date: Thu, April 14, 2011 7:23 am
To: osg-users@lists.openscenegraph.org
Hi,
Thanks Paul for your answer. I am looking into that.
But what would be wrong with storing such non-visual properties as a new type of state set attribute?
Regards,
Robert
------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=38469#38469
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
