Monday, October 7th 2019

AMD Releases Radeon Software Adrenalin 2019 Edition 19.10.1 with Support for Radeon RX 5500 and RX 5500M

AMD today released a newest update to its Radeon Adrenalin driver. Dubbed version 19.10.1, the new release brings many new bug fixes and improvements to the table. For starters it will enable support for the newly released Radeon RX 5500 an 5500M desktop and mobile graphics cards, so now the buyers of these cards will have a driver from day one to start their experience smoothly. Additionally, support for the upcoming game "GRID", set to release on October 11th, is also included with this driver release.

Download the Adrenalin 19.10.1 Driver here.
The change-log follows.

Support For:
  • AMD Radeon RX 5500 desktop graphics products
  • AMD Radeon RX 5500M mobile graphics products
  • GRID
Fixed Issues:
  • Borderlands 3 may experience an application crash or hang when running DirectX 12 API.
  • Borderlands 3 may experience lighting corruption when running DirectX 12 API.
  • Display artifacts may be experienced on some 75hz display configurations on Radeon RX 5700 series graphics system configurations.
  • Radeon FreeSync 2 capable displays may fail to enable HDR when HDR is enabled via Windows OS on Radeon RX 5700 series graphics products system configurations.
  • Some displays may intermittently flash black when Radeon FreeSync is enabled and the system is at idle or on desktop.
Known Issues:
  • Radeon RX 5700 series graphics products may experience display loss when resuming from sleep or hibernate when multiple displays are connected.
  • Toggling HDR may cause system instability during gaming when Radeon ReLive is enabled.
  • Call of Duty : Black Ops 4 may experience stutter on some system configurations.
  • Open Broadcasting Software may experience frame drops or stutter when using AMF encoding on some system configurations.
  • HDMI overscan and underscan options may be missing from Radeon Settings on AMD Radeon VII system configurations when the primary display is set to 60hz.
  • Stutter may be experienced when Radeon FreeSync is enabled on 240hz refresh displays with Radeon RX 5700 series graphics products.
  • AMD Radeon VII may experience elevated memory clocks at idle or on desktop.
Add your own comment

48 Comments on AMD Releases Radeon Software Adrenalin 2019 Edition 19.10.1 with Support for Radeon RX 5500 and RX 5500M

#26
chr0nos
Cheeseball, post: 4129140, member: 64157"
On this driver or 19.9.2/19.9.3?

This is on 19.9.2:


EDIT: This happens on MSI EVOKE OC (I returned this), and two Sapphire reference models (one was defective with random BSODs).
Yep Memory clocks stuck at max when i set refresh rate to 75hz (1800Mhz), switch to 60hz goes down to 200mhz

Also Black flicker on screen if i have MSI afterburner running
Posted on Reply
#27
Cheeseball
chr0nos, post: 4129247, member: 67393"
Yep Memory clocks stuck at max when i set refresh rate to 75hz (1800Mhz), switch to 60hz goes down to 200mhz

Also Black flicker on screen if i have MSI afterburner running
Same 32" Philips monitor in your System Specs? Does it need to be overclocked to reach 75 Hz or is it a stock setting provided by the monitor EDID? Please report it to AMD through their e-mail form.

I haven't tried MSI Afterburner yet. GPU-Z doesn't cause any issues when monitoring.
Posted on Reply
#28
chr0nos
Cheeseball, post: 4129250, member: 64157"
Same 32" Philips monitor in your System Specs? Does it need to be overclocked to reach 75 Hz or is it a stock setting provided by the monitor EDID? Please report it to AMD through their e-mail form.

I haven't tried MSI Afterburner yet. GPU-Z doesn't cause any issues when monitoring.
Yes, same monitor, EDID reports it as stock setting no OC.

EDIT: Did a "Reset" on Afterburner flicker went away but as soon as I mess with a setting comes back.
Posted on Reply
#29
GoldenX
I bet there were some revisions or bios fixes going on behind the scenes, same as with early Turings.
I would raid-call support.
Posted on Reply
#30
potato580+
this rx5500 isnt even avaiable on my country anyway
Posted on Reply
#31
Vya Domus
GoldenX, post: 4129228, member: 160319"
Thanks for bringing Nvidia to a discussion about AMD exclusive problems, non-shill.
Hmm.

