Page 6 of 6 FirstFirst ... 456
Results 51 to 60 of 60

Thread: The Most Important Project Since Mesa 1.0?

  1. #51
    Join Date
    Mar 2012
    Posts
    184

    Default

    Quote Originally Posted by Luke_Wolf View Post
    If that's the case why hasn't a certain WINE producer been sued yet? Also the whole they're going to sue us FUD is silly at best. of all of the things they might sue over their development libraries and languages are the least likely. Why? because Microsoft wants people using their technologies and if they sue over them then would you care to make a guess at what people are less likely to do? That's right, stop or lessen use of it due to fear of getting sued themselves.
    They will sue if they will feel threatened by it thats all. Wine is not threatening them and this D3D reimplementation is the same.
    You conveniently forgot to quote my last sentence
    and they can do much more to annoy implementation and usefulness of DX API in Linux

  2. #52
    Join Date
    Feb 2012
    Posts
    180

    Default

    Forgive me if this has already been asked, since I only had time to skim the thread, but doesn't this mean support could be passed through to programs like Virtualbox or QEMU to get better performance than Wine's d3d? Last time I checked, Wine's lib is how Direct3D works in Virtualbox at the moment, although they have an experimental WDDM driver architecture working.

    Even still, I do like the idea of Gallium3D taking advantage of its portable nature someday and supporting a much wider base of operating systems.

  3. #53
    Join Date
    Oct 2008
    Posts
    3,012

    Default

    Quote Originally Posted by Luke_Wolf View Post
    got a link to that letter to the court? This is the first I've heard of it.
    http://arstechnica.com/tech-policy/2...result-stands/

  4. #54
    Join Date
    Jan 2010
    Posts
    23

    Default

    Quote Originally Posted by scionicspectre View Post
    Forgive me if this has already been asked, since I only had time to skim the thread, but doesn't this mean support could be passed through to programs like Virtualbox or QEMU to get better performance than Wine's d3d? Last time I checked, Wine's lib is how Direct3D works in Virtualbox at the moment, although they have an experimental WDDM driver architecture working.

    Even still, I do like the idea of Gallium3D taking advantage of its portable nature someday and supporting a much wider base of operating systems.
    I don't know how their stuff works, but I think what they want is a WDDM DDI driver with a fake GPU underneath. The way this is implemented would replace the D3D stack (d3d9.dll) which is arguably not very virtualization friendly. I suppose though, if they just want a full pass-through, they could totally do that. It wouldn't work on proprietary drivers unless someone writes pipe_gl or they keep wined3d as a backup (like we do), but it's perfectly possible.

    If someone wants to, the Windows DDI for GPU drivers could be implemented and it would be a small matter of some kernel integration to get it running with the official D3D stack. However, I just don't give a damn about Windows. If someone wants to, go ahead, but it would require a near full rewrite of nine.

  5. #55
    Join Date
    Jul 2010
    Posts
    51

    Default

    The way I see it is that older software would work better as most new games use DirectX 10/11 and/or OpenGL anyway. DirectX 9 is dying at best, so it shouldn't pose any threat to future DirectX vs OpenGL smack talk.

  6. #56
    Join Date
    Jan 2009
    Posts
    607

    Default

    Considering there are new games being developed for Direct3D 9 such as StarCraft 2: Legacy Of The Void. and the lifespan of such a game is at least 5 years, I don't expect Direct3D 9 to become irrelevant until 2018.

    It's not important how many games support Direct3D 10/11. The only thing that matters is how many games supporting Direct3D 10/11 do not support Direct3D 9. And that number should be pretty big for us to even care about Direct3D 10/11.

    The likely scenario is that Mesa will eventually support acceleration of all popular Direct3D APIs.

  7. #57
    Join Date
    Apr 2013
    Posts
    101

    Default

    So, how can I install the Direct3D 9 state tracker?

    and I would like to see benchmarks of this patch enabled against the default wine.

  8. #58
    Join Date
    Oct 2008
    Posts
    104

    Default

    Regardless of anything else, the #1 reason no major vendor is going to use an open source driver on Windows is that doing so will mean computers with their GPUs will be blocked from being able to play back protected content by Microsoft.

  9. #59
    Join Date
    Nov 2010
    Posts
    324

    Default

    Quote Originally Posted by jonwil View Post
    Regardless of anything else, the #1 reason no major vendor is going to use an open source driver on Windows is that doing so will mean computers with their GPUs will be blocked from being able to play back protected content by Microsoft.
    There's a number of reasons why an open source driver would never work in Window. What you're referring to is Silverlight with Netflix. Even then, eventually Netflix will switch over to HTML5.

  10. #60
    Join Date
    Oct 2008
    Posts
    104

    Default

    Quote Originally Posted by Dukenukemx View Post
    There's a number of reasons why an open source driver would never work in Window. What you're referring to is Silverlight with Netflix. Even then, eventually Netflix will switch over to HTML5.
    No, I am talking about ALL content that uses the "Protected Media Path" functionality in Windows. (where the player that is trying to play the content will refuse to play unless all the components in the playback chain have been signed and verified by Microsoft)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •