Little to no theory or derivation of graphics concepts, techniques or history is provided. High-level GPU programming concepts (such as high level shading languages) are not covered. GPU resource management, GPU process scheduling, and low-level Operating System driver/kernel architecture are not covered. The exact relationship and interactions between topics covered in the Graphics Pipeline with other Operating System Note that on each revision of this spec, allĬhanges made for that revision are summarized in a separate document typically distributed with the spec. These shaded boxes DO NOT provideĪ complete listing of all such trivia, however. Topic being described, or to flag an unresolved issues. Justification for decisions, explain history about a feature, provide clarifications or general remarks about a Occasionally, boxed text such as this appears in the spec to indicate Included will be some references to how the Graphics Pipeline isĬontrolled through a Device Driver Interface (DDI), and occasionally depictions of API usage as needed to illustrate points. Targeted by the D3D11.1 Graphics Pipeline, in a form that attempts to be agnostic to any Topics covered in this spec center on definition of the hardware architecture being In addition, software developers who are vested in the details about medium-term GPU hardwareĭirection will find interesting information. Hardware or software components that would be considered part of a D3D11.3-compliant system. The target audience for this spec are the implementers, testers and documenters of

Unit (GPU) design issues and the general architecture of Microsoft Windows Operating Systems, as well

It is assumed that the reader is familiar with real-time graphics, modern Graphics Processing This document describes hardware requirements for Direct3D 11. Condensed Table of Contentsġ.6 How D3D11.3 Fits into this Unified Spec 3 Functionalįull Table of Contents at end of document. Direct3D 11.3 Functional Specification Direct3D 11.

Mass effect rendering thread exception