Our features and tests are completed during development for Windows, but new drivers that target those changes are externally developed and often are not complete until we are well into stabilization periods. D3D12 should not be the blocker accessing new graphics features for Independent Software Vendors (ISVs).Īdditionally, flighting and selfhost doesn't really work for new D3D12 features, only regression testing existing features. The D3D12 runtime shouldn't be holding these features back potentially depressing new hardware and OEM sales for new gaming scenarios. IHVs are successful at delivering new drivers to customers on older OS and customers can buy new hardware. It can take 1-2 years to get through OS upgrade sediment to make our features available to enough users for 3rd party game and application developers to target. While D3D team has been successful under this model, it has some issues.ĭ3D12 features are gated on an OS upgrade. These features require new drivers and often new hardware as well. Rationaleĭ3D12 has traditionally shipped new feature updates with new versions of Windows. Note that the public-facing name for the D3D12 redist and associated components is the DirectX 12 Agility SDK. With this scoping, D3D team is able to ship bug fixes via redist as well. See Supported Windows VersionsĪ redist upgrade only affects the applications that opt in and ship the new dll. Some changes to the base OS are required to support the redist, which D3D team has taken downlevel to 19H2. The D3D team will publish a new d3d12core.dll that developers can install in the application folder to access these features on older OS with an updated driver (and hardware if required).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |