Direct3D 12 Rendering Driver (Mesa NIR approach) by RandomShaper · Pull Request #70315 · godotengine/godot
github.com
Direct3D 12 Rendering Driver (via Mesa 3D's NIR) This is a replacement of #64304. The difference lies in how they approach shader compilation; i.e., how they manage to take SPIR-V shaders into Dire...

By supporting Direct3D 12, Godot gains support for multiple new platforms, such as:

  • Windows Store (UWP).
  • Windows on ARM.
  • GDK.
  • XBox —which can’t be supported officially by Godot, but for which Direct3D 12 support is essential—.

Depending on the complexity of the scene, effects used, etc., this first version of the renderer performs generally worse than the Vulkan one. In some tests, D3D12 has not been able to deliver more than 75% of the Vulkan frames per second. In some other, D3D12 has been able to outperform Vulkan by a small margin. Performance improvements will be ironed out over time.

Expect it to come in Godot 4.3

    • tabular@lemmy.worldEnglish
      13·
      11 months ago

      Perhaps this may help people learn of Godot, and maybe see that they could be playing some game made by Godot on open platforms. Vulkan does a good job though so I think it would be better if devs stopped depending on directX/box.

      • Kolo@mastodon.social
        2·
        11 months ago

        @tabular @version_unsorted personally I agree that everything should just use vulkan. Why waste resources.
        But on the other hand I don’t think it does any harm to include proprietary api. It only helps in integration of OSS (xbox for example can just use it afaik)