Benchmark Results: Metro 2033 (DX11)
| Header Cell - Column 0 | 1680x1050AAA/4x AF | 1680x10504x AA/16x AF | 1920x1080AAA/4x AF | 1920x10804x AA/16x AF | 2560x1600AAA/4x AF | 2560x16004x AA/16x AF |
|---|---|---|---|---|---|---|
| Percent Gainfrom 10.3 to 11.1 | 1.73% | 2.05% | 1.13% | 8.35% | 4.56% | 62.62% |
Metro 2033 isn't even supported by Catalyst 9.10, again, a likely result of AMD's venerable Cypress architecture outdating this game. Within the first 30 seconds, the benchmark stalls then crashes to the desktop. Once we move to 10.3, we finally get a completely stable run. So, somewhere in that range of drivers, AMD optimized its software to properly support Metro 2033.
Even though we lack scores from Catalyst 9.10, the remaining results are quite interesting. Driver to driver, the improvements are still small, but at higher resolutions, we see larger gains. From 10.3 to 11.1, we approach a 10% improvement, but this only applies to 1920x1080 when we max out quality settings.
As we move up to 2560x1600, we see about a 5% gain without any AA or AF. But once we enable these settings, the results change dramatically. Moving from 10.3 to 10.8, the frame rate drops by almost 30 percent. Update to 11.1 and suddenly you are looking at a 63% increase the other way to 11.6 FPS.
