Hi John, On Wed, Dec 16, 2009 at 12:15 PM, Jan Pečiva <[email protected]> wrote: > We can never agree in the discussion. Inventor became de-facto standard for > visualization and simulations for its design that was revolutionary in 90's.
Inventor was the defacto standard in the 90's for scientific visualization, while Performer became defacto standard for visual simulation. It was design that was so revolutionary no modern scene graph has adopted it. > Its design followed OpenGL state design, and if scene graph is well designed > - no cull traversal is needed - you render it directly while getting highest > possible performance. This is so wrong I don't know where to start. State storting and view furstum culling are the two essentials for efficient graphics, send graphics brute force to OpenGL is absolutely not the most efficient way. OpenGL on it's own doesn't do any state sorting or culling it relies upon the calling application to do this all and without it you will not get the best performance from your system. > But you are right, SGI turned to OpenGL Performer with > this cull overhead that can win other benefits. With poorly conditioned > scene graphs, OSG will perform probably much better. But well designed model > - it completely does not matter which one you are using - the traversal time > is negligible - at least that is what I usually reach with Open Inventor. Inventor might be familiar to you, but it certainly isn't anywhere near the OSG or Performer for performance even with the best conditioned scene graph imaginable. The only time Inventor might come close is when there is no view frustum culling because the whole scene is on screen and the state set up is very straight forward that the traversal isn't complicated. > You probably do not understand me. I do not want to re-interpret anything. > Plugin is going to get the same file name as before. Plugin gets loaded the > same way as before. The whole discussion was just about content of > ReaderWriter::_supportedExtensions . But please, let it be for now. To be clear automatically setting ReaderWriter::_supportedExtensions from osgDB won't be generally be safe. For specific plugins it might be possible to use it, and for these I would recommend you try loading the plugin and then adding the extra extension directly as I've suggested in my last two post. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
