"I go fast!1!11!1!"
- Oct 13, 2008
- 25,558 (6.27/day)
- IA, USA
|Processor||Intel Core i7-6700K (4 x 4.00 GHz) w/ HT and Turbo on|
|Motherboard||MSI Z170A GAMING M7|
|Memory||2 x Kingston HyperX DDR4-2133 8 GiB|
|Storage||Crucial MX300 275 GB, Seagate Exos X12 TB 7200 RPM|
|Display(s)||Samsung SyncMaster T240 24" LCD (1920x1200 HDMI) + Samsung SyncMaster 906BW 19" LCD (1440x900 VGA)|
|Case||Coolermaster HAF 932 w/ USB 3.0 5.25" bay|
|Audio Device(s)||Realtek ALC1150, Micca OriGen+|
|Power Supply||Enermax Platimax 850w|
|Mouse||SteelSeries Sensei RAW|
|Software||Windows 10 Pro 64-bit|
|Benchmark Scores||Faster than the tortoise; slower than the hare.|
But Windows 7 still doesn't support anything greater than WDDM 1.1. What they did is add the libraries so that Direct3D 12 calls can be translated to run on WDDM 1.1. Games using the AP will gain some performance benefit from that because D3D12 is much more multithreaded and leaner but it doesn't gain all of the benefits because many were in WDDM versions since 1.1. Could Microsoft have done this a long time ago? Yes. Why have they not? D3D12 adoption in general has been painfully slow so it wasn't a priority until a heavyweight (like Blizzard) started throwing its weight around.