From Fedora Project Wiki
< Changes
Frantisekz (talk | contribs) |
(Add trackers) |
||
| (23 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
== Summary == | == Summary == | ||
Proposal to replace | Proposal to replace default wined3d backend with DXVK, A Vulkan-based translation layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine. | ||
Currently, wine in Fedora uses wined3d and users can install | Currently, wine in Fedora uses wined3d and users can optionally install DXVK (be it wine-dxvk package or by any other means). With this change accepted, wine would use DXVK instead of wined3d on supported GPUs automatically. | ||
== Owner == | == Owner == | ||
* Name: [[User:frantisekz| Frantisek Zatloukal]] | * Name: [[User:frantisekz| Frantisek Zatloukal]] , [[User:Mooninite| Michael Cronenworth]] | ||
* Email: fzatlouk@redhat.com | * Email: fzatlouk@redhat.com | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF33]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 29: | Line 29: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* FESCo issue: | * FESCo issue: [https://pagure.io/fesco/issue/2456 #2456] | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1867215 #1867215] | ||
* Release notes tracker: | * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/546 #546] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 37: | Line 37: | ||
DXVK is an alternative to wined3d providing more performant and more compatible way to run Windows applications and games using DirectX 9, 10 and 11. | DXVK is an alternative to wined3d providing more performant and more compatible way to run Windows applications and games using DirectX 9, 10 and 11. | ||
More detailed description is available on [https://github.com/doitsujin/dxvk DXVK Github]. | |||
DXVK is available | DXVK 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, | Should this proposal be accepted, [https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4# 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. | |||
This proposal can be accepted in a "reduced form" of replacing the default wined3d backend only for DirectX 10 and 11 and leaving DirectX 9 to be handled by the current wined3d. | |||
== Feedback == | == Feedback == | ||
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | ||
[https://www.reddit.com/r/linux/comments/hvbyyr/fedora_proposal_to_replace_default_wined3d/?utm_medium=android_app&utm_source=share Reddit thread on /r/linux] | |||
* "Man, fedora 33 shaping up to be one incredible release" | |||
* "wined3d doesn't have better compatibility at the moment" | |||
* "I picked a bad time to install Leap 15.2. So many bugs. I should've waited a few months or just waited for the next Fedora release." | |||
* "With this [https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4#_1__26 PR] added to check for compatibility, it sounds like a no-brainer to me." | |||
[https://www.phoronix.com/forums/forum/software/desktop-linux/1195484-fedora-looks-to-make-dxvk-their-default-back-end-for-direct3d-9-10-11-on-wine Discussion on Phoronix Forum] | |||
[https://www.gamingonlinux.com/2020/07/linux-distro-fedora-33-may-get-dxvk-as-the-default-for-wine/page=1#comments Article and Discussion on GamingOnLinux] | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Fedora users running recent Windows games will get superior performance and compatibility. Steam already leverages DXVK | Fedora users running recent Windows games will get superior performance and compatibility. Steam already leverages DXVK but there are other Game Stores and standalone games which would benefit from DXVK. Users had to know about this project and install it manually (or use e.g. Lutris), whereas having DXVK included by default will make sure everybody gets the best possible performance and compatibility. | ||
I haven't done benchmarking per se, there are multiple resources on the | I haven't done benchmarking per se, there are multiple resources on the Internet comparing DXVK and wined3d. If necessary I will do additional testing on my hardware in the week of July 27th. | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Merge https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4 ; add Recommends: wine-dxvk into wine the package. | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 73: | Line 88: | ||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
The aim is to convert users with supported Hardware Configuration to DXVK as a part of Fedora 32 > Fedora 33 upgrade. There should not be any breakage since postinst script of wine-dxvk package would verify if the GPU supports Vulkan or not and set alternatives to wined3d or DXVK accordingly. | |||
There is a slight possibility of user experience degradation compared to wined3d on old Intel iGPUs supporting just a subset of Vulkan specification (Ivy Bridge and Haswell generations). I haven't had any opportunity to test DXVK on such hardware, however, if issues are discovered, check for Vulkan from wine-dxvk package PR ( https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4#_1__26 ) could be improved to block certain GPU vendors/generations/models. | |||
AMD and/or nVidia GPUs should not be affected, they either do not support Vulkan at all, or they support it fully. | |||
On GPUs without Vulkan support, wine-dxvk would remain installed and unused, consuming about 167 MB of HDD space. Users would be able to opt-out from using DXVK by adding 'exclude=wine-dxvk*' into /etc/dnf/dnf.conf and removing wine-dxvk package. | |||
== How To Test == | == How To Test == | ||
| Line 84: | Line 101: | ||
2. Install wine-dxvk package | 2. Install wine-dxvk package | ||
3. Run | 3. Run some Windows game with wine | ||
A testday will take place before Fedora 33 GA to determine and workaround (disable DXVK and fallback to wined3d) issues on potentially broken hardware and GPU drivers. | |||
In cases when something worked before installing wine-dxvk and stopped after (or regressed), bugs should be reported to [https://github.com/doitsujin/dxvk/issues DXVK Issue Tracker]. | |||
== User Experience == | == User Experience == | ||
| Line 109: | Line 128: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: Obsolete wine-dxvk through base wine package | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No | ||
* Blocks product? | * Blocks product? No | ||
== Documentation == | == Documentation == | ||
Latest revision as of 18:01, 7 August 2020
DXVK as default wined3d backend on VK capable hardware
Summary
Proposal to replace default wined3d backend with DXVK, A Vulkan-based translation layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine.
Currently, wine in Fedora uses wined3d and users can optionally install DXVK (be it wine-dxvk package or by any other means). With this change accepted, wine would use DXVK instead of wined3d on supported GPUs automatically.
Owner
- Name: Frantisek Zatloukal , Michael Cronenworth
- Email: fzatlouk@redhat.com
Current status
- Targeted release: Fedora 33
- Last updated: 2020-08-07
- FESCo issue: #2456
- Tracker bug: #1867215
- Release notes tracker: #546
Detailed Description
DXVK is an alternative to wined3d providing more performant and more compatible way to run Windows applications and games using DirectX 9, 10 and 11.
More detailed description is available on DXVK Github.
DXVK 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.
This proposal can be accepted in a "reduced form" of replacing the default wined3d backend only for DirectX 10 and 11 and leaving DirectX 9 to be handled by the current wined3d.
Feedback
- "Man, fedora 33 shaping up to be one incredible release"
- "wined3d doesn't have better compatibility at the moment"
- "I picked a bad time to install Leap 15.2. So many bugs. I should've waited a few months or just waited for the next Fedora release."
- "With this PR added to check for compatibility, it sounds like a no-brainer to me."
Article and Discussion on GamingOnLinux
Benefit to Fedora
Fedora users running recent Windows games will get superior performance and compatibility. Steam already leverages DXVK but there are other Game Stores and standalone games which would benefit from DXVK. Users had to know about this project and install it manually (or use e.g. Lutris), whereas having DXVK included by default will make sure everybody gets the best possible performance and compatibility.
I haven't done benchmarking per se, there are multiple resources on the Internet comparing DXVK and wined3d. If necessary I will do additional testing on my hardware in the week of July 27th.
Scope
- Proposal owners: Merge https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4 ; add Recommends: wine-dxvk into wine the package.
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
The aim is to convert users with supported Hardware Configuration to DXVK as a part of Fedora 32 > Fedora 33 upgrade. There should not be any breakage since postinst script of wine-dxvk package would verify if the GPU supports Vulkan or not and set alternatives to wined3d or DXVK accordingly.
There is a slight possibility of user experience degradation compared to wined3d on old Intel iGPUs supporting just a subset of Vulkan specification (Ivy Bridge and Haswell generations). I haven't had any opportunity to test DXVK on such hardware, however, if issues are discovered, check for Vulkan from wine-dxvk package PR ( https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4#_1__26 ) could be improved to block certain GPU vendors/generations/models.
AMD and/or nVidia GPUs should not be affected, they either do not support Vulkan at all, or they support it fully.
On GPUs without Vulkan support, wine-dxvk would remain installed and unused, consuming about 167 MB of HDD space. Users would be able to opt-out from using DXVK by adding 'exclude=wine-dxvk*' into /etc/dnf/dnf.conf and removing wine-dxvk package.
How To Test
1. Make sure you have Vulkan compatible GPU ('vulkaninfo' runs without errors)
2. Install wine-dxvk package
3. Run some Windows game with wine
A testday will take place before Fedora 33 GA to determine and workaround (disable DXVK and fallback to wined3d) issues on potentially broken hardware and GPU drivers.
In cases when something worked before installing wine-dxvk and stopped after (or regressed), bugs should be reported to DXVK Issue Tracker.
User Experience
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: Obsolete wine-dxvk through base wine package
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? No
- Blocks product? No
Documentation
N/A (not a System Wide Change)