Announcement

Collapse
No announcement yet.

Wine's Big Command Stream D3D Patch-Set Updated

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • artivision
    replied
    Originally posted by stefandoesinger View Post
    The easy work is done. The hard part that separates a proof of concept from code that is stable and maintainable in the long term is remaining. In other words, following the 80/20 rule, 80% of the work still needs to be done.

    A good start would be to quantify the performance difference between wined3d and gallium-nine with reproducible benchmarks and then isolate where the performance difference is coming from. And that means not just "it reduces overhead, so it's faster", but something like "There's CPU-side overhead in module X, and GPU-side overhead because shader instructions A, B and C are inefficiently handled by module Y".

    If it turns out that there's a fundamental advantage to a gallium state tracker, and that it's not just working around some bugs in Mesa and Wine that could be fixed with e.g. a better GLSL compiler or adding one or two focused GL extensions to support some d3d-isms better the next task is finding a stable API exposed by gallium-nine and used by Wine.

    Matteo has done some testing with gallium-nine on r600g. If I remember correctly, he saw a moderate performance gain (~15% or something), but attributed most of that to insufficient optimization in the driver's GLSL compiler. I'll ask him to make sure my memory serves me right.

    Thats weird, i have mostly a 2x gain with i5 and 3x+ with Core2. This thing offloads the Cpu dramatically, and some advanced shaders that are not even run with Wine, are now work. Its like a GLSL=disabled plus Threaded-Optimisations plus+++ all together.

    Leave a comment:


  • artivision
    replied
    Originally posted by stefandoesinger View Post
    Well, our (the Wine developers') and the Mesa developers' time is limited. With regards to running d3d9 applications on Mesa we have the following options:
    1. Make Wine work better on all OpenGL implementations.
    2. Make Mesa run all OpenGL applications better.
    3. Write and maintain lots of special code to make Wine run better on Mesa.


    Considering finite resources, we believe 1 is the way to go, and we're helping the Mesa devs with 2. You may disagree and submit code to either project to implement 3. But don't think it's a conspiracy when we disagree with you about what to do with our time.


    I have MESA and Wine compiled by me with the D3D9 state tracker. I just don't know why all the rest they don't. And they need to do the same as me. I didn't ask you why you don't work to improve the state tracker. We have seen what a single person can do if he is technologically and ethically right (a state tracker). So i don't really want to ask anything about your time. There are distros and individuals responsible to have those packages in their repository.

    Leave a comment:


  • RavFX
    replied
    Got a freeze on EVE-online. Was running only one client.

    Two core was stuck at 100% use for exefile.exe (with is the EVE client).
    Might be a rglrx related bug or something else as I'm mining with the same computer.

    Leave a comment:


  • stefandoesinger
    replied
    Originally posted by OnioWoess View Post
    Added HKCU/Software/Wine/Direct3D/SCMT/="enabled" key - it changes nothing.
    Probably because you misspelled it. It should be CSMT, not SCMT.

    Leave a comment:


  • okias
    replied
    D3D9 mesa + wine

    I working on porting D3D9 state tracker to Mesa 10.0. Then I'll proviede some patchset for mesa, wine and create Gentoo ebuilds. Anyway, it need some developer, because without it'll be unusable soon.

    Leave a comment:


  • OnioWoess
    replied
    Well, I dunno what I'm doing wrong but I see almost no difference yet between standard wine (1.6) and this one (1.7.10 patched), clean install both on Linux Mint XFCE Petra Also, on example of these games running under wine and under winXP: Xonotic, Killing Floor and Half Life 2, I still have huge difference in their performance and loss approx half of FPS under wine + freezes. Added HKCU/Software/Wine/Direct3D/SCMT/="enabled" key - it changes nothing. Tested on my old PC with nVidia GTS450 1Gb on 319 drivers, AMD X2 4400+ 1750 Mhz
    Last edited by OnioWoess; 01-12-2014, 04:27 PM.

    Leave a comment:


  • justmy2cents
    replied
    Originally posted by OnioWoess View Post
    excuse me for stupid questions, is this patch-set have effect only for open-source drivers? & this github wine version and crossover 13 from codeveawers are identical?
    i'd guess it is not working only for open source drivers. i'm using tarball from this github on NVidia blob and 2nd version i used was 1.7.10 tarball from wine site. if you noticed, performance was quite different for me. only patch that i applied on both was to get TR2013 working where you remove optimization for CreateEventExW

    no clue about 2nd question

    Leave a comment:


  • OnioWoess
    replied
    excuse me for stupid questions, is this patch-set have effect only for open-source drivers? & this github wine version and crossover 13 from codeveawers are identical?

    Leave a comment:


  • justmy2cents
    replied
    Originally posted by stefandoesinger View Post
    Yes, it can be reused. In fact, a big consideration in my work to merge this upstream is how this will interact with wined3d changes needed to support d3d10/11.
    that's nice to hear. keep on the good work

    Leave a comment:


  • stefandoesinger
    replied
    Originally posted by justmy2cents View Post
    now, question from complete n00b on directx department. is this able to be reused in DX10/11 and how much different those 2 are?
    Yes, it can be reused. In fact, a big consideration in my work to merge this upstream is how this will interact with wined3d changes needed to support d3d10/11.

    Leave a comment:

Working...
X