Next up, drawing polygons. Here, too, various test candidates demonstrate interesting weaknesses.
For this test, we draw a total of 60,000 polygons with anywhere from 3 to 30 vertices, various line weights, and either color-filled or empty in some randomly chosen position on screen. As with our other tests, the random number generator seed remains constant so all test runs produce the same results. All objects appear entirely within the display area, so no clipping is necessary.
GDI Functions Called
Direct drawing test for polygons:
Polygons drawn from the DIB buffer:
When polygons get buffered, performance is the same whether Aero is turned on or off. For direct draw operations, the high-end graphics cards fall way behind the pack. We have to wonder what might be bottlenecking ATI's cards. Similarly, why is Nvidia's GeForce GTX 285 suffering from freezes and delays when rendering polygons? And why is it falling behind Intel's GMA 950/Atom combination and the older G45-based integrated core logic?
- Introduction: Why GDI Output For 2D Graphics Remains Relevant
- The 2D GDI For Windows XP Through Windows 7, In Detail
- 2D Graphics Output Using GDI: Direct Or Buffered?
- The Radeon HD 5000's Symptoms And Their Relevance To Windows 7
- Tom2D: Our Simple 2D GDI Benchmark
- Tom2D: Text Output
- Tom2D: Line Output
- Tom2D Splines/Bézier Curves
- Tom2D: Polygons
- Tom2D: Rectangles
- Tom2D: Ellipses
- Tom2D: Blitting
- Tom2D: Stretching
- UPDATE: ATI Steps Up With A Hotfixed Driver