From Fedora Project Wiki
Line 47: Line 47:
== Benefit to Fedora ==
== Benefit to Fedora ==


<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
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 and users had to know about this project and install it manually (or use eg. Lutris). Having DXVK included by default will make sure everybody gets the best possible performance and compatibility.
 
      Be sure to include the following areas if relevant:
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
 
    When a Change has multiple benefits, it's better to list them all.
 
    Consider these Change pages from previous editions as inspiration:
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


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 and users had to know about this project and install it manually (or use eg. Lutris). 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. I can do some testing on my hardware in the week of Jul 27th.


== Scope ==
== Scope ==

Revision as of 10:29, 21 July 2020

DXVK as default wined3d backend on VK capable hardware

Summary

Proposal to replace defualt wined3d backend by DXVK, A Vulkan-based translation layer for Direct3D 9/10/11 which allows running 3D applications on Linux using Wine.

Owner

Current status

  • Targeted release: Fedora 33
  • Last updated: 2020-07-21
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

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.

DXVK relies on Vulkan support on GPU. More detailed description is available on DXVK Github page ( https://github.com/doitsujin/dxvk ).

DXVK is available to users as 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, PR ( https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4# ) will be merged into 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 wine package itself.

Feedback

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 and users had to know about this project and install it manually (or use eg. Lutris). 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. I can do some testing on my hardware in the week of Jul 27th.

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

Aim is to convert users with supported Hardware Configuration to DXVK as a part of Fedora 32 > Fedora 33 upgrade. There shouldn't be any breakage since postinst script of wine-dxvk package would verify if GPU supports Vulkan or not and set alternatives to wined3d or DXVK accordingly.

The change would take place only on x86_64 architecture, there is a slight possibility of user experience degradation compared to wined3d on old Intel iGPUs supporting just a subset of Vulkan specifications. I don't have an 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 ) can be improved to blacklist certain GPU generations.

AMD and/or nVidia GPUs shouldn't be affected, they either don't support Vulkan at all, or support it fully.

How To Test

1. Make sure you have Vulkan compatible GPU ('vulkaninfo' runs without errors)

2. Install wine-dxvk package

3. Run your favorite Windows game with wine

Testday will happen to determine and workaround (disable DXVK and fallback to wined3d) issues on potentially broken hardware and GPU drivers.

User Experience

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/DXVKwined3d&oldid=582921"