Page 5 of 5 FirstFirst ... 345
Results 41 to 50 of 50

Thread: AMD Catalyst vs. NVIDIA OpenCL Performance

  1. #41
    Join Date
    Oct 2010
    Location
    Amsterdam
    Posts
    295

    Default

    Quote Originally Posted by haplo602 View Post
    Oh, that's an attemp at a joke right ?

    AMD drivers are poor in stability and CONSISTENCY. Bugs that were fixed do appear again randomly in new releases. Things stop working for no apparent reason (I get no VTs on my system with any catalyst past 13.1). Full blown video acceleration is missing (there are parts working at times). Wine compatibility is a separate chapter.

    And I have a Radeon HD5830 in my PC, considering switching to Nvidia just to get Wine and video accell working properly.
    My hd5750 1 gig, has some issues in Serious Sam 3, but its rock stable on linux and windows.

    I do not use wine, maybe wine is the problem.

  2. #42
    Join Date
    Nov 2007
    Posts
    1,353

    Default

    Quote Originally Posted by Gps4l View Post
    My hd5750 1 gig, has some issues in Serious Sam 3, but its rock stable on linux and windows.

    I do not use wine, maybe wine is the problem.
    My understanding of wine is that it uses some opengl features in a way that isnt standards compliant but works well regardless on nvidias proprietary drivers. It has definitely improved ALOT in the last few years though, and the OSS drivers are handling wines issues better.

    I don't understand the exact details of what wines issues are. They are a bit over my head. Some people say that the problem is with mesa being too strict. But personally I think strictness is good, and wine not being strict is the root of the problem.
    Last edited by duby229; 07-02-2013 at 10:24 PM.

  3. #43
    Join Date
    Nov 2007
    Posts
    1,353

    Default

    4th og july celebration started a little early this year, so forgive me if I'm not making sense. kinda drunk. 151 is some shit.

  4. #44
    Join Date
    Sep 2007
    Posts
    327

    Default

    Quote Originally Posted by duby229 View Post
    My understanding of wine is that it uses some opengl features in a way that isnt standards compliant but works well regardless on nvidias proprietary drivers. It has definitely improved ALOT in the last few years though, and the OSS drivers are handling wines issues better.

    I don't understand the exact details of what wines issues are. They are a bit over my head. Some people say that the problem is with mesa being too strict. But personally I think strictness is good, and wine not being strict is the root of the problem.
    The problem is, that NVIDIA's driver works with programs, which are not 100% standard conform. fglrx and mesa are not that easygoing.

  5. #45
    Join Date
    Nov 2007
    Posts
    1,353

    Default

    Quote Originally Posted by oleid View Post
    The problem is, that NVIDIA's driver works with programs, which are not 100% standard conform. fglrx and mesa are not that easygoing.
    Well yeah, I can see that as being a good thing for people who have nVidia cards. For everyone else that uses OSS drivers it is a bad thing. The proper solution is for wine to better conform to opengl standards. The problem is not that mesa is strict, it's that wine isnt.
    Last edited by duby229; 07-03-2013 at 01:33 AM.

  6. #46
    Join Date
    Aug 2012
    Posts
    409

    Default

    It isn't just wine, even Valve's port of the Source engine to Linux is optimized towards NVIDIA proprietary blobs. Just recently we got to the bottom of a serious at the Steam for Linux github with Valve on the horrid performance and input lag of, especially, their multiplayer titles like TF2. The culprit is they are relying on a feature not in OpenGL specifications that NVIDIA drivers perform. NVIDIA has the desktop market cornered with around 70% of graphics cards being NVIDIA, so most games are being optimized towards NVIDIA binary blobs.

  7. #47
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,185

    Default

    Link please? Google gives several dozen input lag tickets on valve's github.

  8. #48
    Join Date
    Aug 2012
    Posts
    409

    Default

    Quote Originally Posted by curaga View Post
    Link please? Google gives several dozen input lag tickets on valve's github.
    https://github.com/ValveSoftware/Sou...mes/issues/765

  9. #49
    Join Date
    Feb 2008
    Location
    Linuxland
    Posts
    5,185

    Default

    There was nothing Nvidia-specific there. The issue in that ticket is AMD's fault, a legal optimization gone wrong.

  10. #50
    Join Date
    Oct 2010
    Location
    Amsterdam
    Posts
    295

    Default

    Quote Originally Posted by mmstick View Post
    It isn't just wine, even Valve's port of the Source engine to Linux is optimized towards NVIDIA proprietary blobs. Just recently we got to the bottom of a serious at the Steam for Linux github with Valve on the horrid performance and input lag of, especially, their multiplayer titles like TF2. The culprit is they are relying on a feature not in OpenGL specifications that NVIDIA drivers perform. NVIDIA has the desktop market cornered with around 70% of graphics cards being NVIDIA, so most games are being optimized towards NVIDIA binary blobs.
    Unless TF2 has regressed this can't be right.

    With my amd card its a smooth on linux as it is on windows.

    hd5750 amd phenom II X4

    Nvidia has a lead over amd performance wise, with openGl but Valve is talking with amd too.

    And amd is talking with game developers, like croteam ( serious sam )

    There will be games released were we will be greeted by and amd logo.

    We do not know the future, but for now steam coming to linux is one of the best things ever for linux.
    Even Richard Stallman said it might be a good thing for Linux.

    http://www.muktware.com/4042/richard...-good-gnulinux

Posting Permissions

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