Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
d3d9_gallium_state_tracker [2014/05/29 03:26]
okias [Roadmap] 		d3d9_gallium_state_tracker [2014/05/29 19:50]
okias bugzilla
Line 19: Line 19:
  
 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 ==== ==== Roadmap ====
Line 24: Line 26:
   * (1) Pass the tests (dlls/d3d9/tests)   * (1) Pass the tests (dlls/d3d9/tests)
   * (2) have an idea how to handle later d3d10 and d3d11   * (2) have an idea how to handle later d3d10 and d3d11
-  * (3) Show clear evidence that performance of d3d9 can't be achieved through translation d3d9 -> opengl.+  * (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.   * (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   * (5) Have an interface between wine and mesa that allows independent updates of mesa and wine
Line 30: Line 32:
  
 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_upstream|Review for upstream inclusion]]
   * [[d3d9_debugging|Debugging]]   * [[d3d9_debugging|Debugging]]
   * [[d3d9_supported_hardware|Tested Hardware]]   * [[d3d9_supported_hardware|Tested Hardware]]
   * [[d3d9_demos|Demos]]   * [[d3d9_demos|Demos]]