If you make use of the Wine compatibility layer on Fedora, it seems the upcoming Fedora 33 release may end up defaulting to DXVK for better performance.
Currently in Fedora, like most distributions, Wine is mostly left alone. Once installed, it's up to users to tinker with it and configure it (I much prefer using Lutris personally). That may change though if this latest proposal is accepted for Fedora 33 which releases in October 2020. There is currently a dedicated wine-dxvk package you can install to get it but this change would set DXVK as the default graphics backend for Wine to translate Direct3D 9/10/11 to Vulkan.
The benefits are obvious, like giving users of Wine a much better gaming experience for Windows-only titles. DXVK is used in Proton for Steam Play, it's developed at a quick pace for game compatibility and the performance is often far better than Wine's own wined3d which translates Direct3D to OpenGL.
See the proposal here if interested.
Article taken from GamingOnLinux.com.Some you may have missed, popular articles from the last month:
It took just about 4 years from first public Vulkan API spec release to distros switching to Vulkan-based solution for D3D translation on Wine by default. I’d say that’s a pretty good time frame for adoption of brand new graphics API.
3 Likes, Who?
I absolutely hope it gets rejected.
The last thing I want in the distro I use is some 3rd-party fork instead of upstream version. Otherwise WINE won't have any patches from Fedora anymore, as (rumor has it) DXVK does not play nice with WINE, outright conflicting with its libraries.
You can down-vote me to hell (well, except you can't ;) ), but I am firmly on WINE's side in their conflict.
DXVK guy is nobody and nothing without WINE (he can go sell his library to Windows users for all I care; I've heard it works on Windows™), he is in no position to bring incompatibility in a piece of software that: a) existed long before he even started his project; and b) enabled a lot of critical Windows™ applications to work in Linux (Winamp with its plug-ins, many of which have no Linux alternative, custom-built game resources extractors, banking software).
Prioritizing some custom upsetream-incompatible library over vanilla version is like a tail wagging a dog!
Everyone who absolutely WANTS DXVK-version can go to… Steam and install Proton™!!!
Last edited by Alm888 on 22 July 2020 at 11:40 am UTC
The last thing I want in the distro I use is some 3rd-party fork instead of upstream version. Otherwise WINE won't have any patches from Fedora anymore, as (rumor has it) DXVK does not play nice with WINE, outright conflicting with its libraries.
You can down-vote me to hell (well, except you can't ;) ), but I am firmly on WINE's side in their conflict.
DXVK guy is nobody and nothing without WINE (he can go sell his library to Windows users for all I care; I've heard it works on Windows™), he is in no position to bring incompatibility in a piece of software that: a) existed long before he even started his project; and b) enabled a lot of critical Windows™ applications to work in Linux (Winamp with its plug-ins, many of which have no Linux alternative, custom-built game resources extractors, banking software).
Prioritizing some custom upsetream-incompatible library over vanilla version is like a tail wagging a dog!
Everyone who absolutely WANTS DXVK-version can go to… Steam and install Proton™!!!
Last edited by Alm888 on 22 July 2020 at 11:40 am UTC
1 Likes, Who?
Quoting: Alm888The last thing I want in the distro I use is some 3rd-party fork instead of upstream version. Otherwise WINE won't have any patches from Fedora anymore, as (rumor has it) DXVK does not play nice with WINE, outright conflicting with its libraries.DXVK is just dll files. Theres no patch or fork required
8 Likes, Who?
Quoting: Alm888I absolutely hope it gets rejected.
The last thing I want in the distro I use is some 3rd-party fork instead of upstream version. Otherwise WINE won't have any patches from Fedora anymore, as (rumor has it) DXVK does not play nice with WINE, outright conflicting with its libraries.
You can down-vote me to hell (well, except you can't ;) ), but I am firmly on WINE's side in their conflict.
DXVK guy is nobody and nothing without WINE (he can go sell his library to Windows users for all I care; I've heard it works on Windows™), he is in no position to bring incompatibility in a piece of software that: a) existed long before he even started his project; and b) enabled a lot of critical Windows™ applications to work in Linux (Winamp with its plug-ins, many of which have no Linux alternative, custom-built game resources extractors, banking software).
Prioritizing some custom upsetream-incompatible library over vanilla version is like a tail wagging a dog!
Everyone who absolutely WANTS DXVK-version can go to… Steam and install Proton™!!!
I'm not familiar with Fedora, so I don't know how they do things, but --- if this were to happen --- couldn't you get Wine directly from WineHQ and use that? I'm on Ubuntu and I've always done that because the version in the Ubuntu repos has historically been pretty out-of-date. Not arguing, just wondering.
0 Likes
What about vkd3d, it might be confusing for users who wants out of the box dx12 app support as well.
Also Winamp, that's a name I haven't heard in decades
Also Winamp, that's a name I haven't heard in decades
1 Likes, Who?
TimeFreeze 22 Jul
Quoting: Alm888I absolutely hope it gets rejected.
The last thing I want in the distro I use is some 3rd-party fork instead of upstream version. Otherwise WINE won't have any patches from Fedora anymore, as (rumor has it) DXVK does not play nice with WINE, outright conflicting with its libraries.
Everyone who absolutely WANTS DXVK-version can go to… Steam and install Proton™!!!
Uhm.....its no fork. DXVK is just dll files. And DXVK-version is also wrong, you dont need Proton for that. And even if you would need Proton you dont need Steam to get Proton.
0 Likes
Quoting: Alm888I absolutely hope it gets rejected.
DXVK guy is nobody and nothing without WINE
Is it personal for you or what? what you have against him? take it easy...
Last edited by bubexel on 22 July 2020 at 12:53 pm UTC
5 Likes, Who?
Thinking on this for a bit (and my words matter exceedingly little because I don't use Fedora at all) I can understand wanting DXVK included with a system wine installation by default, but I can equally see some arguments against it. So I'll mention that here for discussion purposes; I don't really have a personal opinion one way or another, this is just for trying to add to the conversation.
The "for" will be pretty obvious, mostly revolving around better user experience with wine gaming out of the box in most cases, so I won't go into that too much.
The "against" is actually not about DXVK in particular, but rather about additions to a default upstream project. So I'll say wine and DXVK, but I really mean "widespread package and something added to it".
Installing wine should install wine, not wine + extras. Doing otherwise might just confuse people, especially if other distros don't do the same. If everyone (the most popular and largest user base distros) did the same thing, that might be a different case, but otherwise I can see it as a possible source of confusion for users, and developers as well (who can't guarantee that DXVK is available, except if Fedora 33, unless user did this, in which case instructions, except in this case, aaaaaarrrggh).
Then there's the case of updating DXVK, or wine. If one or the other breaks, it locks versions back. I'm still stuck on DXVK-1.5.1 (because reasons), but can happily update wine to 5.12 (or whichever).
Just some thoughts on the matter anyway.
The "for" will be pretty obvious, mostly revolving around better user experience with wine gaming out of the box in most cases, so I won't go into that too much.
The "against" is actually not about DXVK in particular, but rather about additions to a default upstream project. So I'll say wine and DXVK, but I really mean "widespread package and something added to it".
Installing wine should install wine, not wine + extras. Doing otherwise might just confuse people, especially if other distros don't do the same. If everyone (the most popular and largest user base distros) did the same thing, that might be a different case, but otherwise I can see it as a possible source of confusion for users, and developers as well (who can't guarantee that DXVK is available, except if Fedora 33, unless user did this, in which case instructions, except in this case, aaaaaarrrggh).
Then there's the case of updating DXVK, or wine. If one or the other breaks, it locks versions back. I'm still stuck on DXVK-1.5.1 (because reasons), but can happily update wine to 5.12 (or whichever).
Just some thoughts on the matter anyway.
0 Likes
Sounds like a terrible idea. DXVK is for games and does not work for most non-game software. The default should not be limited like that.
0 Likes
Quoting: Alm888I absolutely hope it gets rejected.
The last thing I want in the distro I use is some 3rd-party fork instead of upstream version. Otherwise WINE won't have any patches from Fedora anymore, as (rumor has it) DXVK does not play nice with WINE, outright conflicting with its libraries.
You can down-vote me to hell (well, except you can't ;) ), but I am firmly on WINE's side in their conflict.
DXVK guy is nobody and nothing without WINE (he can go sell his library to Windows users for all I care; I've heard it works on Windows™), he is in no position to bring incompatibility in a piece of software that: a) existed long before he even started his project; and b) enabled a lot of critical Windows™ applications to work in Linux (Winamp with its plug-ins, many of which have no Linux alternative, custom-built game resources extractors, banking software).
Prioritizing some custom upsetream-incompatible library over vanilla version is like a tail wagging a dog!
Everyone who absolutely WANTS DXVK-version can go to… Steam and install Proton™!!!
Wow wow wow!, you went from 0 to a 100 km/h in less than .1 seconds :p
I suggest you to read the Fedora proposal:
Quoting: Fedora ProposalDXVK is available as a wine-dxvk package since Fedora 31. wine-dxvk package uses alternatives system for following wine dll files: d3d9, d3d10.dll and d3d11.dll .
Should this proposal be accepted, a Pull Request will be merged into the wine-dxvk package which ensures it gets set as default backend only on systems with Vulkan support. wine-dxvk will then get added as "Recommends: wine-dxvk" into the wine package itself.
Users can run 'dnf reinstall wine-dxvk' after changing hardware configuration to get alternatives to use DXVK or wined3d updated.
So, it's not that wine+dxvk (which seems to be an already available option) will completely replace wine but that it will be the default option from now on for system that have a GPU that supports Vulkan API.
BTW, I think that this are the guys to blame for this blasphemy: Frantisek Zatloukal & Michael Cronenworth
3 Likes, Who?
Patreon
Liberapay
PayPal Donation
See more from me