DXVK 0.51 Brings Fixes & Asynchronous Pipeline Compilation Support

[theriddick]

What did I post that has anything in relation to photoshop brushes? or do you mean how they take their sweet time applying long existing fixes to wine?

[eydee]

Why this isn't upstreamed in wine yet? 😠

Maybe because it's a standalone project? Why isn't Handbrake or Libreoffice upstreamed in wine yet?

[theriddick]

It's also very easy to use dxvk as its just custom dlls for the most part. On top of the fact that dxvk is constantly being updated.

[tajjada]

Michael, i think it would be very interesting to see some benchmarks comparing the performance of games running in DXVK in Wine, compared to native DX11 on Windows.

Is that possible to do? / Does PTS support it? / Would it be too much effort?

[TemplarGR]

Stop with these idiotic comparisons.

Handbrake and LibreOffice have NOTHING to do with Wine, absolutely nothing.

DXVK has everything to do with Wine, and it cannot work without Wine.

One expects a d3d->vulkan translator to be part of Wine the same way d3d->opengl is part of Wine, end of story.

Technically DXVK can work on windows too, but i agree that it, alongside VK9, should be merged with Wine proper. It is about time Wine has full D3D->Vulkan support, for D3D8-12. They can do it, it is only a matter of will. Vulkan works on all platforms and hardware now, there is literally no excuse, unlike Gallium nine, other than ego and NIH syndrome.

[Djhg2000]

Vulkan works on all platforms and hardware now, there is literally no excuse, unlike Gallium nine, other than ego and NIH syndrome.

Good luck finding an ARM SoC with open source Vulkan support. Or an NVIDIA card for that matter. Or a pre-GCN Radeon card. Or Intel platforms older than Ivy Bridge. The list goes on and on.

There are plenty of reasons to keep OpenGL support for now and it doesn't make sense trying to mainline a driver with limited open source driver support, that competes with an existing implementation, is under heavy development, works perfectly well as a standalone project, and doesn't even use the same language in a huge project like WINE. DXVK is much better off being developed in a separate tree for now.

[VikingGe]

Is that possible to do? / Does PTS support it? / Would it be too much effort?

Almost no Windows game has a CLI-friendly builtin benchmark mode, so I guess that won't happen.

[TemplarGR]

Good luck finding an ARM SoC with open source Vulkan support. Or an NVIDIA card for that matter. Or a pre-GCN Radeon card. Or Intel platforms older than Ivy Bridge. The list goes on and on.

There are plenty of reasons to keep OpenGL support for now and it doesn't make sense trying to mainline a driver with limited open source driver support, that competes with an existing implementation, is under heavy development, works perfectly well as a standalone project, and doesn't even use the same language in a huge project like WINE. DXVK is much better off being developed in a separate tree for now.

Are you serious? Are you for real? Why does the Vulkan support need to be "opensource" for DXVK to work? Closed source Vulkan drivers work just as fine pal... Your whole argument is moot...

[Djhg2000]

Are you serious? Are you for real? Why does the Vulkan support need to be "opensource" for DXVK to work? Closed source Vulkan drivers work just as fine pal... Your whole argument is moot...

Because most of the software stack in a modern distro targets Mesa. I don't know how you've managed to miss that.

[smitty3268]

Because most of the software stack in a modern distro targets Mesa. I don't know how you've managed to miss that.

I'm not sure what you're trying to say, but DXVK works perfectly fine on the NVidia proprietary driver. That's explicitly one of their target platforms, and they've had nvidia developers helping them with bug fixes.

As for ARM - well, the idea for DXVK is to run windows games which are all x86 anyway, so you'd have to mix that with a cpu emulator which would crush performance... So that's kind of moot anyway, even if there was something causing their drivers to not work for some reason.

The real reason to keep GL support is for Macs (until MoltenVK is up to par), and for older hardware that doesn't support Vulkan. And of course because the whole project is still fairly new and still working through some of the kinks.