- Jan 5, 2017
- 3,821
- 3,642
- 136
Looks like AMD GPUs are CPU-bound and possibly the lack of PCIe lanes/memory bandwidth really hurts the low end AMD GPUs a lot.
Those Navi 24 numbers... woof. Really makes the 6600 look like a much better deal in comparison.
RX 6400/6500, GTX 1630 and Arc A380 are in a league of their own.Those Navi 24 numbers... woof. Really makes the 6600 look like a much better deal in comparison.
Agreed, this game is perfectly fine at 60-75fps. Ray tracing is where it becomes useful to prospective hardware buyers. Otherwise it scales well.Although I suspect we will see it more with future console ports. Although, at over 100 fps not sure how much of a bottleneck this really is.
With the upcoming driversRX 6400/6500, GTX 1630 and Arc A380 are in a league of their own.
The greater unknown is the potential in the software.There is potential in the hardware.
It is an interesting review!
The AMD "bottleneck" feels related to the real time shader compilation, which is something somewhat "unique" to this game. I suspect we will see it more with future console ports. Although, at over 100 fps not sure how much of a bottleneck this really is.
He did run it with a Ryzen 5800x3d, which is one of thee best CPUs for that game.
Be curious if he does a CPU follow up on it. Curious as to how the lower end units do, and if AMD pulls ahead as the CPU gets weaker.