Hi Alex, It might be that the Nvidia driver/hardware combination doesn't implement FBO well. Another possibility is that your GPU local memory is too small and the driver is having to swap things on/off the card.
Do you have any other systems that you could try. Robert. On Tue, Oct 14, 2008 at 8:14 AM, Alexander Löffler <[EMAIL PROTECTED]> wrote: > Hi Robert, > > Robert Osfield wrote: >> If your frame rate drops when you zoom it suggests you are fill >> limited which shouldn't be related to the FBO/PixelBuffer/FrameBuffer >> choice for the RTT as it's res is fixed. Hight RT cost would make >> give the app less time to do this fill so perhaps the extra fill is >> just the final straw that broke the camels back. >> >> W.r.t FBO RTT performance - it should be better than >> PixelBufer/FrameBuffer as it will avoid the need to a copy to texture >> (there isn't GLX support for PixelBuffer Render To Texture). If you >> are getting worse performance then this is a driver issue. >> >> What drivers/hardware are you using? > > I am using an NVIDIA GeForce 6200 on SuSE Linux 11 and the current drivers > from > NVIDIA. Here are the relevant parts of my glxinfo (the necessary extensions > for > FBO rendering are all present as well): > > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: NVIDIA Corporation > server glx version string: 1.4 > client glx vendor string: NVIDIA Corporation > client glx version string: 1.4 > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce 6200 TurboCache(TM)/PCI/SSE2 > OpenGL version string: 2.1.2 NVIDIA 173.14.09 > > Alex. > _______________________________________________ > 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
