Now that that’s all cleared up, let’s take a closer look at Microsoft’s new graphics API-starting with a little history. The news so far has centered solely on Direct3D. As Microsoft’s Matt Sandy wrote on the official DirectX blog, DirectX 12 will also encompass “other technologies” that “may be previewed at a later date,” including “cutting-edge tools for developers.” That’s probably why we haven’t heard anything about, say, the next version of DirectCompute. We and others have occasionally referred to Microsoft’s new API as DirectX 12, but what premiered at GDC was technically Direct3D 12, the graphics component of DirectX 12. In this article, I’ll try to explore Direct3D 12’s inception, the key ways in which it differs from Direct3D 11, and what AMD and Nvidia think about it.įirst, though, let’s straighten something out. Now that I’m back home with all my notes from various sessions and meetings with Microsoft and GPU vendors, I can go into a little more detail. I already covered some of those developments in a couple of news posts during the GDC frenzy. It may also be the first version of Direct3D to eke significant performance gains out of current hardware. This will be the first version of Direct3D to unify graphics programming across all of Microsoft’s gaming platforms.
JUST CAUSE 3 DIRECTX 12 WINDOWS
The company announced some pretty big changes, including support for a lower level of abstraction and compatibility with not just Windows, but also Windows Phone and the Xbox One.
JUST CAUSE 3 DIRECTX 12 UPDATE
At the Game Developers Conference this year, Microsoft pulled back the curtain on Direct3D 12, the first major update to its graphics APIs since 2009.
0 kommentar(er)
