Announcement

Collapse
No announcement yet.

Gallium3D Direct3D 9 For Wine Revived, Again

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

  • 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
    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?

    Comment


    • #3
      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.

      Comment


      • #4
        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.

        Comment


        • #5


          Comment


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

            Comment


            • #7
              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.

              Comment


              • #8
                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?

                Comment


                • #9
                  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).

                  Comment


                  • #10
                    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...

                    Comment


                    • #11
                      Originally posted by TemplarGR View Post
                      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...
                      Stefan explained on this thread what's what:

                      http://phoronix.com/forums/showthrea...415#post388415

                      I've actually linked one of his posts that replies to yours directly so people can see how "out there" what you say is.

                      Why do you keep spewing crap?

                      I'm getting quite tired of toxic trolls such as yourself.

                      You seem to know quite a bunch about what "they need to do". So how about you do it?

                      Since when the hell do you get to dictate what a valid argument and what people do with their time.
                      Last edited by who_me; 01-13-2014, 02:40 PM.

                      Comment


                      • #12
                        Originally posted by who_me View Post
                        Stefan explained on this thread what's what:

                        http://phoronix.com/forums/showthrea...415#post388415

                        I've actually linked one of his posts that replies to yours directly so people can see how "out there" what you say is.

                        Why do you keep spewing crap?

                        I'm getting quite tired of toxic trolls such as yourself.

                        You seem to know quite a bunch about what "they need to do". So how about you do it?

                        Since when the hell do you get to dictate what a valid argument and what people do with their time.

                        Post anything you want. A lie is still a lie. We want a Wine with three options on GUI: D3D9_state_tracker, GLSL, GLSL_off. Anything else is considered criminal behavior by me.

                        Comment


                        • #13
                          Originally posted by who_me View Post
                          Stefan explained on this thread what's what:

                          http://phoronix.com/forums/showthrea...415#post388415

                          I've actually linked one of his posts that replies to yours directly so people can see how "out there" what you say is.

                          Why do you keep spewing crap?

                          I'm getting quite tired of toxic trolls such as yourself.

                          You seem to know quite a bunch about what "they need to do". So how about you do it?

                          Since when the hell do you get to dictate what a valid argument and what people do with their time.
                          I am sorry, did i hurt your feelings? I obviously saw his response and i don't buy it, and no one should because he has no valid argument...

                          The patch that is required on the Wine part is quite small and easily maintained. It can be a simple compile time option. It is obvious to anyone semi-knowledgable in software... The only thing they need to do is to NOT translate the d3d commands and instead send them to the d3d state tracker.

                          So his only "argument", that this will require much extra work, is invalid. It won't.

                          They just don't want to accept it because it will make their mac version look bad.

                          Comment


                          • #14
                            TemplarGR, if you think it's so easy, then *you* distribute a version of wine with d3d state tracker support, and deal with all the bugs users will report, and all other support issues. And of course keep your version updated with all changes in mainline wine. Then we'll see how it's just "a simple compile time option" and how "invalid" Stefan's argument supposedly is.

                            artvision, if you want it, then, well, make it happen! You can join up with TemplarGR.

                            Comment


                            • #15
                              Originally posted by TemplarGR View Post
                              I am sorry, did i hurt your feelings? I obviously saw his response and i don't buy it, and no one should because he has no valid argument...
                              Who the hell gives a shit about what arguments you and the other troll buy or not? Who the hell do you think you are?

                              Comment

                              Working...
                              X