Page 3 of 6 FirstFirst 12345 ... LastLast
Results 21 to 30 of 51

Thread: AMD Catalyst 13.9 Final

  1. #21

    Default

    Quote Originally Posted by deri View Post
    you should report those issues on somewhere? Reporting memory leaks on valve git would be a start.
    The memory leaks in Source games and xvba playback exist since 13.8 beta was first released. Im pretty sure they know about them as it affects Steam's most prevalent 3d engine. What im surprised about is that they released an official driver that has these big bugs.

  2. #22
    Join Date
    May 2009
    Posts
    96

    Default

    Correct me if I'm wrong, but I think steam and steam games related bugs/issues should be reported here: http://devgurus.amd.com/community/steam-linux
    However, as a reporter myself I don't see too much activity there...

  3. #23
    Join Date
    Jul 2013
    Posts
    36

    Default

    I have dota and steam for linux gits open I see quite much activity on the dota2. Somebody comments on your issues quite fast. The valve forum for linux has become quite silent place. It feels like that there are less than 100 people reading and writing things.

  4. #24
    Join Date
    Feb 2011
    Posts
    163

    Default

    That does not help much. The vsync bug (100% load on one core) was in the driver since October 2012 :-) We then worked actively with AMD devs, via beta mailinglist and whatever, to get that solved - it was solved with 13.6 - and reintroduced in 13.8beta with a nice additional memleak :-)

    I just gave up. I won't install a catalyst anymore. XVBA development is _stopped_ we did not thing in the code for more than 6 months, as we get no new SDK and users blame us for memleak and bad drivers.

    I will go with the free drivers for now. Xbmc is not yet ready on OSS UVD - but we are working on a solution - especially the really helpful AMD OSS guys put a lot of effort into their driver / mesa development to get the performance issues we currently have, fixed.

    XVBA will be obsolete.

  5. #25
    Join Date
    Feb 2010
    Posts
    519

    Default

    Those of you having issues with Unity reverting to 2D:
    1. Are you on 64bit?
    2. Have you installed the drivers from a tty with X.org shut down? (sudo service lightdm stop)
    3. Have you issued "sudo rm /etc/ati/amdpscdb" before rebooting?

  6. #26

    Default

    Quote Originally Posted by PsynoKhi0 View Post
    Those of you having issues with Unity reverting to 2D:
    1. Are you on 64bit?
    2. Have you installed the drivers from a tty with X.org shut down? (sudo service lightdm stop)
    3. Have you issued "sudo rm /etc/ati/amdpscdb" before rebooting?
    1. yes
    2. no
    3. stopped lightdm, rm, restart without change.

  7. #27

    Default

    Quote Originally Posted by fritsch View Post

    I will go with the free drivers for now. Xbmc is not yet ready on OSS UVD - but we are working on a solution - especially the really helpful AMD OSS guys put a lot of effort into their driver / mesa development to get the performance issues we currently have, fixed.

    XVBA will be obsolete.
    Is any other native xvba speaking player out there for catalyst users? Or no more hw decoding for them?

    Also, vdpau works quite well with mplayer and gnome-mplayer (but doesnt get along with smplayer) - why doesnt it with xbmc?

  8. #28
    Join Date
    Feb 2011
    Posts
    163

    Default

    Short answer: xbmc is OpenGL, fully 3D

    There is no way to get the surfaces back to OpenGL, than via pixmaps. This was fast enough for ION-1s and ION-2s, but it is not for the radeons.

    Xbmc has a second way to handle that problem. Proprietary nvidia implements glinterop, which is currently also adapted for mesa but not there yet.

    Basically playing a video in mplayer is far more easy than doing it in an OpenGL App, when there is no real api call to get the rendering target transfered (fast).

    XVBA will die. We were the one and only application that implemented it. There is nothing else in the OSS world that uses it - despite the 2 years old not maintained anymore xvba-va-driver.

  9. #29
    Join Date
    Jun 2011
    Posts
    38

    Default

    Quote Originally Posted by fritsch View Post
    That does not help much. The vsync bug (100% load on one core) was in the driver since October 2012 :-) We then worked actively with AMD devs, via beta mailinglist and whatever, to get that solved - it was solved with 13.6 - and reintroduced in 13.8beta with a nice additional memleak :-)

    I just gave up. I won't install a catalyst anymore. XVBA development is _stopped_ we did not thing in the code for more than 6 months, as we get no new SDK and users blame us for memleak and bad drivers.

    I will go with the free drivers for now. Xbmc is not yet ready on OSS UVD - but we are working on a solution - especially the really helpful AMD OSS guys put a lot of effort into their driver / mesa development to get the performance issues we currently have, fixed.

    XVBA will be obsolete.
    excited to see XBMC with open source UVD this will be great. My linux experience is so better off with Linux 3.11 and Mesa 9.2 (which Fedora guys generously pushed in Fedora 20) than it was ever with stupid buggy catalyst Thank you Also VDPAU >>> XVBA

    Even flash supports VDPAU lol :P

  10. #30
    Join Date
    Aug 2007
    Posts
    6,673

    Default

    It's very hard NOT to see memory leaks with L4D2 and other source engine games - maybe the dev boxes just have too much ram compared to home users that it does not crash so fast - you can see the memory leak with htop easyly. It is more or less impossible that one of those fglrx devs plays with AMD gfx cards with Steam/Linux. Tell me one...

Posting Permissions

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