GoldenX, post: 4129094, member: 160319"
Funny how an extension for Vulkan co-developed by AMD and Nvidia has day 1 support on Nvidia, but not on AMD.
Truth is ya'll love to trash these subjects whenever you got the chance.
Posted on Reply
#32
Durvelle27
xkm1948, post: 4129180, member: 50521"
Really? I haven't seen much complaining of driver issue since 19.9.3. On the contray I see quite a lot of praise of Navi driver improvement as well as promotion to buy Navi from owners themselves

Can you link me to some of those threads you mentioned?
Just do a google search and you’d see.

And I mean drivers have improved slightly but still are wonky

Hell I can’t even use my triple monitor setup or I get black screens which is a known issue still by AMD
Posted on Reply
#33
Xuper
GoldenX, post: 4129094, member: 160319"
Funny how an extension for Vulkan co-developed by AMD and Nvidia has day 1 support on Nvidia, but not on AMD.
Care to explain more ?
Posted on Reply
#34
xkm1948
Durvelle27, post: 4129432, member: 107186"
Just do a google search and you’d see.

And I mean drivers have improved slightly but still are wonky

Hell I can’t even use my triple monitor setup or I get black screens which is a known issue still by AMD
Alright let's trouble shoot this:

1. Did you OC the card? Is it stable "out of the box"?
2. Tried undervolting it yet? Folks on amd reddit report undervolting is a "One solution solves all problem" miracle
3. Using any 3rd party tool to regulate fan speed? Deleting them?
4. Have you tried using DDU before installing new driver?
5. Hooking up different monitors? Or different display port cable? Or use HDMI instead of Display port?
6. Try fresh installing Windows 10? Completely clean slack might help?
7. Try windows 10 insider build?
8. Try Linux? Folks claim AMD's Linux driver support is amazing.
9. Update mobo BIOS?
10. Use default DRAM speed instead of XMP?
11. Try different DRAM
12. Disable CPU OC?
13. Try different CPU?
14. Try different mobo


And of course there is always the option of RMA.

Also just remembered, have you swapped your AE 5700XT yet to an AIB one?
Posted on Reply
#35
Durvelle27
xkm1948, post: 4129450, member: 50521"
Alright let's trouble shoot this:

1. Did you OC the card? Is it stable "out of the box"?
2. Tried undervolting it yet? Folks on amd reddit report undervolting is a "One solution solves all problem" miracle
3. Using any 3rd party tool to regulate fan speed? Deleting them?
4. Have you tried using DDU before installing new driver?
5. Hooking up different monitors? Or different display port cable? Or use HDMI instead of Display port?
6. Try fresh installing Windows 10? Completely clean slack might help?
7. Try windows 10 insider build?
8. Try Linux? Folks claim AMD's Linux driver support is amazing.
9. Update mobo BIOS?
10. Use default DRAM speed instead of XMP?
11. Try different DRAM
12. Disable CPU OC?
13. Try different CPU?
14. Try different mobo


And of course there is always the option of RMA.

Also just remembered, have you swapped your AE 5700XT yet to an AIB one?
1. card is stock
2. Doesn’t work
3. No apps
4. Clean OS
5. Doesn’t matter what type, connections, just doesn’t work
6. Read 4
7. No different
8. No as Linux isn’t as good for gaming
9. Pastiest BIOs
10. RAM is default
11. RAM doesn’t matter. Try Samsung and Hynix Die
12. CPU stock
13. Made no difference with a 1700X or 3900X
4. No different

Again I’m not sure if you just glance over everything but every issue I have mentioned is clearly mentioned in AMDs own notes as a known issue that hasn’t been solved.

