Hi Paul, The new loader converts face records to Geodes to store record ID and comment. To get a decent framerate you have to enable MERGE_GEODES optimization. OSG_OPTIMIZER=DEFAULT MERGE_GEODES
Regards, Brede On 7/2/06, Paul Martz <[EMAIL PROTECTED]> wrote:
I tested 14 models against latest cvs and came up with the following results: * Load time is universally faster with the new plugin. On average, files load in 60% of the old plugin load time. * Many models loaded with the new plugin render slower. Average measured frame rate was 62% of the same models loaded and rendered with the old plugin. Three models suffered no significant reduction in frame rate. One model rendered at 23% of the old plugin frame rate (but the old plugin rendered the model incorrectly). As a concrete example, one model that should be readily available to many OpenFlight users is the a10s.flt model found in the Creator model gallery... OLD plugin load time: 4.6741 FPS: 383.938 NEW plugin load time: 2.69206 (58% of old plugin load time) FPS: 99.1844 (26% of old plugin frame rate) -Paul > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Robert Osfield > Sent: Wednesday, June 28, 2006 4:34 AM > To: osg users > Subject: [osg-users] Trialing the new OpenFlight as the default > > Hi All, > > I have just checked in mods to src/osgDB/Registry.cpp that > make selection of the new OpenFlight plugin as the default. > > The new plugin is much smaller, cleaner and supports latest > OpenFlight versions, but its also newer, and therefore less > stress tested and the variety of OpenFlight database that > crop up in the wild. Therefore it needs testing, and shaking > down if its going to be the default for 1.1. > > I'd appreciate the community trying out the CVS version of > the OSG and providing feedback on how it supports your > models, its load performance and runtime performance. > > You can select the old plugin any time by either preloading > it, or by using the OSG_OPEN_FLIGHT_PLUGIN env var. i.e. > > set OSG_OPEN_FLIGHT_PLUGIN=old > osgviewer mymodel.flt > > set OSG_OPEN_FLIGHT_PLUGIN=new > osgviewer mymodel.flt > > What I'd recommend is doing performance tests side by side, > such as recording an animation path (by pressing 'z' to > start/stop recording in osgviewer) around your test models, > then running these back in osgviewer i.e. > > osgviewer mymodel.flt -p saved_animation.path > > On completion of animation path the average frame rate will > be reported. Press space bar to reset to the begining of the > path, do this after load to make sure that animation timing > starts, otherwise it'll take a whole loop before starting the timing. > > I'll post some timing/feedback in my next email. > > Robert. > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
