Jump to content

DirectX 11 deprecation poll (Affecting UNIGINE SDK 2.20 and higher)


photo

DirectX 11 deprecation poll  

39 members have voted

  1. 1. What is your primary graphical API on Windows (UNIGINE 2.18 / 2.19)?

    • DirectX 12
      28
    • DirectX 11
      8
    • Vulkan
      2
    • Other (I'm using SDK 2.17 or earlier)
      1
  2. 2. I can easily switch to DirectX 12 if DirectX 11 is not available.

    • Yes
      31
    • No
      1
    • Likely Yes
      7
    • Likely No
      0
  3. 3. My current primary SDK version is:

    • 2.19.x
      34
    • 2.18.x
      3
    • Pre-DX12 version (2.17 and earlier)
      2

  • Please sign in or register to vote in this poll.
  • Poll closes on 01/30/25 at 10:35 PM

Recommended Posts

Posted

Dear UNIGINE Users,

DirectX 12 is now regarded as the primary rendering API on Windows, and we are considering removing the legacy DirectX 11 renderer from the engine to facilitate a smoother transition to new features, such as ray tracing and bindless textures. Maintaining two separate code paths has become increasingly challenging, and if you do not have a practical need for DirectX 11, we would be happy to eliminate it.

We are curious whether you still have strict requirements to use the DirectX 11 API in your projects or when delivering your projects to customers. Are you utilizing any DX11-exclusive features to integrate with third-party software that is also limited to DX11? We would like to understand if there are any factors preventing you from transitioning to DirectX 12 as the default.

Please vote and share your thoughts in the comments!

How to submit a good bug report
---
FTP server for test scenes and user uploads:

×
×
  • Create New...