Hi Paul & Robert,

thanks for your explanations. I started with osg 0.96 and use 1.2 for my software at the moment. At least in those versions I could not find any deprecated-warnings. Also I did not chose osg for performance-reasons primarily, but for it´s clean object orientated interface. Performance is mostly uncritical for me, as I do not use very large scenes.

Those index arrays were useful for me, as my program allows to change the geometries dynamically, and it is not guaranteed that all vertices exist at all times (depending on what the user does). So it was very easy to keep the vertex- and normal arrays the same size all time and just add or remove the indices depending on if a certain vertex exists or not.

I will do the following:
- revert my changes to my own geometry not to use vertex and normal indices anymore - code geometries for shapes like sphere, cylinder, box, cone and maybe some others.

I don´t feel fit to replace the ShapeDrawables with a geometry-based design, but I will be happy to post an example where those shapes are rendered as geometries. I think this would be a useful example, as some people tend to have problems with the math involved.

One more question regarding the flt-exporter: I use the RT 3d Model viewer plugin for firefox to display flt-files in a browser. The background is black here. I don´t know if this is an error of that plugin, or if the GL_CLEAR_COLOR is not yet exported by the exporter.

Regards,

Andreas

Robert Osfield schrieb:
Hi Paul,

On Tue, Dec 2, 2008 at 8:57 PM, Paul Martz <[EMAIL PROTECTED]> wrote:
You are correct that code can access ShapeDrawable primitive/vertex data
using the PrimitiveFunctor. Let me explain my thinking in more detail...
...

Thanks for the explanation.

... (I think there's a notify message when a Geometry takes the
slow path; perhaps we should bump up its verbosity to WARN.)

Perhaps this is something the Optimizer could do - have a warning
pass, or just a conversion pass that generates all the osg::Geometry
without indices - there is a method in osg::Geometry that does this
already:

        bool suitableForOptimization() const;

        void copyToAndOptimize(Geometry& target);

However, it seems to me that coding time would be better spent optimizing
one's data to not use sub-optimal rendering features.

It's curious how often I have strongly made the point about not using
vertex indices for performance reasons, the  comment in osg::Geometry
next to all the vertex indices code is pretty clear too:

 /** deprecated - forces OpenGL slow path, just kept for backwards
compatibility.*/

Yet users still want to use it.  With the coming of OpenGL 3.0 and
OpenGL ES and the lack of display lists and slow path support this is
becoming even more of an issue.

Something I've been planning on doing for a while is to move all
vertex index support out of osg::Geometry to prevent this type of
misuse of deprecated feature.  Perhaps it's time for me to do it -
support for reading old data files will be the awkward part.

Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to