They didn't run anything with RTX on, probably because AMD cards don't have DXR drivers, yet, so there is no competition to compare it to. It would take a subjective judgment to say "using XYZ setting with RTX on looks better and runs faster, let's take a look at those numbers." There is a place in the games/hardware enthusiast sphere for some analysis along those lines, but Anandtech doesn't seem to try to fill that niche.
Oh, I must have been confused, I thought this was a review for new nVidia parts, I guess you are saying it's a feels feels article for people who own the lone four year old AMD part.......?
Use lower quality settings that are markedly slower, ignore both a significant portion of the die space and the relevant performance implications of said die space and purposefully avoid any RTX benches of an RTX card for an RTX review.
That is what you are defending. Reasonable, if you think so :)
Benchmarks that can't be run on a wide variety of hardware are meaningless.
If nVidia wants to include special features that only RTX cards can utilize, that's fine. But there's no sense including them in a general-use benchmark, because there's only a tiny handful of cards that can use them, and they're all the same chip anyways.
I'm sure nVidia will be glad to tell you how many RTX Ops(bungholiomarks, whatever) the new cards get. It will remain a meaningless number.
Also, the performance implications of the die space are "lost shaders". nVidia put this in solely for the compute market and THEN turnd around to try and figure out a gimmick they could sell it to gamers with to obscure the meaningful performance loss.
Ray tracing is a feature of DirectX 12. Metro exodus is using the DirectX 12 implementation for ray tracing.
DXR runs on non RTX cards just fine, simply requires driver support for a DirectX feature.
The ray tracing cores don't move the needle for general compute at all, don't know what helmet head told you that but they have no clue what they are talking about. The tensor cores, otoh, those are very useful for certain compute tasks, they are only used for denoising on the ray tracing side, they aren't the intersection compute units, the feature they bring to the table is DLSS and we can all ignore that forever and that's fine.
The key new feature for the next gen consoles, the big feature every engine developer is pushing for, what had been considered the holy grail of real time graphics for decades, that I don't get why you would ignore in an article with RTX as the subject.
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
Facebook
Twitter
RSS
281 Comments
View All Comments
BenSkywalker - Tuesday, July 2, 2019 - link
Running Metro on the ultra setting using an RTX card is painful, RTX mode is *faster* and looks *way* better, why did you do this?Yojimbo - Tuesday, July 2, 2019 - link
They didn't run anything with RTX on, probably because AMD cards don't have DXR drivers, yet, so there is no competition to compare it to. It would take a subjective judgment to say "using XYZ setting with RTX on looks better and runs faster, let's take a look at those numbers." There is a place in the games/hardware enthusiast sphere for some analysis along those lines, but Anandtech doesn't seem to try to fill that niche.BenSkywalker - Tuesday, July 2, 2019 - link
Oh, I must have been confused, I thought this was a review for new nVidia parts, I guess you are saying it's a feels feels article for people who own the lone four year old AMD part.......?Yojimbo - Tuesday, July 2, 2019 - link
Oh, I must have been confused. I thought I was talking to a reasonable person. Guess not, so I won't bother.BenSkywalker - Tuesday, July 2, 2019 - link
Use lower quality settings that are markedly slower, ignore both a significant portion of the die space and the relevant performance implications of said die space and purposefully avoid any RTX benches of an RTX card for an RTX review.That is what you are defending. Reasonable, if you think so :)
Lord of the Bored - Tuesday, July 2, 2019 - link
Benchmarks that can't be run on a wide variety of hardware are meaningless.If nVidia wants to include special features that only RTX cards can utilize, that's fine.
But there's no sense including them in a general-use benchmark, because there's only a tiny handful of cards that can use them, and they're all the same chip anyways.
I'm sure nVidia will be glad to tell you how many RTX Ops(bungholiomarks, whatever) the new cards get. It will remain a meaningless number.
Also, the performance implications of the die space are "lost shaders".
nVidia put this in solely for the compute market and THEN turnd around to try and figure out a gimmick they could sell it to gamers with to obscure the meaningful performance loss.
BenSkywalker - Tuesday, July 2, 2019 - link
Ray tracing is a feature of DirectX 12. Metro exodus is using the DirectX 12 implementation for ray tracing.DXR runs on non RTX cards just fine, simply requires driver support for a DirectX feature.
The ray tracing cores don't move the needle for general compute at all, don't know what helmet head told you that but they have no clue what they are talking about. The tensor cores, otoh, those are very useful for certain compute tasks, they are only used for denoising on the ray tracing side, they aren't the intersection compute units, the feature they bring to the table is DLSS and we can all ignore that forever and that's fine.
The key new feature for the next gen consoles, the big feature every engine developer is pushing for, what had been considered the holy grail of real time graphics for decades, that I don't get why you would ignore in an article with RTX as the subject.
Meteor2 - Saturday, July 6, 2019 - link
If ray-tracing is so amazing... Where's the support?Phynaz - Wednesday, July 3, 2019 - link
Benching lowest common denominator is meaningless. Sorry if AMD can’t keep up.eva02langley - Tuesday, July 2, 2019 - link
Man, what a nice fanboy we got...