Why was Direct3D 12 removed?

[Luminoth Prime]

I was waiting for Dolphin to be updated to fix the recent Metroid Prime scan bug introduced with 5.0-3322 so I could update from 3318, and when I saw that it was fixed, I downloaded the latest version. Started up Metroid Prime Trilogy, but I noticed that the game was running much slower than usual. I went into the graphics to investigate and found that it was set on Direct3D 11. I went to change it back to Direct3D 12, only to find it's no longer there. Went back to 3318 and found that I could use D3D 12 again.

Why was it removed, and will it return in future updates?

As a side question, is the new Cubeb audio codec supposed to be faster?

[Admentus]

Read the may report for the reason behind the removal of D3D12. You will read as well the reason for the removal of JITIL.

https://en.dolphin-emu.org/blog/2017/06/03/dolphin-progress-report-may-2017/

[seoulgamer]

(06-26-2017, 06:38 PM)Luminoth Prime Wrote: I was waiting for Dolphin to be updated to fix the recent Metroid Prime scan bug introduced with 5.0-3322 so I could update from 3318, and when I saw that it was fixed, I downloaded the latest version. Started up Metroid Prime Trilogy, but I noticed that the game was running much slower than usual. I went into the graphics to investigate and found that it was set on Direct3D 11. I went to change it back to Direct3D 12, only to find it's no longer there. Went back to 3318 and found that I could use D3D 12 again.

Why was it removed, and will it return in future updates?

As a side question, is the new Cubeb audio codec supposed to be faster?

It doesn't suit the developers to leave Direct3D 12 in because it wasn't coded well and wouldn't support new features they wanted to add. As far as I know, the person who developed Direct3D 12 abandoned it, and the other developers had no interest in carrying on that person's work.

Cubeb has slightly lower latency than the other backends, and works on all platforms.

[JMC47]

We've left features in too long before and caused huge controversies. We'd rather kill it early before we're maintaining hacks to keep it around like previous backends.

[Luminoth Prime]

(06-26-2017, 07:06 PM)Admentus Wrote: Read the may report for the reason behind the removal of D3D12. You will read as well the reason for the removal of JITIL.

https://en.dolphin-emu.org/blog/2017/06/03/dolphin-progress-report-may-2017/

Thanks. Good to know that the progress from D3D12 is being carried forward into the Vulkan plugin, at least. I'll try it out and see how it works, because last time I tried it, D3D12 was still better.

(06-26-2017, 10:24 PM)seoulgamer Wrote: It doesn't suit the developers to leave Direct3D 12 in because it wasn't coded well and wouldn't support new features they wanted to add. As far as I know, the person who developed Direct3D 12 abandoned it, and the other developers had no interest in carrying on that person's work.

Cubeb has slightly lower latency than the other backends, and works on all platforms.

(06-27-2017, 08:48 AM)JMC47 Wrote: We've left features in too long before and caused huge controversies. We'd rather kill it early before we're maintaining hacks to keep it around like previous backends.

Damn, that all sucks. I had absolutely no problems with Direct3D 12 and used it on everything. Guess I'll hold on to 3318 until more progress is made on Vulkan or something.