If you read the OP it even clearly states known issues with multi monitor setups
Posted on Reply
#36
xkm1948
Durvelle27, post: 4129480, member: 107186"
1. card is stock
2. Doesn’t work
3. No apps
4. Clean OS
5. Doesn’t matter what type, connections, just doesn’t work
6. Read 4
7. No different
8. No as Linux isn’t as good for gaming
9. Pastiest BIOs
10. RAM is default
11. RAM doesn’t matter. Try Samsung and Hynix Die
12. CPU stock
13. Made no difference with a 1700X or 3900X
4. No different

Again I’m not sure if you just glance over everything but every issue I have mentioned is clearly mentioned in AMDs own notes as a known issue that hasn’t been solved.

If you read the OP it even clearly states known issues with multi monitor setups
Well in that case just keep on waiting, Eventually it will be fixed, I hope
Posted on Reply
#37
GoldenX
Xuper, post: 4129438, member: 83814"
Care to explain more ?
https://phoronix.com/scan.php?page=news_item&px=Vulkan-1.1.124-Released



"A joint AMD/NVIDIA extension"

https://developer.nvidia.com/vulkan-driver This is the beta Vulkan drivers from Nvidia.



https://www.techpowerup.com/download/amd-radeon-graphics-drivers/

Nothing on the changelog.

http://vulkan.gpuinfo.org/listdevices.php this is the official report tool and site for Vulkan, there is another for OpenGL. It can track changes and differences in different drivers.



If you try to upload any driver since 19.8, you will get notified that no changes have been made.


This isn't just now, it's been like this for years in the case of OpenGL.
Now, those Vulkan extensions will eventually be released on AMD too, but after 3 weeks on an unstable state, and will be stable after 6 months or so, it has always been like that.

Vya Domus, post: 4129361, member: 169281"
Truth is ya'll love to trash these subjects whenever you got the chance.
Because it's a real problem, decades old. I understand if you only care about Direct3D performance as a gamer, but that doesn't makes this issue disappear.
AMD needs to allocate more resources on driver development. This hasn't been solved since the ATI days, and so far it seems to be the same story with Navi.

To use their own words:

https://gitmemory.com/issue/GPUOpen-Drivers/AMDVLK/112/535341844

Posted on Reply
#38
Xuper
lol , I thought something big issue here and turn out only two extensions ! Latest version for Nvidia is 1.1.123 and for AMD is 1.1.121
It is really big important because of very few extensions ?
Posted on Reply
#39
GoldenX
Xuper, post: 4129560, member: 83814"
lol , I thought something big issue here and turn out only two extensions ! Latest version for Nvidia is 1.1.123 and for AMD is 1.1.121
It is really big important because of very few extensions ?
What do you think games use to work? DirectX9?
Vulkan is AMDs idea, it exists because of Mantle, and yet it's not a priority, it's in the same forgotten box as OpenGL. Meanwhile the competition has everything ready and working within 24 hours.
Do the work yourself, enter http://vulkan.gpuinfo.org/ pick an AMD card and compare it to a Turing/Pascal/Maxwell, see the missing extensions and features. Do the same on http://opengl.gpuinfo.org/
Game developers have to make exceptions for AMD cards all the time, it shouldn't have to be like that.
Posted on Reply
#40
Vya Domus
GoldenX, post: 4129552, member: 160319"
I understand if you only care about Direct3D performance as a gamer, but that doesn't makes this issue disappear.
What I understand is that there are no widespread issues with AMD cards and Vulkan or OpenGL. You are complaining about some extensions that have been added by Nvidia literally a few days ago. Really scraping the bottom of the barrel here in order to find something to complain about.

How many programs did you ran that need these extensions ? What exactly is the issue that you encountered here that makes your setup unusable?

GoldenX, post: 4129552, member: 160319"
AMD needs to allocate more resources on driver development.
As with every company what they should do is allocate more resources by prioritizing what matters the most, that would be DirectX on Windows to your dismay.

Nvidia probably has a driver support team bigger than AMD's entire GPU division and despite that their drivers are riddled with bugs that need countless fixes. If we put things into perspective the performance of their driver team is abysmal compared to AMD's.

