Announcement

Collapse
No announcement yet.

ATI R600g Gains Mip-Map, Face Culling Support

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

  • Originally posted by bridgman View Post
    One essential part of holding something back is, well, holding it back. I'm not going to give you a list of the stuff we *didn't* release
    telling the name of an kind of technique is not the same as telling the secrets of the technique itself.

    exampel you can say its a electric car and this does not explain how a el. car is working and how its build.

    so yes i'm sorry about the dark secrets of sabotaging FOSS.

    Comment


    • Sure, but by your analogy we're not holding back "an electric car" we're holding back small, non-critical options in the hybrid drivetrain management software.

      Comment


      • Git log hints ioquake might possibly work. Just echoing.

        Comment


        • Originally posted by bridgman View Post
          Sure, but by your analogy we're not holding back "an electric car" we're holding back small, non-critical options in the hybrid drivetrain management software.
          ok but being better and faster is critical for FOSS ;-)

          on my system i can feel it...

          1 day ago i install the fglrx again for testing after long time in 32bit linux
          and if i scroll websites vertical the letters corrupted so you can't read.



          i can feel it :-)

          the radeon open-source driver works perfect ;-)


          i think amd hurts them self by holding spec informations back for 100% speed.

          Comment


          • Originally posted by bridgman View Post
            Did I mention how much I hate having to delete and re-post every time I want to edit something ?
            Maybe you should ask Micheal for mod privileges...

            Comment


            • Q3 now works without glitches and even compiz now seems to work fine (didnt test all the plugins, especialy those with heavy shader usage)

              Comment


              • Well, found a bug, hope Glisse reads this thread sometimes

                Comment


                • Originally posted by droidhacker View Post
                  He probably worded the question precisely to ask both things.
                  Right i ask for both situations.

                  Originally posted by droidhacker View Post
                  I suspect that he knows what he's saying a lot better than he makes it look.
                  sometimes i know this... yes..

                  Originally posted by droidhacker View Post
                  Q has a very mischievous streak.
                  o well on what fineness did you detect this ?

                  and yes i have a mischievous streak.

                  Comment


                  • Originally posted by netkas View Post
                    Well, found a bug, hope Glisse reads this thread sometimes
                    Seems to be broken in classic Mesa as well. *Eek*

                    Comment


                    • Yeah, right now I think something like 96% of the 3D driver is common Mesa code and 4% is classic HW driver for whatever HW you are running.

                      After the move to Gallium3D I guess that will become more like 98% common and 2% hardware-specific

                      Comment


                      • Actually it looks a bit odd with Software Rasterizer as well. Could someone check whether or not geartrain polygons are valid? (edges not allowed to intersect, region must be convex) If some are invalid, it would explain strange rendering. I'm not experienced enough to just see validity by scanning through the code.

                        Comment


                        • Originally posted by netkas View Post
                          Well, found a bug, hope Glisse reads this thread sometimes
                          This is most probably not a driver bug. swrast, llvmpipe, softpipe, r300c, and r300g render it the same as is on your screenshot.

                          Comment


                          • Originally posted by marek View Post
                            This is most probably not a driver bug. swrast, llvmpipe, softpipe, r300c, and r300g render it the same as is on your screenshot.
                            My eyes claimed swrast rendering differed a bit but was still incorrect. Hence why I started wondering about invalid polygons since rendering is undefined there and might even be unexpected in a different way in all drivers.

                            Comment


                            • Yeah, we are damned lucky that the hardware doesn't lock up (that's what usually "undefined" means).

                              Comment


                              • somebody need to check it on nvidia linux drivers.

                                Comment

                                Working...
                                X