Discussion in 'Videocards - AMD Radeon Drivers Section' started by mtrai, Dec 17, 2019.
I've heard of that happening and IMO seems like some sort of sabotage for AMD Radeon users.
LOL, did you forget the "/s"?
seems amd pushed out a newer branch at the end of the year, obvious it wasn't quite ready imo, since they did not release a pro driver on the same branch, instead publishing a slightly newer version of the older branch.
That integer scaling can either save your day or kill it.
Many games are godlike (old ones) but heavier ones like...Diablo II for my instance are unplayable. Why AMD?
Supposedly drivers and hardware should fix all problems of distant past. OpenGL and pre-DX9 gaming shall never be fixed according to a minority of engineers it seems.
Waiting for 20.1.1 for some more fixes, fot me its very stable though.
The Division 2 don't like (badly) HBCC.
I found the solution today
No HBCC and Game is working NP.
DX11 & DX12 alike, now Playing w/DX12 no crashes & performance is Great.
I'm still waiting for the Vega64 to work properly I decided not to sell any card that I have.
and why its not working properly?
There is one profile, custom and its itill not saving on boot. Overclocks are there but fan is not kept. I have to reset every damm time.
I had the same problem. I fixed it by deleting all the profiles and just using the global settings.
This is definite problem with the GUI of this new driver.
Because COD MW freezes 5-10 seconds. I also have 2080ti 1080ti and 1070 none of those nvidia cards have any problems with COD MW 2019.
I've tried the 19.12.2 and 19.12.3 and its still the same between the two of them.... also like Undying said Wattman is borked again and it doesnt load the profile all the time.
I'm just a little bit tired with AMD GPUs for the time being since more problems appear and the old ones keeps hunting them ...
I think every resource they have goes to CPUs since they done a great thing there but for the videocards its still a mess lagging behind green team for far too long ... We need a "Ryzen" GPU here because even 5700XT is not a big deal by any means and the problems it has I'm really happy I don't have one.
P.S. I accept Vega64 for what marvelous piece of hardware it was at launch and I dont care its a true space heater (I'm running at above 300W most of the times going towards 350-380W) but the only thing I demand is good stable performance and no issues in latest AAA titles and that sadly is not happening for me.
My GF has this exact problem in CoD running a 5700xt. Been driving me mad trying to find a fix. On the other hand, I don't have this issue running on a Radeon VII. I am surprised that Vega is having the freezing issue consider it's the same architecture as Radeon VII.
Cache for Sun Spots and Sun Shadows is not working correctly. AMD users have to turn it off.
Or else sabotage. For AMD users it constantly running in the background.
I even reinstalled Windows 10 trying to find a cure ... Have to check Sun Spots and Sun Shadows solution asap ... Will put Vega back in a PC and test tomorrow.
Try to Disable (for Problematic games) HBCC, it helps me solve -Unplayable- The Division 2 Problem.
Now game runs great at Ultra + AA on DX12.
Before that even the DX11 was unplayable, DX12 was crashing right from the start, now it glorious
Yes DX12 is the way to go with Division 2 -> Unmatched performance, smooth as butter.
I've never enabled HBCC again since it gave me problems in Division 2 one year ago ... Never used it because it caused more problems for me than anything that can be considered an actual gain ....
Excuse my ignorance but what is HBCC?
HBM2 High bandwidth memory controler aka HBM2 Cache (Only in Vega & Radeon VII and in the near future in Big Navi).
Task Scheduler Configuration Tool (Schtask.exe) added to Task Manager after 19.12.3 install.
Can anyone else check to see if you are seeing this task in task manager? I'm seeing 2 of these after installing the drivers. Once I uninstall the driver they go away.
One has something to do with AMD Link and the other the installer.
These shouldn't be popping up like this in task manger IMO.