I just received this message. It certainly would indicate that ATI cards DO support
performance counters in recent versions of the drivers:
Anyone checked OSG's performance counter implementation with the listed ATI
driver?
Graphic Remedy is proud to announce the release of gDEBugger Version 3.0.
This new major version supports OpenGL V2.1 standards and contains ATI Hardware
Performance Counters (Percentage Hardware busy, Transform Clip Lighting unit busy, etc.)
integration. These counters are displayed in the Performance Graph and Performance
Dashboard Views. V3.0 also adds the option for Floating Licenses with a dedicated License
Server.
To use the new ATI Hardware Performance Counters inside gDEBugger Version 3.0 all you need
to do is to upgrade your ATI display driver to the latest version available from:
http://ati.amd.com/ (at least: CATALYST 6.9 [8.29])
Download:
========
The new version can be downloaded from http://www.gremedy.com/download.php.
All users may install this 30 days trial version. If you have previously downloaded a
trial version of gDEBugger and the trial period has ended or is shorter than 7 days, you
will automatically be given an additional 7 days to test the new features.
Existing gDEBugger customers who are within their maintenance license period are entitled
to a free upgrade to this version using their present license file.
What's New in Version 3.0:
====================
Added:
----------
- Supports OpenGL 2.1 standard.
- Adds ATI Hardware Performance Counters Integration (Performance Graph View and
Performance Dashboard View).
- Supports Floating licenses: License Server, License Server Status application.
Changed:
-------------
- gDEBugger GUI docking system improvements.
- Reduce gDEBugger memory consumptions.
- Break command will not suspend the debugged application run between glBegin-glEnd
statements.
- Numerous OpenGL ES implementation enhancements.
- Install package was upgraded.
Fixed bugs:
----------------
- Screen resolutions changes may cause an application window with zero size.
- Textures with borders were not handled correctly (Texture viewer).
- In few scenarios, texture images created by glTexImage2D were not stored and
displayed.
As always, we welcome your feedback.
Please submit your comments and suggestions to
http://www.gremedy.com/feedback.php.
Sincerely,
The gDEBugger team
Graphic Remedy
http://www.gremedy.com
mailto:[EMAIL PROTECTED]
------------------------------------------------------------------------------------------------------------
This email was sent to you by the Graphic Remedy gDEBugger mailing list.
For more information, please visit http://www.gremedy.com/mailinglist.php.
--
Chris 'Xenon' Hanson aka Eric Hammil | http://www.3DNature.com/ eric at logrus
"I set the wheels in motion, turn up all the machines, activate the programs,
and run behind the scenes. I set the clouds in motion, turn up light and
sound,
activate the window, and watch the world go 'round." -Prime Mover, Rush.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
