There are already several mature open source projects for implementing other APIs on Vulkan (e.g.
Personally, I feel like a focus primarily on Vulkan would make more sense: It seems to me like it would make a lot of sense to focus on Vulkan (and DX12) and do everything else via conversion layers. When you're releasing a new GPU architecture (or at least "new" to serious gaming) you already have your hands full with driver development. I wonder why they didn't make the strategic decision to do this from the start. I'm curious to see benchmarks of the popular DX9-based games and determining if there are any major graphical glitches from the emulation.ĮDIT, I dug up some information on the D3D9On12:ĮDIT2: I wonder if Intel plans on also emulating DX11 in DX12, or are they already doing that? So basically, D3D9On12 will act as a GPU driver all on its own instead of the actual GPU driver from Intel. Once the D3D9On12 layer receives commands from the D3D9 API, it will convert all commands into D3D12 API calls. Conversion works by sending 3D DirectX 9 graphics commands to the D3D9On12 layer instead of the D3D9 graphics driver directly. To replace it, all DirectX 9 support will be transferred to DirectX 12 in the form of emulation.Įmulation will run on an open-source conversion layer known as "D3D9On12" from Microsoft. Native DX9 hardware support is officially gone from Intel's Xe integrated graphics solutions on 12th Gen CPUs and A-Series Arc Alchemist discrete GPUs.
0 kommentar(er)
