Announcement

Collapse
No announcement yet.

For Radeon Gamers On Ubuntu 20.04 LTS, It's Generally Worthwhile Flipping On RADV's ACO

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

  • TemplarGR
    replied
    Originally posted by randomsalad View Post
    It's not just performance you gain, but also compatibility. A lot of very popular games will show severe visual artifacts when using the LLVM shader backend. In my experience, GTAV and Assassin's Creed Odyssey were two games that were giving me a lot of trouble with incorrect shading making the games unplayable in practice, but switching to ACO (the shader backend, not the game) made these problems go away.
    I wonder if ACO will be the solution for broken Ambient Occlusion on some games with the radeonsi driver. Mainly Unity games like Two Point Hospital and Parkitect have artifacts with Ambient Occlusion on. Yesterday i tried The Colonists and Ambient Occlusion makes the whole screen very dark, it gets fixed when disabled. For Two Point Hospital and Parkitect the fix is to disable DCC with "AMD_DEBUG=nodcc" (although obviously this would cost some performance). But i am not aware of how DCC is implemented. Perhaps it uses shaders in some capacity? Or perhaps the ambient occlusion shader has incompatibilities with DCC on radeonsi? This issue is not present on Windows with Adrenaline drivers.

    In any case, can't wait for ACO to come to radeonSI.

    Leave a comment:


  • wizard69
    replied
    Originally posted by enlar View Post
    Article needs a short explanation about what ACO is... ;-)
    Yeah, there is this assumption that ever acronym is well known in the Linux world. GPU driver technology is a bushel basket full of such acronyms. Even a link would do.

    Leave a comment:


  • randomsalad
    replied
    It's not just performance you gain, but also compatibility. A lot of very popular games will show severe visual artifacts when using the LLVM shader backend. In my experience, GTAV and Assassin's Creed Odyssey were two games that were giving me a lot of trouble with incorrect shading making the games unplayable in practice, but switching to ACO (the shader backend, not the game) made these problems go away.

    Leave a comment:


  • enlar
    replied
    Article needs a short explanation about what ACO is... ;-)

    Leave a comment:


  • oibaf
    replied
    Originally posted by CochainComplex View Post

    Sorry I missed the point that he uses your repo. Thank you for reminding!
    Btw is your repo still build against llvm9. I mean is the bug with llvm10 and opencl still existing? at the moment I'm building it against 10 but without opencl.
    My repo still uses llvm9, 10 it's still broken, but there is a pending patch:

    ​​​When properly merged I'll build against llvm10.

    Leave a comment:


  • Brisse
    replied
    I've been using ACO for everything for months, and besides an issue with Wolfenstein II: The New Colossus back in Mesa 19.3 (fixed in 20.0), I haven't run into any noticeable issues at all. It's been very solid and I suggest everyone should try to enable it system wide. In the rare case you run into a troublesome game, you can always set 'RADV_PERFTEST=llvm' for that particular game.

    Leave a comment:


  • CochainComplex
    replied
    Originally posted by ntropy View Post

    Thats true. Cant wait for SC to go for multi-threaded Vulkan support that will be a massive fps gain.

    I have set aco to be enabled in the system path around the time when it was released and not even merged to mesa. After the initial release phase with some bugs, I have had no issues at all ever since. Where nvidia users often struggle to get a certain game running, for me its all just plug and play. Its pretty amazing and no difference to windows gaming anymore. Except that sometimes it is even running faster on Linux.
    I can confirm that. Super smooth gaming under linux with navi10 and mesa+aco.

    Leave a comment:


  • CochainComplex
    replied
    Originally posted by oibaf View Post

    Mesa in my PPA is already built with LTO.
    Sorry I missed the point that he uses your repo. Thank you for reminding!
    Btw is your repo still build against llvm9. I mean is the bug with llvm10 and opencl still existing? at the moment I'm building it against 10 but without opencl.

    Leave a comment:


  • oibaf
    replied
    Originally posted by CochainComplex View Post
    always feel glad to see the progress of mesa and navi 10 - very nice benchmark. Michael it would be interesting to see the same benchmark with 20.1 +aco build with lto flag.
    Mesa in my PPA is already built with LTO.

    Leave a comment:


  • Tuxee
    replied
    Interesting. When Running the ROTR benchmark on my RX5700 setup on 20.04 with stock kernel 5.4 and mesa I get around 70fps. Switching to mainline kernel the fps jump to 130 - 140fps. Both times without ACO. That's my biggest gripe with AMD - while my 3700X has been a joy, my Navi10 experience has been more or less an ongoing disaster since I bought it last October.

    Leave a comment:

Working...
X