Windows 10: In the works: OpenCL and OpenGL mapping layers to DirectX 12

Brink · Mar 24, 2020

Building on our previous work with the D3D12 Translation Layer library as well as the D3D11On12 and D3D9On12 mapping layers, weâre happy to share that we are working on two new projects: OpenCL and OpenGL mapping layers to D3D12.

Weâre excited to partner with engineers at Collabora to build OpenCL and OpenGL mapping layers using the Mesa 3D open source project. By leveraging our deep Windows and DirectX knowledge and Collaboraâs extensive experience in the open source graphics space, we will be adding a new D3D12 backend to Mesa to support OpenCL and OpenGL, with initial support targeting OpenCL 1.2 and OpenGL 3.3.

We have a few goals as a part of this new work:

Improve support for OpenCL- and OpenGL-based productivity and creative apps where native drivers are not available. We talk a lot about gaming on this blog, but this time the focus is on work, not play. By building the mapping layers on D3D12, we are building on the hard work we and our hardware partners have put into delivering stable and performant DirectX 12 drivers. When complete, the OpenCL and OpenGL mapping layers will provide hardware acceleration to more of your productivity and creative apps with just a DX12 driver, no other driver required.

Contribute back to the graphics community. As we are building the mapping layers using an open source project, we intend to participate in the open source community. We will upstream the D3D12 backend to the main Mesa repository as we continue its development, and we hope that the Mesa and broader graphics development community will benefit from our contribution. In the meantime, you can check out the work in progress.

Make it easier for developers to port their apps to D3D12. For developers looking to move from older OpenCL and OpenGL API versions to D3D12, the open source mapping layers will provide helpful example code on how to use the D3D12 Translation Layer library.

Stay tuned for more updatesâ¦

Angela Jiang
Click to expand...

Source: https://devblogs.microsoft.com/direc...rs-to-directx/

:)

Brink · Mar 24, 2020

D3D12 Translation Layer and D3D11On12 are now open source

If you’re a developer looking to port your game to DX12, we have good news: There’s a helper library available to get you there more easily!

We’re excited to announce that the D3D12 Translation Layer is now open source. The D3D12 Translation Layer is a helper library for translating graphics concepts and commands from a D3D11-style domain to a D3D12-style domain. As an example of how to use the library, we have also opened sourced D3D11On12, a mapping layer that maps graphics commands from D3D11 to D3D12.

Check out the source on GitHub:

D3D12 Translation Layer

D3D11On12

Read on to learn more about what this means for you.

A bit of history: Why mapping layers?

The first mapping layer project was started during the development of Windows 10 and D3D12. The Windows graphics team has a large set of D3D11 content which was heavily utilized during design and bring-up of the D3D12 runtime and driver models. In order to use that content, a mapping layer named D3D11On12 was developed.

This mapping layer proved successful and useful, to the point that a second mapping layer was developed, named D3D9On12. As the name implies, this maps from D3D9 to D3D12, and it has to solve a lot of the same problems as D3D11On12. D3D11On12 was thus refactored into two pieces: a part that implements the D3D11-specific concepts, and a more general part that translates more traditional graphics constructs into a modern low-level D3D12 API consumer. This more general part is what became the D3D12 Translation Layer. The translation layer code is currently being used by two mapping layers that ship as part of Windows: D3D11On12 and D3D9On12.

We realize that the D3D12 Translation Layer solves problems that are not unique 11On12 and 9On12, and we’re sharing the source with the graphics development community so others can reuse and benefit from our work. Both the D3D12 Translation Layer and D3D11On12 are available on GitHub today. If you have questions as you play with the code, feel free to reach out to us on Discord.

What can you do with the code?

Make the move to D3D12 more quickly. Leverage the D3D12 Translation Layer library as-is in your game to port your existing work to D3D12 faster.

Build a mapping layer from your favorite graphics or compute API to D3D12. Take advantage of a tested and conformant IHV DirectX 12 driver via your own D3D12 wrapper.

Contribute back to Windows. We welcome community contributions to both the D3D12 Translation Layer and D3D11On12. Improvements will be pulled back into the Windows codebase and eventually ship in future versions of Windows 10.

Learn more

D3D12 Translation Layer GitHub readme

D3D11On12 GitHub readme

D3D11On12 conceptual documentation

D3D11On12 reference documentation

D3D11On12 blog posts: First and second

Questions? Reach out on Discord

Angela Jiang
Click to expand...

Source: https://devblogs.microsoft.com/direc...w-open-source/

Harshavardhan Rathod · Mar 24, 2020

Directx 12 on Windows 10 is gone

Hi,

Thank you for being a part of Windows 10 Insider Preview.

I appreciate you for providing details about the issue and we are glad to assist you.

Try the following steps and check if it helps:

Step 1:

I suggest you to check the DirectX Version installed on your system.

Follow the below steps to check the DirectX Version:

Press Windows key + R from the Desktop.

Type dxdiag and hit Enter.

Check the DirectX Version.

Step 2:

I suggest you to update the Graphic driver from the Device Manager and check if it works.

Follow the below steps:

Press Windows + R on the Keyboard.

Type in devmgmt.msc and hit Enter.

Select Graphic driver from the list.

Right click on the Graphic driver and click on Update driver Software.

If the issue persists then install the latest graphic driver from the manufacturer and check if it helps.

Kindly let us know if you need any further assistance with Windows. We are glad to assist you.

Thank you.

FordGT90Concept · Mar 24, 2020

Why You Should Use OpenGL Instead Of DirectX

I have Quake and Quake II source on my server...

I found, and attached glqwcl-readme.txt, which goes into to detail about 3DFX, Glide, and OpenGL.

Quake also has the DirectX SDK. It appears that qwcl.exe would use DirectX and glqwcl.exe would use OpenGL; thusly, both are supported.

Quake II appears to be OpenGL.

So...

Quake - OpenGL and DirectX

Quake II - OpenGL

Quake III - OpenGL

Why was DirectX support dropped? Probably because the lead programmer (John Carmack) is a die hard Linux fan and DirectX means no playing the game on Linux. ID Software is, however, the exception, not the norm.

Windows 10: In the works: OpenCL and OpenGL mapping layers to DirectX 12

In the works: OpenCL and OpenGL mapping layers to DirectX 12

In the works: OpenCL and OpenGL mapping layers to DirectX 12

In the works: OpenCL and OpenGL mapping layers to DirectX 12

In the works: OpenCL and OpenGL mapping layers to DirectX 12 - Similar Threads - works OpenCL OpenGL

Directx 12

Directx 11 not working on directx 12

Directx 11 not working on directx 12

Directx 12

Directx 12

DirectX 12

Windows 10 gets OpenCL and OpenGL compatibility layers for apps

DirectX 12

Directx 12