AMD Software: Adrenalin Edition 22.7.1- Driver download and discussion

Discussion in 'Videocards - AMD Radeon Drivers Section' started by justdoge, Jul 26, 2022.

  1. AlleyViper

    AlleyViper Master Guru

    Messages:
    505
    Likes Received:
    77
    GPU:
    Strix 2070S A|480 X
    This is also starting to deserve its own meme, even if it only appeared recently on the issues list, it goes way back. Polaris related, as my rx480 becomes stuck on max 3d gpu clock when exiting Doom Eternal (vulkan), with gpu utilization reading as 100% on monitoring utils (not on task manager). Same as described in this thread, restarting AMDRSServ.exe will restore normal behavior. It's noticeable when preventing the card to work fanless under very light loads.

    On the good side, these drivers finally solved an issue I was having since 22.3.1 + freesync that could cause desktop sutter/lag after playing/seeking videos on mpc-be/hc (some users report it after exiting games), so as vsync failing in non-exclusive fullscreen.
     
    Last edited: Aug 3, 2022
  2. illusiveman

    illusiveman Member Guru

    Messages:
    156
    Likes Received:
    124
    GPU:
    XFX 6700XT Ultra
    I tried with all FSR modes from Ultra quality to ultra performance and couldn't reproduce it.
    Must be GPU specific or some specific bug in the windows version of the driver in case you're using W11...because I'm still on W10.
     
  3. CPC_RedDawn

    CPC_RedDawn Ancient Guru

    Messages:
    9,464
    Likes Received:
    1,769
    GPU:
    6800XT/3080Ti
    I am on latest Windows 10 21H2 19044.1865 nothing modified.

    More than likely GPU specific, the only other thing I can think is a monitor issue? May move my PC downstairs and test it on my LG TV.
     
  4. illusiveman

    illusiveman Member Guru

    Messages:
    156
    Likes Received:
    124
    GPU:
    XFX 6700XT Ultra
    Yeah...probably GPU. I have a Acer xv272u...standard 1440p 144Hz monitor with freesync. Nothing special.
     

  5. akanerin7

    akanerin7 Member

    Messages:
    48
    Likes Received:
    23
    GPU:
    Vega
    The new OpenGL are FULLY NATIVE, it doesn't use anything related to their DirectX Driver anymore unlike their early implementation in UWP Dev Channel.. just in case anyone saying its a wrapper this time
     
    Last edited: Aug 3, 2022
    HD64G likes this.
  6. The Creator

    The Creator Master Guru

    Messages:
    576
    Likes Received:
    403
    GPU:
    Red Devil 6800XT LE
    And what is the version when this happened (wrapper -> native)? I use the latest UWP (newer than 22.7.1) which uses the same OpenGL 22.07 beta as 22.7.1 does. So which old OpenGL version is a wrapper - 22.06 beta or 22.05 beta?
     
    Last edited: Aug 3, 2022
    akanerin7 likes this.
  7. Blisk

    Blisk Active Member

    Messages:
    83
    Likes Received:
    60
    GPU:
    RX 6900XT
    ???

    It wasn't a wrapper in the UWP either.
     
    akanerin7 likes this.
  8. akanerin7

    akanerin7 Member

    Messages:
    48
    Likes Received:
    23
    GPU:
    Vega
    22.05/22.06 beta.. it loaded the d3d vendor driver as well related stuff, for what purpose? idk.. since it generate shader cache for it.. the new one on 22.07 beta doesnt seems to require it or generate any kinda dx cache.

    it also work fine even if i try to hook it the same way as prev one which btw will crash it.

    Edit: i've also noticed that the newer OpenGL fullscreen seems to be Exclusive, some stuff that i ran on borderless fullscreen just run as exclusive fullscreen
    (not really that important but its interesting, at least it didn't crash anymore due switching between app)
     
  9. Lbuipo

    Lbuipo Member Guru

    Messages:
    129
    Likes Received:
    72
    GPU:
    Amd Vega 64
    What is the main issue, if there is a warpper inside AMD drivers?!
    I dont care less, if my games run smother!
    But, there is no wrapper!
    giphy(2).gif
     
    Last edited: Aug 3, 2022
    HD64G and Cryio like this.
  10. AsiJu

    AsiJu Ancient Guru

    Messages:
    8,134
    Likes Received:
    2,882
    GPU:
    MSI RX6800XT G.XT.
    We already went through this in this thread, let's not go there again.
     
    MyEinsamkeit and akanerin7 like this.

  11. akanerin7

    akanerin7 Member

    Messages:
    48
    Likes Received:
    23
    GPU:
    Vega
    my bad, moving on.. the driver seems pretty great.. at least on my experience
     
    HD64G and AsiJu like this.
  12. =GGC=Phantomblu

    =GGC=Phantomblu Member Guru

    Messages:
    177
    Likes Received:
    51
    GPU:
    Radeon RX 6900XT
    For you, maybe you've never read it
    https://devblogs.microsoft.com/directx/updates-in-graphics-and-gaming/

    https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/
     
    akanerin7 likes this.
  13. Guns1

    Guns1 New Member

    Messages:
    4
    Likes Received:
    0
    GPU:
    rx 470 4Gb
    I cannot launch FINAL FANTASY VIII REMASTERED (OpenGL) after installing 22.7.1 driver.
    The game crashes on launch with the error: 3303725833: 2123 failed to load shaders, reverting to fixed function.
     
  14. akanerin7

    akanerin7 Member

    Messages:
    48
    Likes Received:
    23
    GPU:
    Vega
  15. Macer

    Macer Active Member

    Messages:
    86
    Likes Received:
    69
    GPU:
    AMD Radeon RX6900XT
    me too...
    OpenGL 22.07 Beta does not work with Play FINAL FANTASY VIII REMASTERED...
    [​IMG]
     

  16. Chastity

    Chastity Ancient Guru

    Messages:
    3,083
    Likes Received:
    1,165
    GPU:
    Nitro 5700 XT
    Had a weird issue on my system after updating to KB5015885. System would start up, play my daily D2R session, and is fine. Start the game up a second time, and it would crash out, usually at a character load and is initializing, tho it could happen during gameplay. Also, sometimes tabs in my browsers (FFox and Edge) would just crap out and need to be refreshed.

    After some investigating logs, redoing my GPU drivers, chipsets, and other digging, I discovered my system was running two instances of explorer.exe, with one in "lolwtf" limbo. So I killed both processes, and then restarted explorer.exe, and ever since system has been solid again, even after reboots. I have not been able to recreate since, which I was able to do before.

    So SOMETHING got fubar, but it seems it has corrected itself after some nudging. Lesson lo learn: don't jump to assuming it's a GPU driver issue.
     
  17. Macer

    Macer Active Member

    Messages:
    86
    Likes Received:
    69
    GPU:
    AMD Radeon RX6900XT
    OBS released 28.0 Beta 1 today. Supports AMD AMF H.264/AVC B-Frame encoding.

    awesome
    [​IMG]

    But B-frames are enable, results in regular encoder overloads with stuttery, inconsistent playback.

    I'm not sure why.
     
    Last edited: Aug 3, 2022
    HD64G likes this.
  18. justdoge

    justdoge Member Guru

    Messages:
    119
    Likes Received:
    39
    GPU:
    MSI RX580 Gaming X
    use StreamFX plugin for mainline obs, it has everything
     
  19. incneet

    incneet Member

    Messages:
    40
    Likes Received:
    0
    GPU:
    RX460 2GB
    you guys have in some parts of the video, slowdowns using amd relive to record?
     
  20. illusiveman

    illusiveman Member Guru

    Messages:
    156
    Likes Received:
    124
    GPU:
    XFX 6700XT Ultra
    It seems that they removed at least one extension from OGL driver. I found this on Reddit:

    Hello,

    I am a member of the [RPCS3] development team, an open-source PS3 emulator that uses the open standards OpenGL and Vulkan as render APIs.

    We are seeing great performance improvements with the latest AMD OpenGL driver on Windows. However, we've also noticed that the extension GL_NV_depth_buffer_float that was previously implemented in the driver, isn't present anymore.

    The formal [GL_ARB_depth_buffer_float](https://registry.khronos.org/OpenGL/extensions/ARB/ARB_depth_buffer_float.txt) is more limited than [GL_NV_depth_buffer_float](https://registry.khronos.org/OpenGL/extensions/NV/NV_depth_buffer_float.txt) (see point 6 in Issues) because it does not allow writing values smaller or bigger than [0,1], which is something we absolutely need to do on our OpenGL render.

    The PS3 has a float depth z buffer (which is also supported by PC hardware) and PS3 games are actually making use of this extended range to do things like reverse Z. This cannot be emulated with simple normalisation without a lot of unsolvable issues.

    Could someone from the OpenGL team please check this? /u/AMD_Vik

    Link to reddit thread https://redd.it/wfs193
     
    Mott, HD64G, Blisk and 1 other person like this.

Share This Page