Page 4 of 4 FirstFirst ... 234
Results 31 to 39 of 39

Thread: Is AMD's New 2D Acceleration Architecture Still Slow?

  1. #31
    Join Date
    Aug 2007
    Posts
    6,679

    Default

    You must really love ATI when that does not annoy you.

  2. #32
    Join Date
    Dec 2008
    Posts
    1,002

    Default

    I don't have any graphics corruption in Firefox or any other app. I did however have a couple of spontaneous reboots, mostly triggered by switching or closing a Firefox tab. I don't know if this is a general driver issue or only triggered by the new 2d accel code paths. But I've disabled the new 2D accel code for now.

    On a positive note. The gstreamer-gl plugin from git now works correctly with this Catalyst release. So it's now possible to have tear-free video with gstreamer based video players and fglrx.

  3. #33
    Join Date
    Oct 2007
    Posts
    912

    Default

    I have some issues with firefox, and pretty much well anything gtk actually, notably when scrolling, but only on the secondary monitor (running 2 X servers, no xinerama or expanded desktop or anything). No black patches, but large areas of "blank" (grey, white, whatever is the background colour) until the window is refreshed (switching virtual desktops will fix it, until I scroll again).
    This is with E16, gentoo 64bit, hd3650, kernel 2.6.32 and xorg-server 1.7.6 (from memory, I'm tired and not at my own computer right now). No compositing enabled.

  4. #34
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by Kano View Post
    Did you really see a driver that works with KDE 4 correctly with the new accelleration active? I really think to disable it by default, because it only causes problems with gtk2 apps. Maybe it was tested with gnome (hint: ubuntu) only.
    "Did you really see a driver that works with KDE 4 correctly with the new accelleration active?"

    i use it. day for day. what is your problem ? black-windows bug? i know to 'control' it for me there is no problem.

  5. #35
    Join Date
    Aug 2007
    Posts
    6,679

    Default

    For me it's an annoying bug. But you are an ati fanboy...

  6. #36

    Default

    Quote Originally Posted by Kano View Post
    You must really love ATI when that does not annoy you.
    i'm not gonna lie, i am a rather large AMD fan, but honestly, its not something that really affects my computer using habbits in anyway, so the source of the bug being from ati is not related to the fact that it doesn't really annoy me.

    i suppose i should qualify that "a second" was figurative, literally speaking, it is more of an instant flash from normal-black-normal.

  7. #37
    Join Date
    Nov 2008
    Location
    Germany
    Posts
    5,411

    Default

    Quote Originally Posted by Kano View Post
    For me it's an annoying bug. But you are an ati fanboy...
    i do not have the bug anymore. i fixed that!

  8. #38
    Join Date
    Jun 2009
    Posts
    1,191

    Talking

    Quote Originally Posted by Kano View Post
    Did you really see a driver that works with KDE 4 correctly with the new accelleration active? I really think to disable it by default, because it only causes problems with gtk2 apps. Maybe it was tested with gnome (hint: ubuntu) only.
    yeah i think is still too buggy for everyday use, especially if you use kde4 and gtk apps (yeah same problem, i thougth it was only me yeah im not crazy).

    about the ubuntu only is pretty posible i concur.

    so far only the FOSS driver render perfectly kde4 99.99% of the time,mmm in the fglrx side i dont remember if ever existed such a driver.

    ohh, anyone noticed that enable full vsync in the control center hang the X and after the ovbious restart your 3d performance goes to hell?(NOT with glxgears, i mean comparing unigine tropics bench after and before)(i know with vsync i wont get 400 fps, duh!)(i mean 58~ before vsync ~32 after vsync)(yeah unigine tropics is nasty at full settings) (yeah my monitor is set at 85 not 32 or 30)

    anyway at least is nice to see that some QA is beggining to appear in the drivers, beside the ovbious this drivers screw less things that were working fine before than most previous driver release i remember, so +1 for the lonely guy at amd's basement

    another one, anyone noticed that many shaders operation in wine with fglrx are heavily corrupted? ill post some screen later to figure out if it is fglrx regresion or wine

  9. #39
    Join Date
    Jul 2010
    Posts
    1

    Default Pixbufs

    I would have liked to have seen a Pixbufs benchmark - that is where the catalyst driver was notably poor in previous tests, and helps to explain the real-world perception of improvement I think (e.g. things like scrolling).

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •