Announcement

Collapse
No announcement yet.

ati catalyst 10.6 released

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

  • #31
    The new 2D acceleration architecture is really nice, isn't it

    Comment


    • #32
      I can't try it because I'm on X server 1.8, but does VSync work now when watching movies in a window? (Without disabling desktop effects of course.)

      Any Xv improvements or does it still suck ass?

      Comment


      • #33
        I have the same exact question as RealNC. Are the VSync problems fixed?

        Have they been fixed for HD5xxx cards? Tearing fixed? When you guys comment and say direct2D is awesome, what do you mean? Are you playing 2D games or are you talking about moving windows? Playing videos?

        Thanks

        Comment


        • #34
          Originally posted by RealNC View Post
          I can't try it because I'm on X server 1.8, but does VSync work now when watching movies in a window? (Without disabling desktop effects of course.)

          Any Xv improvements or does it still suck ass?
          VSync works well for me now but I have not tried Xv output; only OpenGL with VA-API. The 2D acceleration works very well and I'm pleasantly surprised! This is an excellent b-day gift. Thanks AMD

          Comment


          • #35
            Originally posted by RealNC View Post
            I can't try it because I'm on X server 1.8, but does VSync work now when watching movies in a window? (Without disabling desktop effects of course.)

            Any Xv improvements or does it still suck ass?
            10-7 can handle Xserver1.8

            ;-)

            Comment


            • #36
              Originally posted by DivineGrace View Post
              VSync works well for me now but I have not tried Xv output; only OpenGL with VA-API. The 2D acceleration works very well and I'm pleasantly surprised! This is an excellent b-day gift. Thanks AMD
              Happy birthday

              /sleep

              Comment


              • #37
                Hmmm... I didn't notice much improvement to the tearing. It has minimized a bit (or maybe this is the sugar-pill effect).

                There is a certain issue I'm suffering from that's annoying me these past couple of days. I have a dual-LCD monitor setup. If play a video on my primary LCD screen, I get no tearing (gl output). If I play on my secondary screen, I get tearing (single line in the middle of the screen if full screen).

                Anyone experienced this? Have any suggestions?

                My xorg.conf:
                Code:
                Section "ServerLayout"
                	Identifier     "aticonfig Layout"
                	Screen      0  "aticonfig-Screen[0]-0" 0 0
                EndSection
                
                Section "Files"
                EndSection
                
                Section "Module"
                	Load  "glx"
                EndSection
                
                Section "ServerFlags"
                	Option	    "Xinerama" "off"
                EndSection
                
                Section "Monitor"
                	Identifier   "aticonfig-Monitor[0]-0"
                	Option	    "VendorName" "ATI Proprietary Driver"
                	Option	    "ModelName" "Generic Autodetecting Monitor"
                	Option	    "DPMS" "true"
                EndSection
                
                Section "Monitor"
                	Identifier   "0-DFP3"
                	Option	    "VendorName" "ATI Proprietary Driver"
                	Option	    "ModelName" "Generic Autodetecting Monitor"
                	Option	    "DPMS" "true"
                	Option	    "PreferredMode" "1920x1080"
                	Option	    "TargetRefresh" "60"
                	Option	    "Position" "0 0"
                	Option	    "Rotate" "normal"
                	Option	    "Disable" "false"
                EndSection
                
                Section "Monitor"
                	Identifier   "0-DFP4"
                	Option	    "VendorName" "ATI Proprietary Driver"
                	Option	    "ModelName" "Generic Autodetecting Monitor"
                	Option	    "DPMS" "true"
                	Option	    "PreferredMode" "1920x1080"
                	Option	    "TargetRefresh" "60"
                	Option	    "Position" "1920 0"
                	Option	    "Rotate" "normal"
                	Option	    "Disable" "false"
                EndSection
                
                Section "Device"
                	Identifier  "aticonfig-Device[0]-0"
                	Driver      "fglrx"
                	Option	    "Monitor-DFP3" "0-DFP3"
                	Option	    "Monitor-DFP4" "0-DFP4"
                	Option	    "TexturedVideoSync" "on"
                	Option	    "Capabilities" "0x00000800"
                	BusID       "PCI:2:0:0"
                EndSection
                
                Section "Screen"
                	Identifier "aticonfig-Screen[0]-0"
                	Device     "aticonfig-Device[0]-0"
                	DefaultDepth     24
                	SubSection "Display"
                		Viewport   0 0
                		Virtual   3840 3840
                		Depth     24
                	EndSubSection
                EndSection
                ----

                Comment


                • #38
                  My script ( http://kanotix.com/files/install-fglrx-debian.sh ) adds .34 support because ATI was too stupid to add 1 extra line!!! The driver has got a serious regression however compared to 10-5. You don't see that with newer Xservers, but with Kanotix Excalibur (Xserver 1.4.2) you do.

                  With default settings you can run and stop fgl_glxgears without problems, but when you force vsync then you have got ghost images. It seems nobody tests vsync on by default, which is really bad, as you always have to force that...

                  Comment


                  • #39
                    Originally posted by emergence View Post
                    Hmmm... I didn't notice much improvement to the tearing. It has minimized a bit (or maybe this is the sugar-pill effect).

                    There is a certain issue I'm suffering from that's annoying me these past couple of days. I have a dual-LCD monitor setup. If play a video on my primary LCD screen, I get no tearing (gl output). If I play on my secondary screen, I get tearing (single line in the middle of the screen if full screen).

                    Anyone experienced this? Have any suggestions?
                    Are they both the same make and model of screen? If they're not both exactly the same refresh rate then you will get this.

                    Comment


                    • #40
                      Disappointing that there is still no working vsync for compiz/windowed videos, but on to the good, with d2d performance is improved all across the board on my mobility 2600. Especially scrolling in web browsers (chrome, fx, opera)

                      Comment


                      • #41
                        Originally posted by mugginz View Post
                        Are they both the same make and model of screen? If they're not both exactly the same refresh rate then you will get this.
                        Yeah, same exact model.

                        Comment


                        • #42
                          Originally posted by emergence View Post
                          Yeah, same exact model.
                          Ooh, that doesn't sound good.

                          Can you confirm they're both at the same refresh rate via the screens own menu systems?

                          Comment


                          • #43
                            I seem to be having some strange issues with this new driver.

                            When running sacred overworld with wine the letter W or Y looks completely white like a brick, the letter picked seems to be random.

                            This doesn't happen with Catalyst 10.5. I couldn't find anywhere else where something like this happens in my everyday use, but I'll keep looking.

                            (Sorry for my bad English)

                            Comment


                            • #44
                              Looking good for me except that googleearth crashes on startup:

                              Stacktrace from glibc:
                              /usr/lib32/googleearth/googleearth-bin[0x805caa6]
                              [0xf777e400]
                              /lib32/libc.so.6(abort+0x182)[0xf5a29d52]
                              /lib32/libc.so.6(__assert_fail+0xf8)[0xf5a1f788]
                              /usr/lib32/libX11.so.6(_XReply+0x322)[0xf52dd1d2]
                              /usr/lib32/libGL.so.1(AtiCallFGLComposite+0xf5)[0xf4cff88b]

                              Anyone else having this trouble? I'm running Ubuntu 10.4 and problem occurs whether or not Compiz is enabled.

                              Comment


                              • #45
                                Originally posted by alphacrucis2 View Post
                                Looking good for me except that googleearth crashes on startup:

                                Stacktrace from glibc:
                                /usr/lib32/googleearth/googleearth-bin[0x805caa6]
                                [0xf777e400]
                                /lib32/libc.so.6(abort+0x182)[0xf5a29d52]
                                /lib32/libc.so.6(__assert_fail+0xf8)[0xf5a1f788]
                                /usr/lib32/libX11.so.6(_XReply+0x322)[0xf52dd1d2]
                                /usr/lib32/libGL.so.1(AtiCallFGLComposite+0xf5)[0xf4cff88b]

                                Anyone else having this trouble? I'm running Ubuntu 10.4 and problem occurs whether or not Compiz is enabled.
                                OK the problem appears to be that I followed the Ubuntu binary driver howto which it appears missed something in the install. Not sure why only googleearth was affected as Stellarium was fine. Tried reinstalling Catalyst 10.6 via the method in the AMD instructions on the web site and googleearth is now happy.

                                Comment

                                Working...
                                X