AMD Radeon R9 Fury X Reviews

@gongo said:

lol !

will HBM be like GDDR5 with error management detection...when you over-overclock the memory, the graphics will still run but you get worse performance?
 
@fellix said:

The argument against the FuryX wrt memory is the same as the on that was made against the GTX680 with its 1.5GB vs the 2GB of the 7970. Or against the 3GB of the 780Ti vs the 4GB against the R9 290X.
GTX680 comes with 2GB as well. Maybe you're thinking about the older GTX580, but it wasn't meant to compete with Tahiti anyway.
 
@3dilettante said:

lol !

will HBM be like GDDR5 with error management detection...when you over-overclock the memory, the graphics will still run but you get worse performance?
GDDR5 implemented a CRC check to allow it to reach high bus speeds while maintaining an acceptable error rate. HBM has dropped that feature since it has dropped the very high bus speeds.
There is a provision in the spec to allow for ECC, if the DRAM in the stack decides to implement it, but I don't think that is showing up as a consumer option.

One thing I am looking for is whether thermal effects can cause HBM to enter into a high-temperature refresh mode for insufficiently cooled air-cooled cards.
 
@firstminion said:

Everybody who expected FuryX to perform worse at 4K with today's games didn't pay attention to benchmarks for other GPUs. Even with the GTX970, it wasn't trivial to come with convincing examples where the 512MB less made a major difference.

As long as the working set fits the memory, it doesn't matter how much more GB there are on board.

The argument against the FuryX wrt memory is the same as the on that was made against the GTX680 with its 1.5GB vs the 2GB of the 7970. Or against the 3GB of the 780Ti vs the 4GB against the R9 290X.
It may be a problem in the future, but right now, you have to look hard to find any issues with it. The only difference is that the 4GB is a structural limitation of HBM1 where it was a pure cost issue for the GTX680/780Ti in the past.

Sorry if I'm out of the loop, but you can't grasp that from topics like Is4Genough?.
 
@Jawed said:

http://forums.overclockers.co.uk/showpost.php?p=28248073&postcount=1944

I noticed that in MSI Afterburner in the settings menu, after I enabled extendofficialoverclockinglimits and rebooted I was able to OC the memory.

He posted GPU-Z screenies later. He's only overclocked by 50Mhz.

He, like seemingly half the people posting on the OcUK forum, is experiencing unpleasant pump noise (as opposed to normal pump noise). I suspect this is going to erupt soon, especially as OcUK won't replace them as faulty, despite the fact that AMD said they are faulty and should not be in retail.
 
@3dilettante said:

Possibly, there's the foam rubber insert hack that was noted earlier, but that is unfortunate since this time it seemed like AMD had done the right thing by contracting the cooler out to the specialists. Perhaps their inventory tracking is not as good as they think, this is not the same pump whine as before, this is a case of high-frequency hearing loss among the quality-control staff, or their quality control's rigor may be as suspect as before.
Does Cooler Master have other examples of this? It seems off that they'd let this out of their manufacturing process, but they obviously did for the review samples.
 
@gamervivek said:

How did this lesser known site managed to overclock the HBM while the rest couldn't? GPU-z error?

The core clock was also overclocked higher, as do the CPU clock..so they are not a like for like comparison?

20Mhz on core clock and like 100Mhz on CPU are quite like to like. Though other user didn't report that big of an increase with 10% overclock.

crossfire scaling in some games by AMDmatt,

http://www.overclock.net/t/1561860/various-amd-radeon-r9-fury-x-reviews/2530
 
@pharma said:

Fury X CrossFire vs reference SLi 980ti results are incoming ...

Poor man's transulation:
For this test, we briefly observed fluidity tested in each game. First, as we have already seen several times in bi-GPU and 4K, the Radeon generally have a small advantage over the GeForce at the felt. We assume here that the SLI link is reaching its limits, whether the frame pacing algorithms Nvidia are not fully functional in very high resolutions.

However, in any game we did not encounter any real fluidity problem on GeForce GTX 980 Ti SLI, unlike the Radeon R9 Fury X CFX suffering in 3 games:

- Dying Light max: very heavy jerks, unplayable
- Evolve medium: jerky at times, mainly early in the game
- Evolve very high: jerky at times, mainly early in the game
- The Witcher 3 medium: regular small jerks
- The Witcher 3 max without Hairworks: regular small jerks
- The Witcher 3 max with Hairworks: big jerks, very unpleasant

Note that in all these games the Radeon R9 295X2 suffers from the same problems, which are exacerbated by the lower level of performance.

...
Then, with Evolve and especially Dying Light, we could observe realistic and playable situations where it seems obvious that the memory of 4 GB per GPU is insufficient. To solve the problem, the only solution is to reduce the current level of detail textures, and it remains to seen if AMD can improve the behavior of Fury X with future drivers.

