Radeon Software Adrenalin 2020 Edition 21.1.1 Download & Discussion

Discussion in 'Videocards - AMD Radeon Drivers Section' started by ninja750, Jan 21, 2021.

  1. itpro

    itpro Master Guru

    Messages:
    931
    Likes Received:
    505
    GPU:
    Radeon Technologies
    10bit pixel format and 10bpc are entirely different. You compare true 1billion color depth vs 16,7million colors simulating 10 bit. So, it doesn't work. It isn't nice to use a professional output setting for gaming.
     
    passenger likes this.
  2. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    17,405
    Likes Received:
    2,759
    GPU:
    MSI 6800 "Vanilla"
    Oh so that's why the VRAM overclock causes a small flicker effect even with minimal changes.
    (~1Mhz or so depending on what the slider rounds up to in advanced mode being enough.)

    EDIT: Rather that's why the Radeon Settings software (Entire screen perhaps.) seem to flicker a bit when hitting the "Apply" button with the VRAM overclock active.
    (Or loading a profile or anything that also takes effect and involves modifying the VRAM values.)
     
  3. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    15,310
    Likes Received:
    2,610
    Yep. That's a result of Overdrive8 API unification, previously AMD had separate calls for changing clocks, power limit, fan speeds etc. But with Overdrive8 somebody @ AMD decided that is is a good idea to combine functions for applying absolutely any settings into a signle API call. So there is one uber function that can apply everything. It won't be a problem if it was working properly and at least it seem to be initially designed properly: there are requested flags allowing the caller to mark requested properties and tell this function what exactly you're going to change: fan speeds, clocks or anything else. However there seem to be a bug inside the implementation, which is ignoring requested properties mask and reapply everything as soon as VRAM clock is above default. This causes this flicker, it is quite normal to see it when applying new memory clock but it does full memory re-overclocking way each time even when you change anything else. This also delays this function call drastically. Hope to see it fixed one day.
     
  4. OnnA

    OnnA Ancient Guru

    Messages:
    12,741
    Likes Received:
    3,171
    GPU:
    Vega XTX LiQuiD
    Yup, my monitor is also OC'ed and is still 10Bit + Freesync at edited range of 30-75FPS
    Original = 70Hz FS 48-70 10Bit 1440p
    CRU = 71Hz FS 30-75 10Bit 1440p

    OC can go up to 74Hz but w/8Bit so i don't want it that way ;)
     

  5. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    17,405
    Likes Received:
    2,759
    GPU:
    MSI 6800 "Vanilla"
    Some of the PowerPlay functionality and this Overdrive API and settings can't be good to keep combined in this way easiest thing to see is how every GPU generation has slight differences in how some of these settings apply and actually affect.
    Going from absolute values to scalars and from the power states to a more free range of minimum or maximum values.

    6000 series with Navi20 further changing it to some offset system and while Wattman changes it's layout the naming remains mostly unaltered making it more complicated than it needs to be.
    Driver or bios limits must be a thing too but even without that you have a whole bunch of different systems trying to go through some unified function but with different results and effects.

    This must be easier for AMD to develop against but it can't be good practice especially maintaining legacy GPU's and functionality which would likely explain some of the bugs and issues with Wattman and some of the regression in behavior or why some stuff differs in how it works from one GPU generation to another.

    Great explanation even if it sounds pretty problematic for how it works but it certainly explains or clears up a few things around some of these little problems and inconsistencies with AMD's software. :)


    EDIT: Also confirms a lot of suggestions or theories that have been around as to why some of these issues are happening.
    Would certainly hope to see AMD fix some of this but it seems more likely they might be pulling another overhaul when the next major Radeon Settings Software overhaul and driver build is released.

    Could fix or improve some things but could also break or cause other regressions and particularly with the earlier GPU generations and support for GCN hardware.
    (RDNA1 as well really or Navi10 rather.)


    Well AMD themselves would be the only ones to know for certain, plus what documentation and available information they do supply likely under various NDA's I would expect to be a thing too.

    Nice to see this being supported even so with all of the problems that appear to be involved in trying to work with this system but this certainly shows just how much work has to go into trying to get this supported in software such as MSI Afterburner.
    (And all the testing and hardware involved in that.)


    EDIT: Well I'm not too good with explanations as per usual.
    Appreciate all the work going into this, shame AMD tends to break or change this functionality every so often though leading to various complications.

    Yeah the act of requesting a change in voltage for example and then some unified system, five generations of GCN and two RDNA and then the actual GPU architecture for these instruction sets and it all has to work.

    Not like I would know it's way above my tech knowledge but it can't be optimal at all.
    Everything through the newer Overdrive API after that got unified and having that trying to handle the relevant Power Play functionality for the hardware.

    I could be quite off though, sounds like hoping a decades worth of hardware here will all play nicely with the driver API and layers here getting whatever you get for results through this.
    Would explain some of the longer outstanding issues and the time it took for AMD to work out a few of the regressions even if it's not too far back like Vega or Polaris plus the Radeon VII and it's support or lack thereof.
     
    Last edited: Jan 23, 2021
  6. xandaobh

    xandaobh New Member

    Messages:
    4
    Likes Received:
    3
    GPU:
    RX 470
    Trash driver.. playing csgo is trash on this... rx570
     
    watchblocker and itpro like this.
  7. Digilator

    Digilator Master Guru

    Messages:
    474
    Likes Received:
    124
    GPU:
    Sapphire 5700XT
    In what way?
     
    itpro likes this.
  8. pedropaulo

    pedropaulo Ancient Guru

    Messages:
    2,254
    Likes Received:
    70
    GPU:
    HD5850
    Also issues with CS:Source, the text is almost unreadable, and crash and lag in Metro Exodus.
     
  9. The Creator

    The Creator Master Guru

    Messages:
    227
    Likes Received:
    41
    GPU:
    Red Devil 6800XT
    Vsync in Metro 2033 doesn't work with this and previous drivers on 6800XT.
     
  10. passenger

    passenger Master Guru

    Messages:
    424
    Likes Received:
    70
    GPU:
    Sapphire RX580 8GB
    Similar like itpro said the moment you enable "10-bit Pixel Format“ option Freesync is hell. Normal color depth option with Freesync works fine but in conjunction with 10-bit pixel format setting Freesync is dead.
     
    itpro likes this.

  11. Montville

    Montville Master Guru

    Messages:
    295
    Likes Received:
    39
    GPU:
    Aorus RX 570 4GB
    Works fine here - 10bit 4k panel
    UE590_U28E590D (DP)

    ...and Free sync no issues with games
     
    Michael Lange likes this.
  12. JRMBelgium

    JRMBelgium Member

    Messages:
    12
    Likes Received:
    3
    GPU:
    Radeon RX6800 16GB
    I can confirm that if you overclock the GPU memory in the global profile, you get a black flicker every time you launch a GPU accelerated application ( game, discord, etc... ).
    But if you use the game profile for the OC's, no issues.
     
    HD64G likes this.
  13. passenger

    passenger Master Guru

    Messages:
    424
    Likes Received:
    70
    GPU:
    Sapphire RX580 8GB
    10-Bit pixel format enabled under Graphics/Advanced settings? Lucky you..
    [​IMG]
     
  14. Montville

    Montville Master Guru

    Messages:
    295
    Likes Received:
    39
    GPU:
    Aorus RX 570 4GB
    Yep, passenger, it is..
     

    Attached Files:

  15. aufkrawall2

    aufkrawall2 Master Guru

    Messages:
    771
    Likes Received:
    106
    GPU:
    6800 reference UV
    Not for me on my MSI 5700 XT Gaming X, it causes severe stutter each time fan speed is changed. Applies to both Afterburner and the Wattman "advanced" curve. The percentage slider in Wattman works though.
     

  16. ninja750

    ninja750 Master Guru

    Messages:
    280
    Likes Received:
    71
    GPU:
    RX580 Pulse
    indeed, I use argus monitor that allows 0%
     
  17. itpro

    itpro Master Guru

    Messages:
    931
    Likes Received:
    505
    GPU:
    Radeon Technologies
    Enabled no working properly isn't the same thing. Toggle means nothing...
     
  18. Montville

    Montville Master Guru

    Messages:
    295
    Likes Received:
    39
    GPU:
    Aorus RX 570 4GB
    Gaming is smooth even when 4k - that's all what counts here!
     
  19. rflair

    rflair Don Commisso Staff Member

    Messages:
    4,125
    Likes Received:
    419
    GPU:
    5700XT
    You could use MPT to control the fan, you pretty much just set it and forget it.
     
  20. rflair

    rflair Don Commisso Staff Member

    Messages:
    4,125
    Likes Received:
    419
    GPU:
    5700XT
    You could tell some people that you gradient test your monitor and they would still Negative Nancy what ever you have to say, ignore them.
     
    Passus and Montville like this.

Share This Page