G.Skill KM360 Keyboard Review
Alphacool EISBAER Ex BLACK LCS review
Netgear Nighthawk AX12 Wi-Fi 6 router review
Corsair HS60 PRO Surround Headset Review
MSI Radeon RX 5700 Gaming X review
Team Group Cardea II NVMe 1 TB SSD Review
ASRock X570 Phantom Gaming ITX/TB3 review
Promo: URCDKey Autumn Sale Windows 10 Pro for $11
Patriot P200 1TB SATA3 SSD Review
ASRock Radeon RX 5700 XT Taichi OC+ review
Download: Radeon Adrenalin Edition 19.10.1 WHQL driver
AMD released a new driver, the October build adds support for Radeon 5500 and fixes a number of issues with borderlands 3 and FreeSync 2 related items. There are reports that the 75Hz bug is fixed in this driver- updated to WHQL driver.
Download: GeForce Hotfix Driver Version 436.51 - 10/03/2019 09:52 AM
So NVIDIA released a hotfix driver today, again moments after an official driver. The driver is based on 436.48 however entails crash fixes for FIFA 19/FIFA 20/Star Wars: Battlefront II (2017) and fl...
Download: GeForce 436.48 WHQL drivers - 10/01/2019 03:04 PM
NVIDIA just released a fresh set of graphics card drivers, this release provides increased performance and the optimal gaming experience for Tom Clancy’s Ghost Recon Breakpoint and Asgard&am...
Download: Radeon Software Adrenalin 2019 Edition 19.9.3 - 09/30/2019 09:27 PM
AMD releases Radeon Software Adrenalin 2019 Edition 19.9.3, this new driver is primarily intended to provide Ghost Recon Breakpoint and adds Radeon Image Sharpening (RIS) support for Vega class produ...
Download: AMD chipset driver revision 1.9.27.1033 - 09/30/2019 09:25 AM
AMJD Releases the adrenaline edition 1.9.27.1033 of the chipset driver, AMD is offering a new version for third-generation Ryzen processors ("Matisse") with an updated " AMD Ryzen Ba...
Download: Samsung SSD Magician 6.0.0 - 09/26/2019 07:07 PM
Samsung has updated their Samsung SSD Magician towards build 6.0.0, Samsung Magician software is designed to help you manage your SSD with a simple and intuitive user interface. The software is mirro...
Skinner
Senior Member
Posts: 420
Joined: 2003-03-22
Senior Member
Posts: 420
Joined: 2003-03-22
#5718132 Posted on: 10/08/2019 03:24 PM
Most of the work is allready done, (dx11 is on its end), I can't image it would so much work to port it over to Vega 2 given the "little" hardware differences compared to Vega 1.
Most of the work is allready done, (dx11 is on its end), I can't image it would so much work to port it over to Vega 2 given the "little" hardware differences compared to Vega 1.
Eastcoasthandle
Senior Member
Posts: 2150
Joined: 2006-05-22
Senior Member
Posts: 2150
Joined: 2006-05-22
#5718149 Posted on: 10/08/2019 03:53 PM
Warning:
Do not enable Radeon OSD at desktop and start a game as it can cause problems.
Some games may cause a black screen when you exit out of it with OSD enabled. As reported by others I've confirmed one game BlackOps 4. Other games seem ok. I think it has something to do with how Activision uses their anti cheating in that game.
Can anyone tell me how to disable OSD at desktop?
Do not enable Radeon OSD at desktop and start a game as it can cause problems.
Some games may cause a black screen when you exit out of it with OSD enabled. As reported by others I've confirmed one game BlackOps 4. Other games seem ok. I think it has something to do with how Activision uses their anti cheating in that game.
Can anyone tell me how to disable OSD at desktop?
OnnA
Senior Member
Posts: 9429
Joined: 2014-10-25
Senior Member
Posts: 9429
Joined: 2014-10-25
#5718157 Posted on: 10/08/2019 04:10 PM
It is disabled by Default.
For me that is.
Warning:
Do not enable Radeon OSD at desktop and start a game as it can cause problems.
Some games may cause a black screen when you exit out of it with OSD enabled. As reported by others I've confirmed one game BlackOps 4. Other games seem ok. I think it has something to do with how Activision uses their anti cheating in that game.
Can anyone tell me how to disable OSD at desktop?
Do not enable Radeon OSD at desktop and start a game as it can cause problems.
Some games may cause a black screen when you exit out of it with OSD enabled. As reported by others I've confirmed one game BlackOps 4. Other games seem ok. I think it has something to do with how Activision uses their anti cheating in that game.
Can anyone tell me how to disable OSD at desktop?
It is disabled by Default.
For me that is.
Jackalito
Senior Member
Posts: 519
Joined: 2013-11-03
Senior Member
Posts: 519
Joined: 2013-11-03
#5718171 Posted on: 10/08/2019 04:41 PM
Do you mean to have the option disabled from Radeon Settings, or not having the overlay with the stats before launching the game?
Overlay is enabled by default after installing the drivers, but can be disabled easily under Preferences.
Warning:
Do not enable Radeon OSD at desktop and start a game as it can cause problems.
Some games may cause a black screen when you exit out of it with OSD enabled. As reported by others I've confirmed one game BlackOps 4. Other games seem ok. I think it has something to do with how Activision uses their anti cheating in that game.
Can anyone tell me how to disable OSD at desktop?
Do not enable Radeon OSD at desktop and start a game as it can cause problems.
Some games may cause a black screen when you exit out of it with OSD enabled. As reported by others I've confirmed one game BlackOps 4. Other games seem ok. I think it has something to do with how Activision uses their anti cheating in that game.
Can anyone tell me how to disable OSD at desktop?
Do you mean to have the option disabled from Radeon Settings, or not having the overlay with the stats before launching the game?
Overlay is enabled by default after installing the drivers, but can be disabled easily under Preferences.
ninja750
Senior Member
Posts: 154
Joined: 2007-09-20
Senior Member
Posts: 154
Joined: 2007-09-20
#5718177 Posted on: 10/08/2019 04:48 PM
and poor gaming performance 1080p and 1080p with low settings (for very high fps playing)
Still, no news on BSOD on windows launch, crashes during games, spontaneous PC shutdowns for the 5700 series.
and poor gaming performance 1080p and 1080p with low settings (for very high fps playing)
Undying
Senior Member
Posts: 11756
Joined: 2008-08-28
Senior Member
Posts: 11756
Joined: 2008-08-28
#5718189 Posted on: 10/08/2019 05:06 PM
Do you mean to have the option disabled from Radeon Settings, or not having the overlay with the stats before launching the game?
Overlay is enabled by default after installing the drivers, but can be disabled easily under Preferences.
I think hes saying before the game starts dont enable osd in desktop. It would be great if osd can be turned on while in game tho.
Do you mean to have the option disabled from Radeon Settings, or not having the overlay with the stats before launching the game?
Overlay is enabled by default after installing the drivers, but can be disabled easily under Preferences.
I think hes saying before the game starts dont enable osd in desktop. It would be great if osd can be turned on while in game tho.
connos
Senior Member
Posts: 1154
Joined: 2008-10-30
Senior Member
Posts: 1154
Joined: 2008-10-30
#5718190 Posted on: 10/08/2019 05:08 PM
AMD Chill writing a incorrect registry value and keeping always enabled possibly interfering with other things until removed and manually set to a valid 1 or 0 value.
Wattman possibly using default settings on start until a profile is manually loaded and for Navi the minimum frequency is often outright ignored though putting in a higher value for voltage can reduce stuttering during clock fluctuations which also happen under D3D10 - D3D12 and Vulkan though not as severe as whatever is going on with D3D9 at the moment.
RIS or Radeon Image Sharpening is interfering with D3D12 functionality on a few systems where it just causes a crash if it's enabled.
75Hz and Enhanced Sync have been fixed now so that's resolved and then specific game issues and a couple of other things but there's work to be done.
I might be missing a few things, trying to keep a active list of fixed and known issues mostly the remaining known ones though I can't confirm everything on my own system although some of the repeatedly reported issues are easy enough like checking how D3D9 and lower settings behave in terms of clock speeds or the registry value for Chill and what it gets set to after a clean uninstall and install of the newest driver.
.
I have problems with frequency boosting in BFV 1080p low settings render ahead off. It boost to 776mhz only!!!! Its a stuttering mess. With my 480 i never had such issues.
AMD Chill writing a incorrect registry value and keeping always enabled possibly interfering with other things until removed and manually set to a valid 1 or 0 value.
Wattman possibly using default settings on start until a profile is manually loaded and for Navi the minimum frequency is often outright ignored though putting in a higher value for voltage can reduce stuttering during clock fluctuations which also happen under D3D10 - D3D12 and Vulkan though not as severe as whatever is going on with D3D9 at the moment.
RIS or Radeon Image Sharpening is interfering with D3D12 functionality on a few systems where it just causes a crash if it's enabled.
75Hz and Enhanced Sync have been fixed now so that's resolved and then specific game issues and a couple of other things but there's work to be done.
I might be missing a few things, trying to keep a active list of fixed and known issues mostly the remaining known ones though I can't confirm everything on my own system although some of the repeatedly reported issues are easy enough like checking how D3D9 and lower settings behave in terms of clock speeds or the registry value for Chill and what it gets set to after a clean uninstall and install of the newest driver.
.
I have problems with frequency boosting in BFV 1080p low settings render ahead off. It boost to 776mhz only!!!! Its a stuttering mess. With my 480 i never had such issues.
OnnA
Senior Member
Posts: 9429
Joined: 2014-10-25
Senior Member
Posts: 9429
Joined: 2014-10-25
#5718197 Posted on: 10/08/2019 05:18 PM
Tested with GR BP, AC:O, GR WL & ME:A -> ReLive OSD working as intended.
Turned On when in Game (today i was testing some new Tweak).
-> https://github.com/GPUOpen-LibrariesAndSDKs/AGS-SDK/releases
I think hes saying before the game starts dont enable osd in desktop. It would be great if osd can be turned on while in game tho.
Tested with GR BP, AC:O, GR WL & ME:A -> ReLive OSD working as intended.
Turned On when in Game (today i was testing some new Tweak).
-> https://github.com/GPUOpen-LibrariesAndSDKs/AGS-SDK/releases
Morax
Member
Posts: 78
Joined: 2016-02-22
Member
Posts: 78
Joined: 2016-02-22
#5718221 Posted on: 10/08/2019 06:17 PM
There's a couple of issues yeah.
Chromium or CEF for Chromium Engine Framework could crash the driver and it's improved but not fixed and if it's specific software like Discord then other software without profiles can still cause problems.
Hardware accelerated media playback has gone from blue screening to crashes to working but causing the GPU to boost to higher levels to just not working so that too needs some work.
D3D9 in particular and overall lower settings that don't engage the GPU's various sensors and metrics for boosting causes it to dip to almost idle speeds at times (As low as 30 MHz.) though the behavior is to force something like VSR and super-sample and then revert to regular resolution which keeps boost active so that too needs work.
Multi display functionality with HDMI and I think also Display Port and then further issues with FreeSync support, multi-display FreeSync support and the ongoing black screen display or full driver or GPU shut downs is another series of issues.
(Partially improved but not fully fixed yet.)
Intermittent display corruption or driver crashes though part of this can probably also be linked to trying to push the VRAM clocks too high since under load they run into error control correction or ECC which maintains stability but instead causes performance to degrade though the behavior can happen on stock settings too.
AMD Chill writing a incorrect registry value and keeping always enabled possibly interfering with other things until removed and manually set to a valid 1 or 0 value.
Wattman possibly using default settings on start until a profile is manually loaded and for Navi the minimum frequency is often outright ignored though putting in a higher value for voltage can reduce stuttering during clock fluctuations which also happen under D3D10 - D3D12 and Vulkan though not as severe as whatever is going on with D3D9 at the moment.
RIS or Radeon Image Sharpening is interfering with D3D12 functionality on a few systems where it just causes a crash if it's enabled.
75Hz and Enhanced Sync have been fixed now so that's resolved and then specific game issues and a couple of other things but there's work to be done.
I might be missing a few things, trying to keep a active list of fixed and known issues mostly the remaining known ones though I can't confirm everything on my own system although some of the repeatedly reported issues are easy enough like checking how D3D9 and lower settings behave in terms of clock speeds or the registry value for Chill and what it gets set to after a clean uninstall and install of the newest driver.
Also pretty sure PCI Express 4.0 and stability is improved for X570 AMD motherboards and using the 1.0.0.3 ABBA bios or later but I've seen mixed reports on that too.
Still liking the hardware (Third week now since picking this up.) but four months in and the software and driver situation is kinda rough so it's tough to actually recommend the GPU unless you're aware that the situation can be a problem and it's costing AMD some sales too with users giving up and returning or selling the cards plus since it can improve by going back to older drivers it's more in the software and not something like a certain batch being a bit busted in hardware though at least that also means a later driver can eventually start fixing this all up and then it can be a smooth experience but that still needs to happen and so far well yeah there's more driver fixes that need to land and get confirmed as fully fixed.
EDIT: As to bug reports and validity well a singular issue isn't much but when it gets reply after reply with others hitting and confirming the same problem then yeah it's probably more likely to be a issue at that point and while some are less susceptible to stutter or framerate dips things like the D3D9 performance problems are easily confirmed too.
So which one causes Netflix to stutter when either it's overlay (dis)appears and when a new line of subtitles appears, but only in "full screen" (I can watch English stuff without subtitles (it's not my motherlanguage), but any other language except my own becomes problematic.
And I do experience the lower/idle clocks and frequencies going all over the place in certain (not well optimised) DX9 games, like Train Simulator. The forcing VSR doesn't work in this case.
There's a couple of issues yeah.
Chromium or CEF for Chromium Engine Framework could crash the driver and it's improved but not fixed and if it's specific software like Discord then other software without profiles can still cause problems.
Hardware accelerated media playback has gone from blue screening to crashes to working but causing the GPU to boost to higher levels to just not working so that too needs some work.
D3D9 in particular and overall lower settings that don't engage the GPU's various sensors and metrics for boosting causes it to dip to almost idle speeds at times (As low as 30 MHz.) though the behavior is to force something like VSR and super-sample and then revert to regular resolution which keeps boost active so that too needs work.
Multi display functionality with HDMI and I think also Display Port and then further issues with FreeSync support, multi-display FreeSync support and the ongoing black screen display or full driver or GPU shut downs is another series of issues.
(Partially improved but not fully fixed yet.)
Intermittent display corruption or driver crashes though part of this can probably also be linked to trying to push the VRAM clocks too high since under load they run into error control correction or ECC which maintains stability but instead causes performance to degrade though the behavior can happen on stock settings too.
AMD Chill writing a incorrect registry value and keeping always enabled possibly interfering with other things until removed and manually set to a valid 1 or 0 value.
Wattman possibly using default settings on start until a profile is manually loaded and for Navi the minimum frequency is often outright ignored though putting in a higher value for voltage can reduce stuttering during clock fluctuations which also happen under D3D10 - D3D12 and Vulkan though not as severe as whatever is going on with D3D9 at the moment.
RIS or Radeon Image Sharpening is interfering with D3D12 functionality on a few systems where it just causes a crash if it's enabled.
75Hz and Enhanced Sync have been fixed now so that's resolved and then specific game issues and a couple of other things but there's work to be done.
I might be missing a few things, trying to keep a active list of fixed and known issues mostly the remaining known ones though I can't confirm everything on my own system although some of the repeatedly reported issues are easy enough like checking how D3D9 and lower settings behave in terms of clock speeds or the registry value for Chill and what it gets set to after a clean uninstall and install of the newest driver.
Also pretty sure PCI Express 4.0 and stability is improved for X570 AMD motherboards and using the 1.0.0.3 ABBA bios or later but I've seen mixed reports on that too.
Still liking the hardware (Third week now since picking this up.) but four months in and the software and driver situation is kinda rough so it's tough to actually recommend the GPU unless you're aware that the situation can be a problem and it's costing AMD some sales too with users giving up and returning or selling the cards plus since it can improve by going back to older drivers it's more in the software and not something like a certain batch being a bit busted in hardware though at least that also means a later driver can eventually start fixing this all up and then it can be a smooth experience but that still needs to happen and so far well yeah there's more driver fixes that need to land and get confirmed as fully fixed.
EDIT: As to bug reports and validity well a singular issue isn't much but when it gets reply after reply with others hitting and confirming the same problem then yeah it's probably more likely to be a issue at that point and while some are less susceptible to stutter or framerate dips things like the D3D9 performance problems are easily confirmed too.
So which one causes Netflix to stutter when either it's overlay (dis)appears and when a new line of subtitles appears, but only in "full screen" (I can watch English stuff without subtitles (it's not my motherlanguage), but any other language except my own becomes problematic.
And I do experience the lower/idle clocks and frequencies going all over the place in certain (not well optimised) DX9 games, like Train Simulator. The forcing VSR doesn't work in this case.
JonasBeckman
Senior Member
Posts: 15621
Joined: 2009-02-25
Senior Member
Posts: 15621
Joined: 2009-02-25
#5718249 Posted on: 10/08/2019 07:30 PM
I wonder if Netflix falls under HDCP which had support added for version 2.3 with Navi in one of the 19.8 driver releases but then Navi in addition also uses VCN instead of the earlier VCE or Video Core Next 1.0 over Video Core Experience so that's a new thing as well if using hardware video acceleration including for the web browser such as with HTML5 including Chrome and other browsers probably also Edge itself and Edge using Chrome though that I think still hasn't fully replaced the default version yet.
Even lower resolution videos could engage the GPU fan though from what I tested of media playback so it clearly boosted enough to kick up the temperature a notch which would be even tougher on 1920x1080 media and also 3840x2160 which VCN should at least have support for to some degree now and Navi GPU's plus the various reported issues with VP9 playback in particular if that encoding is used.
Not too sure how it is with AVC1 and then there's AV1 as well but experimental and limited use for now though I don't think hardware playback for this version of the GPU decoder supported all formats and resolutions fully.
I'm not all that good at media and these changes are also quite new but I do know there's been ongoing issues with support and playback both on Vega and earlier (Though I believe at least the 500 series of Polaris was updated a bit for HDCP I think unlike Vega.) so Navi having other issues there's certainly room for issues and bugs with this too and the later drivers already changed something to resolve a playback issue with media outright blue-screen crashing the system so that in itself just highlights the issues that earlier and current drivers have had to try and deal with and resolve or for users to work around.
More of a acknowledgement than a answer but for Navi there's new features and new bugs, Polaris was brought up in terms of what it supported but Vega never got some of these additions even if they had been discussed formerly but it never happened so at worst it might be pushing the CPU more than GPU and that's what is causing problems here and then full-screen might fall under different rules such as V-Sync which might also be part of it assuming it's true full screen and not borderless giving the GPU exclusive control and other changes to how a exclusive full screen is handled.
Pretty sure I've seen Netflix mentioned several times too so might be a common problem or part of a series of problems around this or other media issues in general both for newer and older GPU models and AMD just has not gotten around to resolving them which I think goes back quite a while by this point.
EDIT: And then Vega and other older and less of the big seller GPU models other than Polaris might not see any quicker action but then RIS was brought over so it's not like it's dropped entirely either but who knows how long this fix could take with all else that is going on.
Prioritizing and all that even if it's a longer standing bug which unfortunately can take quite some time if it's not just forgotten which is something that happens too.
(Happens to both AMD and NVIDIA though I don't have a good overview of unlisted but still very much still present longer standing bugs and issues.)
I wonder if Netflix falls under HDCP which had support added for version 2.3 with Navi in one of the 19.8 driver releases but then Navi in addition also uses VCN instead of the earlier VCE or Video Core Next 1.0 over Video Core Experience so that's a new thing as well if using hardware video acceleration including for the web browser such as with HTML5 including Chrome and other browsers probably also Edge itself and Edge using Chrome though that I think still hasn't fully replaced the default version yet.
Even lower resolution videos could engage the GPU fan though from what I tested of media playback so it clearly boosted enough to kick up the temperature a notch which would be even tougher on 1920x1080 media and also 3840x2160 which VCN should at least have support for to some degree now and Navi GPU's plus the various reported issues with VP9 playback in particular if that encoding is used.
Not too sure how it is with AVC1 and then there's AV1 as well but experimental and limited use for now though I don't think hardware playback for this version of the GPU decoder supported all formats and resolutions fully.
I'm not all that good at media and these changes are also quite new but I do know there's been ongoing issues with support and playback both on Vega and earlier (Though I believe at least the 500 series of Polaris was updated a bit for HDCP I think unlike Vega.) so Navi having other issues there's certainly room for issues and bugs with this too and the later drivers already changed something to resolve a playback issue with media outright blue-screen crashing the system so that in itself just highlights the issues that earlier and current drivers have had to try and deal with and resolve or for users to work around.
More of a acknowledgement than a answer but for Navi there's new features and new bugs, Polaris was brought up in terms of what it supported but Vega never got some of these additions even if they had been discussed formerly but it never happened so at worst it might be pushing the CPU more than GPU and that's what is causing problems here and then full-screen might fall under different rules such as V-Sync which might also be part of it assuming it's true full screen and not borderless giving the GPU exclusive control and other changes to how a exclusive full screen is handled.
Pretty sure I've seen Netflix mentioned several times too so might be a common problem or part of a series of problems around this or other media issues in general both for newer and older GPU models and AMD just has not gotten around to resolving them which I think goes back quite a while by this point.
EDIT: And then Vega and other older and less of the big seller GPU models other than Polaris might not see any quicker action but then RIS was brought over so it's not like it's dropped entirely either but who knows how long this fix could take with all else that is going on.
Prioritizing and all that even if it's a longer standing bug which unfortunately can take quite some time if it's not just forgotten which is something that happens too.
(Happens to both AMD and NVIDIA though I don't have a good overview of unlisted but still very much still present longer standing bugs and issues.)
Morax
Member
Posts: 78
Joined: 2016-02-22
Member
Posts: 78
Joined: 2016-02-22
#5718279 Posted on: 10/08/2019 08:39 PM
I wonder if Netflix falls under HDCP which had support added for version 2.3 with Navi in one of the 19.8 driver releases but then Navi in addition also uses VCN instead of the earlier VCE or Video Core Next 1.0 over Video Core Experience so that's a new thing as well if using hardware video acceleration including for the web browser such as with HTML5 including Chrome and other browsers probably also Edge itself and Edge using Chrome though that I think still hasn't fully replaced the default version yet.
Even lower resolution videos could engage the GPU fan though from what I tested of media playback so it clearly boosted enough to kick up the temperature a notch which would be even tougher on 1920x1080 media and also 3840x2160 which VCN should at least have support for to some degree now and Navi GPU's plus the various reported issues with VP9 playback in particular if that encoding is used.
Not too sure how it is with AVC1 and then there's AV1 as well but experimental and limited use for now though I don't think hardware playback for this version of the GPU decoder supported all formats and resolutions fully.
I'm not all that good at media and these changes are also quite new but I do know there's been ongoing issues with support and playback both on Vega and earlier (Though I believe at least the 500 series of Polaris was updated a bit for HDCP I think unlike Vega.) so Navi having other issues there's certainly room for issues and bugs with this too and the later drivers already changed something to resolve a playback issue with media outright blue-screen crashing the system so that in itself just highlights the issues that earlier and current drivers have had to try and deal with and resolve or for users to work around.
More of a acknowledgement than a answer but for Navi there's new features and new bugs, Polaris was brought up in terms of what it supported but Vega never got some of these additions even if they had been discussed formerly but it never happened so at worst it might be pushing the CPU more than GPU and that's what is causing problems here and then full-screen might fall under different rules such as V-Sync which might also be part of it assuming it's true full screen and not borderless giving the GPU exclusive control and other changes to how a exclusive full screen is handled.
Pretty sure I've seen Netflix mentioned several times too so might be a common problem or part of a series of problems around this or other media issues in general both for newer and older GPU models and AMD just has not gotten around to resolving them which I think goes back quite a while by this point.
EDIT: And then Vega and other older and less of the big seller GPU models other than Polaris might not see any quicker action but then RIS was brought over so it's not like it's dropped entirely either but who knows how long this fix could take with all else that is going on.
Prioritizing and all that even if it's a longer standing bug which unfortunately can take quite some time if it's not just forgotten which is something that happens too.
(Happens to both AMD and NVIDIA though I don't have a good overview of unlisted but still very much still present longer standing bugs and issues.)
Netflix requires HDCP 2.2 for 4K/HDR, which also requires PlayReady 3.0. The latter is still missing on Vega, but stutters occur with HD-streams and even SD ones (like Star Trek DS9). And it's 'fullscreen' mode appears to be borderless (at least in case of the Win 10 app).
It's some issue with Netflix's overlay texts and stuff. Maybe some codec issue indeed.
Changing motherboard/CPU didn't solve it, and neither did any of this year's drivers, or any reinstallation of Windows 10. The problem didn't exist on my GTX 1080 I had before (and that one actually DID support PlayReady 3, but it didn't do FreeSync…. well, not last year…)
I wonder if Netflix falls under HDCP which had support added for version 2.3 with Navi in one of the 19.8 driver releases but then Navi in addition also uses VCN instead of the earlier VCE or Video Core Next 1.0 over Video Core Experience so that's a new thing as well if using hardware video acceleration including for the web browser such as with HTML5 including Chrome and other browsers probably also Edge itself and Edge using Chrome though that I think still hasn't fully replaced the default version yet.
Even lower resolution videos could engage the GPU fan though from what I tested of media playback so it clearly boosted enough to kick up the temperature a notch which would be even tougher on 1920x1080 media and also 3840x2160 which VCN should at least have support for to some degree now and Navi GPU's plus the various reported issues with VP9 playback in particular if that encoding is used.
Not too sure how it is with AVC1 and then there's AV1 as well but experimental and limited use for now though I don't think hardware playback for this version of the GPU decoder supported all formats and resolutions fully.
I'm not all that good at media and these changes are also quite new but I do know there's been ongoing issues with support and playback both on Vega and earlier (Though I believe at least the 500 series of Polaris was updated a bit for HDCP I think unlike Vega.) so Navi having other issues there's certainly room for issues and bugs with this too and the later drivers already changed something to resolve a playback issue with media outright blue-screen crashing the system so that in itself just highlights the issues that earlier and current drivers have had to try and deal with and resolve or for users to work around.
More of a acknowledgement than a answer but for Navi there's new features and new bugs, Polaris was brought up in terms of what it supported but Vega never got some of these additions even if they had been discussed formerly but it never happened so at worst it might be pushing the CPU more than GPU and that's what is causing problems here and then full-screen might fall under different rules such as V-Sync which might also be part of it assuming it's true full screen and not borderless giving the GPU exclusive control and other changes to how a exclusive full screen is handled.
Pretty sure I've seen Netflix mentioned several times too so might be a common problem or part of a series of problems around this or other media issues in general both for newer and older GPU models and AMD just has not gotten around to resolving them which I think goes back quite a while by this point.
EDIT: And then Vega and other older and less of the big seller GPU models other than Polaris might not see any quicker action but then RIS was brought over so it's not like it's dropped entirely either but who knows how long this fix could take with all else that is going on.
Prioritizing and all that even if it's a longer standing bug which unfortunately can take quite some time if it's not just forgotten which is something that happens too.
(Happens to both AMD and NVIDIA though I don't have a good overview of unlisted but still very much still present longer standing bugs and issues.)
Netflix requires HDCP 2.2 for 4K/HDR, which also requires PlayReady 3.0. The latter is still missing on Vega, but stutters occur with HD-streams and even SD ones (like Star Trek DS9). And it's 'fullscreen' mode appears to be borderless (at least in case of the Win 10 app).
It's some issue with Netflix's overlay texts and stuff. Maybe some codec issue indeed.
Changing motherboard/CPU didn't solve it, and neither did any of this year's drivers, or any reinstallation of Windows 10. The problem didn't exist on my GTX 1080 I had before (and that one actually DID support PlayReady 3, but it didn't do FreeSync…. well, not last year…)
Benik3
Senior Member
Posts: 489
Joined: 2011-07-28
Senior Member
Posts: 489
Joined: 2011-07-28
#5718316 Posted on: 10/08/2019 10:40 PM
You are mistaken and I know better what I need. Freesync is for everybody. I use it to play videos at proper speed...
What do you use for playing video with FreeSync support?
Because what I know, this was discussed many times with result, that it's not possible...
You are mistaken and I know better what I need. Freesync is for everybody. I use it to play videos at proper speed...
What do you use for playing video with FreeSync support?
Because what I know, this was discussed many times with result, that it's not possible...
Eastcoasthandle
Senior Member
Posts: 2150
Joined: 2006-05-22
Senior Member
Posts: 2150
Joined: 2006-05-22
#5718324 Posted on: 10/08/2019 11:13 PM
Do you mean to have the option disabled from Radeon Settings, or not having the overlay with the stats before launching the game?
Overlay is enabled by default after installing the drivers, but can be disabled easily under Preferences.
Thanks, but the overlay is enabled at desktop
ops:
I really don't see the need to have this enabled at desktop.
What I am seeing is that in BO4 the OSD remains on even after you exit the game. It's suppose to "turn off" when you are at desktop. This is what appears to trigger the blackscreen. Turning the monitor on/off returns the image of the desktop with the osd in the upper right corner.
Do you mean to have the option disabled from Radeon Settings, or not having the overlay with the stats before launching the game?
Overlay is enabled by default after installing the drivers, but can be disabled easily under Preferences.
Thanks, but the overlay is enabled at desktop
ops:I really don't see the need to have this enabled at desktop.
What I am seeing is that in BO4 the OSD remains on even after you exit the game. It's suppose to "turn off" when you are at desktop. This is what appears to trigger the blackscreen. Turning the monitor on/off returns the image of the desktop with the osd in the upper right corner.
GREGIX
Senior Member
Posts: 538
Joined: 2004-09-20
Senior Member
Posts: 538
Joined: 2004-09-20
#5718344 Posted on: 10/09/2019 12:16 AM
This driver is bugged for me, as 19.3.3 too. No RIS. Windows resizing make smudges?, multiple images of that window, on FF or just folders view. This sucks.
Radeon 7
This driver is bugged for me, as 19.3.3 too. No RIS. Windows resizing make smudges?, multiple images of that window, on FF or just folders view. This sucks.
Radeon 7
Click here to post a comment for this news story on the message forum.
Senior Member
Posts: 2369
Joined: 2012-10-22
It is not profitable at all. Lost working days and coding hours from software developing are more expensive than a cheap radeon vii. 1% of users use crossfire nowadays. There is no point from any perspective.