Page 1 of 8 123 ... LastLast
Results 1 to 10 of 73

Thread: Gallium3D Direct3D 9 For Wine Revived, Again

  1. #1
    Join Date
    Jan 2007
    Posts
    15,378

    Default Gallium3D Direct3D 9 For Wine Revived, Again

    Phoronix: Gallium3D Direct3D 9 For Wine Revived, Again

    Back in 2010 there was native Direct3D 10/11 support on Linux via a Gallium3D state tracker implemented for the Radeon/Nouveau open-source drivers. The D3D 10/11 Linux support was ultimately removed but last year a Direct3D 9 state tracker was published with patches for it to be taken advantage of by Wine. That work has now been restored...

    http://www.phoronix.com/vr.php?view=MTU2OTQ

  2. #2
    Join Date
    Sep 2007
    Posts
    343

    Default

    Quote Originally Posted by phoronix View Post
    David Heidelberger is trying to push along "Gallium Nine" since it delivers better Wine-based gaming performance for some games/hardware. The point he uses is Bioshock running 35-45 FPS with the Direct3D Linux support or just 23-35 FPS with the conventional Wine Direct3D to OpenGL translation layer. David fixed up the state tracker to work with Mesa 10.x. Thus it's now easy to play with and run the code.
    What would be the performance on Windows?

  3. #3
    Join Date
    Dec 2012
    Posts
    573

    Default

    Quote Originally Posted by oleid View Post
    What would be the performance on Windows?
    Higher, but we don't know what gpu he has.

    I'm really interested in the d9 state tracker because wow doesn't work with radeon at all. Either the d3d performance is ass or the opengl driver crashes the game.

  4. #4
    Join Date
    Oct 2011
    Posts
    69

    Default

    The comparison done with Bioshock running with Wine + it's own d3d implementation vs Wine + Gallium is interesting, but it would be even more interesting to see Bioshock with Wine + Gallium vs Wine + CSMT and it's one d3d implementation.

  5. #5
    Join Date
    Jun 2009
    Posts
    171

    Default




  6. #6
    Join Date
    Sep 2007
    Posts
    343

    Default

    Quote Originally Posted by zanny View Post
    Higher, but we don't know what gpu he has.
    We know, have a look at this page.

  7. #7
    Join Date
    Sep 2010
    Posts
    55

    Default

    Running Bioshock at such framerate on an integrated Radeon 6550D is actually quite good. I find it funny that Wine developers don't want to integrate such functionality. It could seriously boost Wine adoption. From the outside it looks a bit of an ego-trip.

  8. #8
    Join Date
    Mar 2011
    Posts
    19

    Default

    Quote Originally Posted by werfu View Post
    Running Bioshock at such framerate on an integrated Radeon 6550D is actually quite good. I find it funny that Wine developers don't want to integrate such functionality. It could seriously boost Wine adoption. From the outside it looks a bit of an ego-trip.
    This would benefit Linux only.

    I may be wrong (speacially since Wine is huge) but wouldn't creating a fork of Wine that has Linux as its only target OS while implementing the Gallium3D DX9 sorta fix this thought incompatiblity?

  9. #9
    Join Date
    Sep 2010
    Posts
    55

    Default

    Quote Originally Posted by andrebrait View Post
    This would benefit Linux only.

    I may be wrong (specially since Wine is huge) but wouldn't creating a fork of Wine that has Linux as its only target OS while implementing the Gallium3D DX9 sorta fix this thought incompatiblity?
    Forking for only a functionality wouldn't be so useful. I guess it shows that Wine should be more modular. Gallium3D is also available on FreeBSD. The only OS supported by Wine that wouldn't get the DX9 tracker is MacOS X (if we neglect OpenBSD and NetBSD, which I suspect users aren't really gamers).

  10. #10
    Join Date
    Dec 2009
    Location
    Greece
    Posts
    351

    Default

    As i said in the other thread, no matter what the Wine devs reply, it is apparent to all that they don't want to support the d3d9 state tracker because it is not available for Macs.

    They have no valid argument. The vast majority of the work for the state tracker is on the part of Mesa. The only thing they need to do is mainline the ability to use it... In effect this means just providing d3d9 calls as-is instead of transforming them to opengl... It is actually quite trivial...

    I am sure MESA would mainline the d3d9 state tracker if it was used by Wine. As it is, there is no point, since no one aside a few do-it-yourselfers will use it...

Posting Permissions

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