AMD Fury X Owners' Thread

Test this in some 3Dmark (if it's really working).
Should give You some 200-400pts IMhO.

 

Have its issues but still a beast even today.

 

^^ Only if Fury had HBCC
Think about it....

 

If only had more than 4gb vram.

 

I did same thing on some older Trixxx years ago. Maybe 5.2.1? Also, nice Core Clock. I never passed 1070MHz, but my HBM is on rocksolid 600MHz for almost three years. Quid pro quo.

 

I spent a couple hours extensively testing clock speed changes on the core and memory today. Unfortunately it seems although Trixx increases the clock speed at the software level, it does not appear to translate to the hardware level. Improvements from 500-650Mhz seemed to be negligible and within margin of error. Every benchmark and piece of software appears to show a clock speed change yet the performance just doesn't reflect it.

 

AMD Memory Tweak for Vega is working, it gives ~200-400pts in 3Dmark FS and better min. 0.1% in games.
We need to always test, placebo is not the way

 

https://i.imgur.com/GQac4dM.png
Take a look on my settings.

 

Not much to tell (i don't have Fury )
If it's working then OK, check in Your favorite game (long session).

 

I wanted to share my settings with FlawleZ, if he would like to use AMD Memory Tweaker

 

One of the reasons you see no change with adjusted memory frequency is that the memory timings get loosened to compensate - You also need to OC HBM in steps (I think it's 5MHz steps?) I can do 525MHz but if I do 550MHz, my framerate gets cut in half, 600MHz I can do just about but will need to tweak timings to get any improved latency. Nevertheless, increasing the bandwidth helps throughput (so fps in higher resolutions), it doesn't necessarily help improve max fps - that's where tweaking the timings comes along.

@Fox2232 Is the best person to ask about this.

 

The Fury was not a flop. AMD marketing was.

I had a Nitro+ Fury and sitll have my fury X.
If it had 6GB+ vram, id still be using it.
It surprisingly does really well with my new 3840x1080 144hz monitor. It struggled very badly in 2017+ newer titles when I had my 3440x1440 100hz. It was a vram issue.

 

Hi. HBM in Fiji behaves irregularly.
1st is actual clock. Memory does not really clock at speed you select. It clocks at bands. vBIOS of My Fury X had bands:
474~523 MHz
524~573 MHz
574~623 MHz

From practical standpoint there is no difference between running 524 or 573 MHz, clock is same.
But then there are timings strips:
0~100 MHz
101~400 MHz
401~500 MHz
501~600 MHz (Used above this range too.)

In reference card's vBIOS, 401~500 & 501~600MHz were equal. So one could quite safely alter 501MHz+ strip and keep card at 500MHz stock to ensure card will not have troubles booting during experiments. And it enabled easy side by side performance comparisons.
- - - -
But then comes time into play. And sad fact that AMD disabled Fiji's ability to OC HBM via increase of clock by driver change. Can't say if they reenabled OC later, but any time someone came to believe they got OC back, they did not. If OC works, there should be around 6% performance difference just by moving from 523 to 524MHz.
What remains is tightening memory timings.

And from that comes paradox. While actual clock does not change as you move from 500MHz, highest timing strip is still loaded as you move to 501MHz and above.

And side note, I have not seen or heard of single Fiji GPU that had stable memory at 624MHz and above. Some crash immediately, some fail under any load. Some artifact. Some fail at compute. Even messing with voltage up and down did not help. Which is quite funny. (Especially since HBM1 standard says 1.2V and AMD did run them at 1.3V.)
So, as long as @FlawleZ is clocking 650MHz, we can be quite sure that card is not actually OCing HBM.

 

Let's talk about performance in Cyberpunk 2077. Game runs... fine?
If you can stand medium setting with low cascade shadow resolution disabled SSR (my personal choice, because high value is too heavy and low is too "shimmering")
Dynamic FidelityFX to 65%-100% range + RIS for 80% and you get playable 60fps experience, even in combat.
Im sure i will re-play this game on my new rig in future. Maybe in next two years.
It's like Deus Ex 9. I love it so much.

EDIT:
I forget to add.
There is no issue with 4GB VRAM and High textures.

 

Are you sure? Most youtubers and reviewers said 4gb = medium textures. High settings goes up to 6gb vram usage.

 

Yeah, i never seen pop-up texture or stuttering because lack of VRAM in my 20 hours gameplay for now.
I know how it looks, i remember Resident Evil 7 and High textures. Fortunately medium settings using same quality textures, just with decreased memory budget.

Cyberpunk 2077 uses 3.5-3.7GB here. I guess there is some intelligent in-game texture storage system. Check GTX 1650S, same situation.
Also i can recommend using static FidelityFX.
In some section of city CPU is bottleneck, so Dynamic Fidelity using lowest resolution possible to get more fps, of course it didn't happend.

 

you won't see popup, you'll see bubble-in because thats how the engine visually handles lod blending

 

Nothing like that happened.

 

Thanks for sharing. I tried applying those settings and I get an error from the AMD Memory Tweak XL stating "Changing memory is unfortunately not supported due to driver limitations"

 

Up