From Fedora Project Wiki
Line 84: Line 84:


== Contingency Plan ==
== Contingency Plan ==
<!-- 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: Revert and try to do in next release
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: beta freeze
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Blocks release? No
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? Workstation
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==

Revision as of 16:35, 15 December 2014

Direct3D

Summary

What is difference between classic wine and wine enhanced with Nine support? The answer is simple - performance. When we play most DirectX 9 games, we want the highest performance possible. Sadly, wine loses a lot of Direct3D9's speed through the inefficent translation of HLSL and D3D9 calls to OpenGL.

https://wiki.ixit.cz/d3d9

Owner

  • Name: Igor Gnatenko and Axel Davy
  • Email: ignatenkobrain@fedoraproject.org and davyaxel@free.fr
  • Release notes owner:

Current status

  • Targeted release: Fedora 22
  • Last updated: 15 december, 2014
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

TODO List
Description Assignee Status References
Enable Direct3D9 state tracker in mesa Igor Gnatenko
Pass pass
[1][2]
  1. ↑ http://pkgs.fedoraproject.org/cgit/mesa.git/commit/?id=dc2fc7918e7ba9fc5ded9f59e0b5d3725414ece6
  2. ↑ http://pkgs.fedoraproject.org/cgit/mesa.git/commit/?id=21449d7adf357239bf8982165d29676b2611cd06
Land d3d support in wine Axel Davy and Igor Gnatenko
Inprogress inprogress
[1]
  1. ↑ https://github.com/iXit/wine

Benefit to Fedora

All games wich using Direct3D9 (most of games which wine can run) will have very very good speedup. Real numbers?

  • On a simple demo with a weak CPU (Athlon TK-55 X2) CPU usage dropped from 20% to 10%!
  • Need a benchmark? 2014-09-14, with older DRI2
  • For real games, we're getting mostly double the framerate (depends on the game, the driver and the card)

Scope

  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

  1. # dnf install wine
  2. Check if mesa-d3d installed automatically
  3. Run some benchmarks/games in wine

Expected results: no problems and more better performance

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Revert and try to do in next release
  • Contingency deadline: beta freeze
  • Blocks release? No
  • Blocks product? Workstation

Documentation

N/A (not a System Wide Change)

Release Notes

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