I had more blackscreens using Nvidia in 3 years than I had for almost a decade using AMD/ATI. I don't really complain about it because it's a waste of time and it doesn't even matter both companies have drivers that work the vast majority of the time.
Posted on Reply
#41
GoldenX
Vya Domus, post: 4129566, member: 169281"
What I understand is that there are no widespread issues with AMD cards and Vulkan or OpenGL. You are complaining about some extensions that have been added by Nvidia literally a few days ago. Really scraping the bottom of the barrel here to find something to complain about.

How many programs did you ran that need these extensions ? What exactly is the issue that you encountered here that makes your setup unusable?
So the fact that there are over a dozen complains on the AMD forums about atrocious OpenGL performance means nothing.
Those are new extensions, fresh, nothing is using them yet, but no one will until AMD implements them. If you take half a year to do that...

I get it, this is not a problem to the end user, Fortnite/Control/Call of Duty just works. But being called a shill because you point a real problem with facts will make anyone angry, sensitive fanboys and all.
Posted on Reply
#42
Vya Domus
GoldenX, post: 4129568, member: 160319"
So the fact that there are over a dozen complains on the AMD forums about atrocious OpenGL performance means nothing.
OpenGL reached a dead end as soon as Vulkan was released, if you want AMD to improve it's performance now, good luck, that's all I have to say.

GoldenX, post: 4129568, member: 160319"
Those are new extensions, fresh, nothing is using them yet, but no one will until AMD implements them.
Let's get this straight, you're complaining about something that has just been released which isn't used by anything yet and wont be for some time into the future, then, you proceed to give an example of how Nvidia does support these useless extensions as of now and you wonder why some might have the inclination to call you a fanboy or shill ?

Surely you can see why that would happen.
Posted on Reply
#43
GoldenX
Vya Domus, post: 4129574, member: 169281"
OpenGL reached a dead end as soon as Vulkan was released, if you want AMD to improve it's performance now good luck, that's all I have to say.
OpenGL will still be maintained and used as long as Vulkan keeps being mobile focused and has less features. It is as dead as DirectX12 is with the release of Vulkan.

Vya Domus, post: 4129574, member: 169281"
Let's get this straight, you're complaining about something that has just been released which isn't used yet by anything and wont be for some time into the future, then, you proceed to give an example of how Nvidia does support these useless extensions as of now and you wonder why some might have the inclination to call you a fanboy or shill ?

Surely you can see why that would happen.
This is an example, shows that this happens ALL THE TIME. Want me to fetch the last 100 Vulkan versions and show you how long it took AMD to implement their changes? You can do it yourself, I'm just an Nvidia shill after all, despite using only AMD since 2013. My last Nvidia card was a 7600GT, and it's drivers were shit.
Posted on Reply
#44
Vya Domus
GoldenX, post: 4129576, member: 160319"
This is an example, shows that this happens ALL THE TIME. Want me to fetch the last 100 Vulkan versions and show you how long it took AMD to implement their changes? You can do it yourself, I'm just an Nvidia shill after all, despite using only AMD since 2013. My last Nvidia card was a 7600GT, and it's drivers were shit.
I'd sure love to see the last 100 extensions that broke some games or programs.

I'd also like OpenCL 2.0 on my 1080 but Nvidia refuses to support anything past 1.2 for many, many years.

You probably couldn't care less about my complaint just as I don't about these extensions.

But in the end none of these things matter to 99.9% of users. Do you still not see why this is a waste of time ?
Posted on Reply
#45
Cheeseball
GoldenX, post: 4129552, member: 160319"


https://www.techpowerup.com/download/amd-radeon-graphics-drivers/
Dude, those two functions won't be needed for a while. I'm not sure if you're delving into GPGPU/HW acceleration/engine development but VK_KHR_timeline_semaphore is just a more efficient way of doing VK_STRUCTURE_TYPE_SEMAPHORE_CREATE_INFO, combining queue searching and pinpointing. VK_KHR_shader_clock is just a low-level counter that can be done (roughly) with SPV_KHR_shader_clock. Both AMD and NVIDIA have alternative ways of doing these

