Download: Radeon Adrenalin Edition 19.10.1 WHQL driver

#5717908 Posted on: 10/07/2019 08:24 PM

---

Nothing interesting for me. Still no PlayReady 3 for Vega, and nothing else fixed/added which concerns me at the moment.

Will remain on 19.9.2 for now.

#5717928 Posted on: 10/07/2019 09:17 PM

---

Still problematic with Radeon VII:
- Freesync can't work on more than one display at the same, and this is random on which it will be enabled
- unable to enable RIS when Crossfire is enabled.

#5717930 Posted on: 10/07/2019 09:24 PM

---

*Crossfire is not supported anymore since 2017.
*You do not need to use freesync in more than 1 displays, freesync is for gamers, if you need to work get another rig.

AMD will not support your horrendous setup. Good luck.

#5717932 Posted on: 10/07/2019 09:29 PM

---

@JonasBeckman

Do you think there are any improvements with 19.10 vs 19.9?

#5717934 Posted on: 10/07/2019 09:47 PM

---

I was just looking if AMD had anything new and saw 19.9.3 still but I guess not all GPU's are updated yet to this 19.10.1 driver page though changing the driver URL manually worked.

Well 5500 support, GRID and some Borderlands fixes.

75Hz should be fixed and mentions of FreeSync but those weren't the only displays having the black screen problem but perhaps it's resolved at last though no mention of the display corruption and some others but the multi-display issue is now part of the known issues.

Wonder what else is in here. Might be possible to find at least something.


EDIT: Profile file only shows a update of the last build number of the driver version so might just be a minor update though there are some nice bug fixes even so.

Also just a profile for Grid (2019) already in the release notes.


Chill registry value is still showing as a invalid DWord but can be deleted and remade at least until reboot(?) or when it was it reset until this gets fixed.

As for issues well the loading spinner in Windows is still off since at least 19.9.1 so there's still something going on though if that's all and it's not tied to other problems it's minimal.
(Shows as a darker blue kinda corrupt color version instead of the light blue default.)
(From reports other users have mentioned it too so something is causing it but not for everyone and it might be somewhere around 19.8.2 and later drivers or 19.9.1 where it happens.)


EDIT: And for the INF in addition to Navi14 entries and support for the 5500 it has these as well.


HKR, "UMD\DXVA", DXVA_WMV, %REG_SZ%, "0"
HKR, "UMD\DXVA", DXVA_WMV_DEF, %REG_SZ%, "0"


HKR,, PXProfileSync, %REG_DWORD%, 1


So something I'm not entirely sure about and then something for media playback via DirectX Video Acceleration and WMV for Windows Media Video I think.

Considering the naming and the other existing settings for the second one...

HKR,, PXUseAPLForSwitch, %REG_DWORD%, 1
HKR,, PXReducePopUps, %REG_DWORD%, 1

I wonder if it might be related to something for Radeon Settings itself.

But then again the PXAA settings above that for the Common (Older GPU models.) and Plus (Navi10 and now Navi14) contains stuff like .DLL drivers for D3D and other bits so could be something else too.

#5717950 Posted on: 10/07/2019 11:49 PM

---

*Crossfire is not supported anymore since 2017.
Enabling the option is still needed to enable explicit multi-GPU in DX12 and Vulkan. This is supported!


You are mistaken and I know better what I need. Freesync is for everybody. I use it to play videos at proper speed, for emulators and for gaming of course. It worked fine in 19.6.3 driver and before. To play a game right now I must disconnect all displays except one. It isn't to smart to think it should be like this... It is a bug.

How can you know this? Or is this just trolling like the rest of your post?

#5717951 Posted on: 10/08/2019 12:00 AM

---

Is MorePowerTool working with this driver?

#5717972 Posted on: 10/08/2019 01:57 AM

---

ChillEnabled can be fix by deleting it.
Then rename it using the Qword for it instead of DWord as it allows you to set it to 0 and it will stick to 0 once you reboot (reboot the pc).

If you use Chill then set it to 1 instead and reboot.

---------------
DX12 seems to work a whole lot better in BFV in the last few driver releases.
But there is a catch to using DX12. You have to let it load up. It can take an entire round before it's completely stutter free. It goes like this:
-1st time playing a match with DX12, lots of stutter.
-After about 2 minutes minor stutters here and there
-After 5 minutes you hardly notice and if you do notice a stutter once you preform that action again it doesn't stutter any more
-Next round, stutter free gaming.

Once you go through that process the next time you play it's been pretty uneventful bliss.

#5717973 Posted on: 10/08/2019 02:05 AM

---

ChillEnabled can be fix by deleting it.
Then rename it using the Qword for it instead of DWord as it allows you to set it to 0 and it will stick to 0 once you reboot (reboot the pc).

If you use Chill then set it to 1 instead and reboot.


Wasn't it the other way around?

1 is of and 0 is on?

#5717975 Posted on: 10/08/2019 02:06 AM

---

Wasn't it the other way around?

1 is of and 0 is on?
IMHO that's wrong. In the registry 1 has always denoted enabling while 0 denotes disabling.

#5717976 Posted on: 10/08/2019 02:09 AM

---

Yeah, I do think the same as you.
But, supposedly it's backwards.

#5717977 Posted on: 10/08/2019 02:09 AM

---

Yeah, I do think the same as you.
But, supposedly it's backwards.
The issue was that when you rebooted the PC so that the changes would take effect ChillEnabled would revert to 1 using the Dword. And that's the predicted behavior for 32bit.

However, if you want to over ride it you use 64bit Qword instead and it will leave it off (0) when you reboot the PC. And since we all are using 64bit OS we should be using 64 bit keys.

Edit:
I would encourage anyone to make sure it's off. I've only seen Chill benefit the ultra low end. IE: Laptop on battery, etc.

#5717979 Posted on: 10/08/2019 03:14 AM

---

@JonasBeckman

Do you think there are any improvements with 19.10 vs 19.9?

I will test it when they upd. this to WHQL.
Now im waiting for 19.9.3 WHQL (we shall see which gets it).

Note:
Can somebody test if it's WHQL? (it can be cuz' new GPU was introduced)

#5717983 Posted on: 10/08/2019 03:33 AM

---

@OnnA It's beta.

#5717988 Posted on: 10/08/2019 03:48 AM

---

Thanks.