Announcement

Collapse
No announcement yet.

ATI R500: Mesa vs. Catalyst Benchmarking

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

  • #16
    Originally posted by l8gravely View Post
    X1300 MESA ------------------
    X1300 fglrx ==================================
    X1850 MESA ------------------------
    X1800 flgrx ================================================
    Actually the graphs was ordered as

    X1300 MESA ------------------
    X1850 MESA ------------------------
    X1300 fglrx ==================================
    X1800 flgrx ================================================

    which I felt was very confusing, as this suggests that you should compare the MESA with each other and not MESA vs flgrx.

    Otherwise I think article was perfect! I love the Phoronix articles!

    Comment


    • #17
      Originally posted by Louise View Post
      Actually the graphs was ordered as

      X1300 MESA ------------------
      X1850 MESA ------------------------
      X1300 fglrx ==================================
      X1800 flgrx ================================================

      which I felt was very confusing, as this suggests that you should compare the MESA with each other and not MESA vs flgrx.

      Otherwise I think article was perfect! I love the Phoronix articles!
      That's what I was trying to get across, that the graphs could have used color, orientation and better organization to showcase the differences more easily. Since we read (most of us) Left to Right, it would make sense to have the graphs laid out in the same orientation. Those big, phat^Wfat, wide bars drive me crazy.

      Now don't get me wrong, I enjoy the articles and I think they're doing a great service here for all of us OSS fans and AMD/ATI fans. I purposefully picked this hardware becase of the open docs. Sorry nVidia, you're not in the running...

      John

      Comment


      • #18
        how about some compiz benchmarks? I find compiz much smoother on MESA as compared to FGLRX

        Comment


        • #19
          Originally posted by Extreme Coder View Post
          Michael, for the games that didn't work, was it because of the unavailability of S3TC (libtxc-dxtn) ? Because the same games that didn't work here didn't work with the OSS driver on my Radeon 9200 SE until I added the S3TC support library.
          Doom3demo works without S3TC on my 9250 with ati radeon driver.

          Comment


          • #20
            Nexuiz in fact is very sensitive to how the VBO support behaves. At least some months ago on my Radeon mobility 9000 with the radeon driver it would usually help to disable usage of VBOs in Nexuiz (gl_vbo 0). There are plenty of values to try:

            gl_vbo : "3" ("3") : make use of GL_ARB_vertex_buffer_object extension to store static geometry in video memory for faster rendering, 0 disables VBO allocation or use, 1 enables VBOs for vertex and triangle data, 2 only for vertex data, 3 for vertex data and triangle data of simple meshes (ones with only one surface)
            Plus notice that without GLSL support Nexuiz will have most "advanced" effects disabled, running with a fixed-pipeline "fallback". At least my Radeon 3850 is actually *slower* with that fixed-pipeline renderer than with the visually more advanced GLSL renderer, so results are easily skewed depending on what capabilities a driver offers.

            Comment

            Working...
            X