Hacker News Reader

I wonder if they have any plans on implementing DirectX on top of Vulkan to make things faster.

There wouldn't really be a big advantage to that I think. The whole point of Vulkan is to give more control to the application developer (submit work from multiple threads, etc).

The statelessness is the advantage, in which case there is a nice mapping onto DirectX12. Otherwise you'd have to calculate and do Delta state changes yourself.

Then for DX11 and earlier, the state would be the draw calls themselves so to speak. You'd be shocked at how many game engines horribly mismanage state.

You don't think making calls to a DirectX implementation built on top of Vulkan would be more performant than coverting DirectX calls to OpenGL calls during runtime?

I reckon it's more likely there'll be an OpenGL implementation on top of Vulkan which Wine will just be able to use.

I mean as a way to avoid the DirectX to OpenGL translator overhead.

I'm completely unqualified to be commenting on this but I was thinking that there are already so many hours put into the translator that the Wine project may not want to throw away all that work.

Best to ask on the mailing list, though.

Reply on news.ycombinator.com