Zathalus
Member
4080 above 5080 doesn't look right. Day 1 patch fix incoming??
According to the pinned comment, mistakes in the graph. The 4060 is 18fps for example.Why is the 4060 beating the 4070?
4080 above 5080 doesn't look right. Day 1 patch fix incoming??
According to the pinned comment, mistakes in the graph. The 4060 is 18fps for example.Why is the 4060 beating the 4070?
Noticed that, too. And the 5080 outperformes the 4080 on a lower preset. Kinda weird, indeed.4080 above 5080 doesn't look right. Day 1 patch fix incoming??
Crimson Desert Benchmark: 40 GPUs Tested
Preset Scaling Performance
![]()
Upscaling Performance
![]()
Cinematic 1440p
![]()
High Preset 1440p
![]()
ugh my 4090 is obsolete. That FPS is atrocious. I need a 5090 bad
And it seems like Digital Foundry screwed up with their benchmarks for RR.
![]()
HU also concludes that it's extremely taxing.And it seems like Digital Foundry screwed up with their benchmarks for RR.
![]()
wtf is "cinematic"?
Optimization guide.
HU also concludes that it's extremely taxing.
![]()
![]()
I think it's because perhaps they had a different build. HU had the review build and lighting quality there maxed out at Cinematic. Alex made no mention of a Max setting like HUB does, this was seemingly added later. He probably had an earlier test build.One thing to consider is that the option for RR, increases graphics quality to an extreme preset. So the loss is not just due to RR overhead. Most of it is probably just the increased detail.
The other thing to consider, is that, just like with Computerbase, RR on AMD and NVidia have a similar performance impact. Proving that DF's numbers were incorrect.
Of course quality is another problem for AMD.
I think it's because perhaps they had a different build. HU had the review build and lighting quality there maxed out at Cinematic. Alex made no mention of a Max setting like HUB does, this was seemingly added later. He probably had an earlier test build.
Yeah there's no way the 4090 is barely faster than the 4080S and the gap between the 4090 and 5090 is too big also imho. Smells like RE9 all over againUnless there's a lot of mistakes there's a lot of cards close together at 1440p cinematic. That suggests it's CPU bound, but the 5090 proves it's not.
Yeah this. Best investment ever. And I could sell it now for more than i paid for it at launch over 3 years ago, it's crazy.I've gotten so much mileage out of my 4090. It's absolutely ridiculous. Thanks for sharing!
I've gotten so much mileage out of my 4090. It's absolutely ridiculous. Thanks for sharing!
Much more in-depth compared to every other channel, but I find it interesting how Steve brought up numerous bugs, slow load times, and CTDs, when Hardware Unboxed mentioned no such things. He also had the public build, whereas Steve and Tim seemingly had a pre-release/review build.
Of not, is how wildly the 1% lows swung on his system with the 5060 Ti, but from what HU said, it was fairly stable. I also haven't seen many people complain about the performance or stability either.
Edit: Also forgot to mention I think HU's methodology was lacking. All Steve from HU did was run a 40 seconds pass through a town. GN ran multiple passes under multiple different scenarios.
Much more in-depth compared to every other channel, but I find it interesting how Steve brought up numerous bugs, slow load times, and CTDs, when Hardware Unboxed mentioned no such things. He also had the public build, whereas Steve and Tim seemingly had a pre-release/review build.
Of not, is how wildly the 1% lows swung on his system with the 5060 Ti, but from what HU said, it was fairly stable. I also haven't seen many people complain about the performance or stability either.
Edit: Also forgot to mention I think HU's methodology was lacking. All Steve from HU did was run a 40 seconds pass through a town. GN ran multiple passes under multiple different scenarios.
Also thought he had a faulty system, but he had 3 test benches and all had problems.Yes, it was very in-depth, especially the time animations.
But he didn't run all those 20 runs he showed, for every GPU. He did that for one or two, picked the scenario that was most consistent and that was closes to the average and then ran all other GPUs only on that city path.
Then there were somethings that were strange. The pink squares he showed, I don't think that anyone else had this problem. And if it had happened with HU, Tim and Steve would have referenced it, as they usually do.
But this type of problem usually shows up either with a bad shader compilation, or with faulty ram/vram.
The game crashes to desktop, usually indicate a software problem. Though it can also be hardware related. So that can be the game having issues.
But when a system hard crashes to the UEFI boot, that is a hardware problem. Usually a bad PSU or bad memory. Though it can also be a bad CPU or motherboard.
It's not a game problem.
After seeing all he went through, I strongly believe he had a faulty system. And that was what was causing most of his problems.
Also thought he had a faulty system, but he had 3 test benches and all had problems.
Whatever the case, I really hope they fo something about RR deleting the rain.
GG on the 3080 still pulling 60 @ 1440p/Max settings w/o DLSS
And they said 10GB would make it useless
Game still looks better than 95% of games on the market today soIt is a problem for many other games.
Pear Abyss hard locked VRAM usage in this game, on cinematic settings + 4K output it still is mostly compatible with 8GB GPUs... Why the fuck limit the game like that?
Game still looks better than 95% of games on the market today so![]()
100%True. But they could use that memory to reduce pop in.