Announcement

Collapse
No announcement yet.

AMD's R300 Gallium3D Driver Is Looking Good For 2011

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

  • #16
    Originally posted by marek View Post
    Nexuiz should be a lot faster if you enable GLSL.
    Has GLSL need to enable? if so, how?

    Comment


    • #17
      To clarify the Fedora situation: as of Fedora 14, r300g is the default driver (actually there's no way to choose r300c any more, it's not in the package). I believe this change was made back in June, though it may actually have been September (the changelog is a little unclear). To be fair to Michael, you could still characterize this as 'preparing', because F14 isn't released yet.

      The nouveau Gallium driver is still in mesa-dri-drivers-experimental, I'm not sure when Ben is planning to mark it as not-experimental any more. But it actually works pretty well on a lot of hardware now. I'm running GNOME Shell on it as I type this.

      Comment


      • #18
        Originally posted by Beiruty View Post
        Has GLSL need to enable? if so, how?
        Nexuiz menu -> Settings -> Video -> Use OpenGL 2.0 shaders (GLSL)

        Comment


        • #19
          Originally posted by marek View Post
          Nexuiz menu -> Settings -> Video -> Use OpenGL 2.0 shaders (GLSL)
          Thanks, i see that is application specific option.

          Comment


          • #20
            Originally posted by monraaf View Post
            At least vdrift supports automated benchmarking and I believe you have used it in the past for benchmarking. So why you not use it anymore?
            Yeah, I wrote part of the VDrift benchmarking code in the game, but It was too slow to run on the RV515.
            Michael Larabel
            http://www.michaellarabel.com/

            Comment


            • #21
              Originally posted by marek View Post
              Nexuiz should be a lot faster if you enable GLSL.
              Yes, I was wondered why this Nexuiz benchmark did show regression.

              I've tested that enabling GLSL in Nexuiz on r300g brought almost twice the performance of r300 in most places, especially seen on maps/places where r300 had performance drops - tested on my RV350. The performance gain in Xonotic is visible, too.

              Comment


              • #22
                And I'm wondering why distro developers kill r300 driver in favour r300g.
                It's still usefull to test if r300g haven't brought regressions so there should be packages with classic Mesa drivers in main repositories, too.
                For me it's very usefull to have two drivers and few their versions in separate directories for testing. It's so simple now as disabling desktop effects and setting variable for driver preload starting game or other application.

                Comment


                • #23
                  There was discussion about including Spring RTS in another thread. The open question is whether the games have a scriptable benchmark mode.

                  Comment


                  • #24
                    Originally posted by xeros View Post
                    And I'm wondering why distro developers kill r300 driver in favour r300g.
                    It's still usefull to test if r300g haven't brought regressions so there should be packages with classic Mesa drivers in main repositories, too.
                    For me it's very usefull to have two drivers and few their versions in separate directories for testing. It's so simple now as disabling desktop effects and setting variable for driver preload starting game or other application.
                    Agreed. A simple export command on the command line makes a difference will a windows game work or not. I still have to use classic driver, wine games simply do not work with gallium.

                    Comment


                    • #25
                      What about r700? Why is my GPU always left out T_T

                      Comment


                      • #26
                        There is a 600g driver as well, which currently supports r6xx, r7xx and Evergreen. It started later than 300g but is catching up fast.

                        Comment


                        • #27
                          Originally posted by bridgman View Post
                          There is a 600g driver as well, which currently supports r6xx, r7xx and Evergreen. It started later than 300g but is catching up fast.
                          Reading the commit statements from Arlied, it sounds like r600g is supposed to be about on par with the classic driver already, and Evergreen should be pretty much working as well. I'm sure it hasn't been tested nearly as much, though, so there are probably more bugs to be found.

                          Comment


                          • #28
                            Originally posted by pejakm View Post
                            Agreed. A simple export command on the command line makes a difference will a windows game work or not. I still have to use classic driver, wine games simply do not work with gallium.
                            That seems fixed in master but not in 7.9:
                            https://bugs.freedesktop.org/show_bug.cgi?id=30011
                            or am I missing something?

                            Comment


                            • #29
                              Originally posted by Michael View Post
                              Yeah, I wrote part of the VDrift benchmarking code in the game, but It was too slow to run on the RV515.
                              why not wrote a part of an spring engine benchmark code ?

                              be a hero

                              Comment


                              • #30
                                The last thing I'd like to see in the r300g driver is support for the force_s3tc_enable in .drirc/env variable. As I wrote at:
                                http://www.phoronix.com/forums/showthread.php?t=26472
                                games are starting to use this trick to force the S3TC extension (when they only use decompression), and while this works perfectly with r300c it doesn't work with r300g. Forcing thousands of users to install libtxc_dxtn.so is not an easy solution (especially since distributions don't usually provide packages for it), especially if it's technically not really needed.

                                Comment

                                Working...
                                X