Glo.
Diamond Member
- Apr 25, 2015
- 5,765
- 4,670
- 136
Here is what Sebbbi thinks about Vega GPU.DSBR isn't a API call, that happens automatically in Vega, it is made to reduce the amount of work Vega must do.
In other words, game sends geometry to DX/Vulkan/openGL API. Drivers take that data, do whatever tweaking on it, and send it on to the hardware.
DSBR works on a pixel level, and it may have zero (0) impact on the workload, depending on if the game's workload has already culled the geometry down to the pixel level. Hint, most modern AAA game engines already do this.
That means, that if the game/app already is doing pixel level culling, then DSBR won't have any work to do, and you won't see any savings (which is why some of those benchmarks we have seen, this feature has zero impact on them).
That also means, that in really old games where the culling wasn't down to the pixel level, DSBR should show some nice gains, but again, this is workload specific (some engines are better than others).
*Edit, is there any AT'er that got a Vega FE? If so, and they have a Unreal 4 based game, they could turn off occlusion via TOGGLEOCCLUSION console command, and DSBR should keep the framerates the same as before, well, in theory. I don't got a Unreal 4 based game to see what that actually does.
Which patches do you speak of? I did a quick glance, and didn't see anything relevant.
https://forum.beyond3d.com/posts/1992079/
"It behaves just like any other GCN GPU".
In theory you are correct that this is automatic. The problem is: Are drivers enabling the new features? Is it all working properly as it should or we have to wait 6 months after Vega RX release to get best out of it?
No they do not have to be final clock speeds. The same way have seen 3.6/4.0 GHz on Ryzen 7 Eng samples few months before release, not be final clock speeds. Or was it?Engineering samples of Ryzen were clocked lower than final chips, so why would these very early leaks of Raven Ridge be a the final clock speeds? Which specific Bristol Ridge part was it compared with?
Assumptions like this, leaping to conclusions, is how Vega got overhyped.
Yes it has. But its applications job to decide what to do with them.Doesn't DX12 still need to know what's there through drivers?
That is why Raja have said that with Low-Level APIs they cannot do very much for control of performance.