Example, we can already see that the Evolve jerks subside after a short playing time, signs of a gradual reorganization of the remaining data in memory. It is not the case in Dying Light that gradually adds new textures in an already saturated memory and causes big jerks. AMD said that its priority approach was to work with developers to ensure a more efficient conduct of their vis-à-vis gaming memory usage. An ideal approach, but that can have its limits if not everyone accepts to make efforts.

http://www.hardware.fr/focus/111/crossfire-radeon-r9-fury-x-fiji-vs-gm200-round-2.html
 
@gamervivek said:

Far Cry 4 now runs smooth as butter on 295x2 in TR's recent review of 980Ti while it ran pretty badly during Titan X's release. AMD won't get all developers to play ball like that and of course it doesn't matter much if the game is fixed months after everybody has had their fill of it.

Another HBM overclock and a decent performance increase at 1080p/win7 in kombustor test. From 49 to 57fps just by HBM overclocking. 105Mhz on core only gives 1fps increase in comparison.

http://www.overclock.net/t/1547314/...nano-x-x2-fiji-owners-club/1720#post_24106947

Newest version of gpuz also shows the correct bandwidth value.
 
@ToTTenTranz said:

A little context from that Hardware.fr quote:
They're complaining about stuttering from 3 games, out of a total of 12 tested games:

[ Anno 2070 ]
[ Batman Arkham Origins ]
[ Battlefield 4 ]
[ Crysis 3 ]
[ Dying Light ]
[ Evolve ]
[ Far Cry 4 ]
[ GRID 2 ]
[ Hitman Absolution ]
[ Project Cars ]
[ Splinter Cell Blacklist ]
[ The Witcher 3 ]
[ Tomb Raider ]




- The Witcher 3 max with Hairworks: big jerks, very unpleasant

Agreed, no one likes big jerks. They're really unpleasant.
Those jerks...
 
@pjbliverpool said:

Far Cry 4 now runs smooth as butter on 295x2 in TR's recent review of 980Ti while it ran pretty badly during Titan X's release. AMD won't get all developers to play ball like that and of course it doesn't matter much if the game is fixed months after everybody has had their fill of it.

Another HBM overclock and a decent performance increase at 1080p/win7 in kombustor test. From 49 to 57fps just by HBM overclocking. 105Mhz on core only gives 1fps increase in comparison.

http://www.overclock.net/t/1547314/...nano-x-x2-fiji-owners-club/1720#post_24106947

Newest version of gpuz also shows the correct bandwidth value.

I find it amazing that even with HBM + Colour compression, this GPU is STILL bandwidth limited!
 
@pharma said:

Fury X DriverGate testing results - no magic sauce.

Conclusion: No Difference
As shown in the charts above, all differences are within margin of error. There is effectively no difference from one driver revision to the next when considering only the existing Fury X options. For these purposes, reviews which were conducted using press drivers – assuming no other test error – can be considered effectively as accurate as reviews conducted using official launch drivers.

http://www.gamersnexus.net/guides/1996-amd-r9-fury-x-driver-benchmark

Edit: Url fixed.
 
@silent_guy said:

I find it amazing that even with HBM + Colour compression, this GPU is STILL bandwidth limited!
I'm not (yet) willing to accept that: if the memory timings (in cycles) don't change with increased clocks, it could be due to reduced latency as well.
 
@3dilettante said:

Utilization figures in some of the tests like the Techreport's show a sizeable gap between theoretical and realized bandwidth, and AMD's color compression appears to be about as helpful as last-gen Nvidia compression.
Maybe in an ideal world it wouldn't be limited in certain scenarios, but at least some measurements show that utilization is far enough from peak to be a factor.
 
@homerdog said:

I am reading about and seeing some videos showing the Fury Xes emitting some horrible noise from the watercooling pump. In fact PCPer's 2 retail samples are worse than their review sample. Does anyone here actually have a Fury X to test this?
 
@3dilettante said:

Anecdotal reports appear to have some samples without noise, but multiple with it.
PC Perspective's using retail cards, so it appears to be a substantiated data point.

Best-case, AMD's statement to reviewers was factually inaccurate with respect to some number of retail cards, which would join an impressive run of divergences from reality that executives, documentation, and emails have provided for this product and its rehashed launch brethren.
I can think of two worst-case scenarios, one where AMD's factual inaccuracy to reviewers and paying customers is a universal departure from reality, and one where there was a problem that was fixed, but it's not the same one and it's not AMD's statements but AMD itself that remains in another reality.

I could go on, but maybe someone can track down an mp3 of silence, then a long sigh of resignation, then the sound of someone running their hand down their face, then going Christ.
 
Back
Top