Vya Domus, post: 4129584, member: 169281"
I'd also like OpenCL 2.0 on my 1080 but Nvidia refuses to support anything past 1.2 for many, many years.
If you have NVIDIA hardware, you should be using CUDA on top of OpenCL. That would provide maximum performance unless you have software that only uses OpenCL (I'm looking at you [B]Final Cut Pro X)[/B], but even then the performance is still pretty good.

Vya Domus, post: 4129584, member: 169281"
But in the end none of these things matter to 99.9% of users. Do you still not see why this is a waste of time ?
I agree. You should not be complaining about specific features that the general population won't really use (unless you yourself have specific use-cases) but complain about broken functionality (e.g. the 75Hz/144Hz memory issue) that affects daily usage.
Posted on Reply
#46
GoldenX
Well let's just agree that VIA makes the best drivers. I haven't heard a single problem from them. I'm a VIA shill.

Cheeseball, post: 4129594, member: 64157"
Dude, those two functions won't be needed for a while. I'm not sure if you're delving into GPGPU/HW acceleration/engine development but VK_KHR_timeline_semaphore is just a more efficient way of doing VK_STRUCTURE_TYPE_SEMAPHORE_CREATE_INFO, combining queue searching and pinpointing. VK_KHR_shader_clock is just a low-level counter that can be done (roughly) with SPV_KHR_shader_clock. Both AMD and NVIDIA have alternative ways of doing these
What about VK_EXT_fragment_shader_interlock ? Or GL_ARB_compute_variable_group_size on OGL, those are quite important ones.
Posted on Reply
#47
evernessince
Cheeseball, post: 4129229, member: 64157"
I forward you to your own quote:





"Blah blah blah blah."

Please contribute to the discussion by either sharing your findings to help fix issues related to AMD drivers and stop mentioning NVIDIA-related driver issues as a counter-argument.

---

I just tested Enhanced Sync in PUBG with 19.10.1 and haven't had any crashes. This is at 120 Hz (disabled overclock on my monitor), FreeSync on, Anti-Lag off. Stock WattMan settings. Shader Cache did cause hitching at first, but I left it on so it can load whatever it needs in the game (the four big maps in PUBG) and now it seems to be fine. This results in a constant 120 Hz with minimal frame drops (e.g. loading on the plane). Will test VSR to 1440p, although I already have render scale in-game set to 120.
As expected, you have nothing to add but petty name calling. You should take your own advice. FYI GoldenX was the one to bring up Nvidia here, not me. You once again completely misassociate. You came into here calling me a shill without reading prior comments and you have zero intention of apologizing even though it was you who failed to even read the context before jumping in and making mistakes. It is sad that common decency is so hard to find nowadays.

GoldenX, post: 4129228, member: 160319"
Thanks for bringing Nvidia to a discussion about AMD exclusive problems, non-shill.
Actually you were the one to do this

You said:
"Funny how an extension for Vulkan co-developed by AMD and Nvidia has day 1 support on Nvidia, but not on AMD. "

Not remembering your own posts? I love how the self projection here.
Posted on Reply
#48
Cheeseball
GoldenX, post: 4129596, member: 160319"
What about VK_EXT_fragment_shader_interlock ? Or GL_ARB_compute_variable_group_size on OGL, those are quite important ones.
VK_EXT_fragment_shader_interlock is quite inefficient for transparency, which is why AMD didn't implement it. If you need to use this, you can just do it directly in a DX12 engine (this is better on both hardware), if you have OpenGL use glTextureBarrier (again, better on both hardware), or use multiple subpasses instead.

GL_ARB_compute_variable_group_size was proposed by NVIDIA, but it should be usable on any modern hardware as of OpenGL 4.5.

@GoldenX, we can continue this discussion through PMs if you'd like as this is getting out-of-topic.


Bottom line, driver improvements are still needed on both sides of the camp.
Posted on Reply
Add your own comment