FYI........................
Here are 2 snippets of dxdiag's of my Team Red box w\ AMD's HBCC enabled in 1 and disabled in the other.
Please note the graphics card mem stats in both dxdiag reports to see what HBCC is doing w\ extra system mem to set up the onboard HBM2 mem as a "last-level cache".
I'm running w\ HBCC enabled but not due to the usual reasons as given for using this as the 8Gb of HBM2 onboard mem is more than enough so this card will not run out of HBM2 mem or "cache" w\ HBCC disabled..............
There is a You-Tube video out of a couple of folks who interviewed Raja Koduri at Siggrath when Rx Vega was launched that asked him about how this HBCC worked and Raja said himself that the aspect of HBCC's ability to use system mem to offload lesser used data from the HBC (onboard mem) to retain the most used data in the HBC was not needed at this time due to the 8Gb of HBM2 onboard (he referred to this as "forward looking" meaning that this asset would come into it's own in the future, especially when gamers start using very high resolution graphics in excess of 4K) but he did say that the asset of HBCC's AI coding can be taken advantage of right now by using it to preempt data loading ahead of time so that the GPU doesn't have to wait for data to be loaded into the cache to use it and to maintain the most needed data at the very front of the cache to reduce latency.......such as needed textures to display in a scene while running a game in motion. He gave an example of a 1st person shooter game in which you would turn around a corner to encounter a bad guy who is about to shoot you so you try to get a shot off 1st but in the process of getting your weapon on target your system hesitates momentarily to load textures (read draw calls here) to continue to draw\render\display the scenes smoothly in motion which keeps you from shooting before the bad guy does so you die due to the system not having the textures already loaded ahead of time.......Raja said this asset of HBCC is why you would want it enabled right now. He also said that HBCC could benefit immediately due to most games typically over report the amount of onboard graphics mem that they actually need to ensure that they have enough mem available so HBCC using it's AI can distinguish between the amount of onboard mem that the game reports that it needs vs the amount that the game is actually using to then only allocate the actual amount of "cache" that the game is using which can then reserve the remainder for other duties instead of being taken up but not being used which can help w\ overall system latency.
It is due to this response by Raja is why I have HBCC enabled. I let the driver auto set the amount of system mem to use in tandem w\ the 8Gb of HBM2 mem which is approx. 4Gb as shown between the 2 dxdiag reports.
So far all shows to be working very well while flying AHIII as the game play is very, very smooth and responsive thruout.
So if you have 1 of these cards installed you might try it out as HBCC is disabled in the drivers by default but is active.
