From Fedora Project Wiki
Line 25: Line 25:
Developers: [https://plus.google.com/110830723758089847922 Axel Davy] (davyaxel@free.fr)
Developers: [https://plus.google.com/110830723758089847922 Axel Davy] (davyaxel@free.fr)


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.
When playing d3d9 games on Wine, their d3d9 calls are translated to OpenGL. This is complicated process, because you have to deal with different drivers having different extensions available, and the fact that opengl and d3d9 don't map perfectly together. Gallium Nine implements the d3d9 API with Gallium internal API, which maps better to d3d9 than OpenGL. You remove some layers of translation in the process which enables better performance. Gallium Nin


Actual situation is, that wine has to translate DirectX => OpenGL => Gallium, which add complications and brings inefficiency. What we can do about it? It's easy, skip OpenGL!
'''what is Gallium''':
Most opensource drivers were migrated to Gallium framework. Thanks to Gallium framework is possible simply extend all drivers, by state trackers (ST) with different functionality.
Gallium is an internal graphic driver abstraction of Mesa to enable support of non-opengl languages more easily (it is used for vdpau and vaapi on r600/radeonsi for example). It is used by nouveau and r300 up to radeonsi for AMD. Intel Opengl support doesn't use gallium, but a gallium driver named ilo exists, but isn't sponsored by Intel.
For these which will work, you'll get reduced cpu usage and better performance.
 
In my case BioShock runs with gallium-nine about 35-45 fps, which is nice. Without I get from my on-cpu AMD 6550D graphic card only 23-35 fps (tested from saved point). So – difference between playable and “poor performance”.
 
[ game: resolution 1920×1080, all graphic settings off; hw: gpu clock 720 Mhz, memory 1866 Mhz ]


[https://wiki.ixit.cz/d3d9 https://wiki.ixit.cz/d3d9]
[https://wiki.ixit.cz/d3d9 https://wiki.ixit.cz/d3d9]

Revision as of 10:48, 22 December 2014

Wine to use mesa Direct3D

Summary

Enhancing mesa and wine with Direct3D9 support will increase performance and reduce resource usage in applications which using D3D9 framework.

Owner

  • Name: Igor Gnatenko
  • Email: ignatenkobrain@fedoraproject.org
  • Release notes owner:

Current status

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

Detailed Description

Developers: Axel Davy (davyaxel@free.fr)

When playing d3d9 games on Wine, their d3d9 calls are translated to OpenGL. This is complicated process, because you have to deal with different drivers having different extensions available, and the fact that opengl and d3d9 don't map perfectly together. Gallium Nine implements the d3d9 API with Gallium internal API, which maps better to d3d9 than OpenGL. You remove some layers of translation in the process which enables better performance. Gallium Nin

what is Gallium: Gallium is an internal graphic driver abstraction of Mesa to enable support of non-opengl languages more easily (it is used for vdpau and vaapi on r600/radeonsi for example). It is used by nouveau and r300 up to radeonsi for AMD. Intel Opengl support doesn't use gallium, but a gallium driver named ilo exists, but isn't sponsored by Intel.

https://wiki.ixit.cz/d3d9

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
Hardware compatibility List
Hardware Status References
AMD (r300-r500)
Warning warn
[1]
  1. ↑ some game will work, not all of them
AMD (r600-radeonsi)
Pass pass
Nvidia (nv50-nvc0)
Pass pass
[1]
  1. ↑ minor issues on some games that won't trigger on amd
Intel (ilo)
Fail fail
[1]
  1. ↑ Driver not advanced enough for now
Intel (i915)
Inprogress inprogress
[1]
  1. ↑ untested. Probably won't work

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=399135"