Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Last revision Both sides next revision
d3d9_gallium_state_tracker [2014/03/15 14:05]
okias created
d3d9_gallium_state_tracker [2014/05/31 18:34]
okias
Line 1: Line 1:
-Gallium D3D9 state tracker know also as gallium-nine or "d3d9 st".+====== Gallium D3D9 state tracker know also as gallium-nine or "d3d9 st"====== 
 + 
 +IRC: #d3d9 on freenode.net
  
 Consist from two parts Consist from two parts
Line 7: Line 9:
 At this moment, must be compiled both mesa and wine from special repos or has to be patched. At this moment, must be compiled both mesa and wine from special repos or has to be patched.
 Correct way it's build mesa and wine from git repositories, placed here Correct way it's build mesa and wine from git repositories, placed here
-  * https://github.com/okias/Mesa-3D(gallium-nine-10.0 branch) +  * https://github.com/chrisbmr/Mesa-3D (gallium-nine branch) 
-  * https://github.com/okias/wine +  * https://github.com/chrisbmr/wine (d3dadapter9-wip branch)
-Both repositories are forked from person, who worked on d3d9 last (which was <a href="https://github.com/chrisbmr" target="_blank">Christoph Bumiller</a>)+
-<em>In this moment, work continue on porting gallium nine to Mesa 10.1.</em>+
  
 You should build mesa as usual, only change is passing <code>--enable-nine</code>. You should build mesa as usual, only change is passing <code>--enable-nine</code>.
 For wine build, only thing you'll need is already builded mesa with enabled nine. For wine build, only thing you'll need is already builded mesa with enabled nine.
  
-When you got this working, run <code>regedit</code>go to <code>HKCU->Software->Wine->Direct3D</code> and create DWORD named UseNative. Set value to 1 for enable, 0 to disable.+When you got this working, run <code>regedit</code> 
 +go to 
 +<code>HKCU->Software->Wine->Direct3D</code> and create DWORD named UseNative. Set value to 1 for enable, 0 to disable.
  
 As first thing, you may want try run __wine/dlls/d3d9/tests__ and see what pass. As first thing, you may want try run __wine/dlls/d3d9/tests__ and see what pass.
 +
 +Also if you want see CPU load and FPS, ''export GALLIUM_HUD="cpu0+cpu1+cpu2+cpu3;fps"'' (for 4 core configuration)
 +
 +==== Roadmap ====
 +
 +  * (1) Pass the tests (dlls/d3d9/tests)
 +  * (2) have an idea how to handle later d3d10 and d3d11
 +  * (3) Prove that d3d9 state tracker can be faster than translation d3d9 -> opengl.
 +  * (4) Handle applications that do opengl and d3d on the same window.
 +  * (5) Have an interface between wine and mesa that allows independent updates of mesa and wine
 +
  
 Also check other wiki pages as: Also check other wiki pages as:
 +  * [[https://trello.com/b/W7S0wqHW/d3d9|Bugzilla]]
 +  * [[d3d9_upstream|Review for upstream inclusion]]
 +  * [[d3d9_debugging|Debugging]]
 +  * [[d3d9_supported_hardware|Tested Hardware]]
 +  * [[d3d9_demos|Demos]]