While proton enables that, that’s still just vulkan outperforming DirectX.
So technically proton isn’t improving performance here, it’s just allowing the game to run on better performing systems (like Linux and vulkan).
While proton enables that, that’s still just vulkan outperforming DirectX.
So technically proton isn’t improving performance here, it’s just allowing the game to run on better performing systems (like Linux and vulkan).
Cethin@lemmy.zip 2 months ago
It’s just Vulkan outperforming DirectX by translating DirectX to Vulcan. If you’re comparing the default experience with Windows and Linux, how can you say Proton isn’t technically improving performance? What would you call that if a performance increase is caused by running through Proton?
Aceticon@lemmy.dbzer0.com 2 months ago
As pointed out higher up this thread DXVK and Vulkan also work in Windows (without Proton) were they give performance improvements.
Further, it’s perfectly possibly to run Windows games via DXVK and Vulkan in Linux without Proton - just use plain Wine (of which Proton is a branch) instead - and you also get the performance improvements (certainly that’s my perception in my system since I tend to get my games from GoG instead of Steam when available and thus run them via Wine instead of Proton).
So that’s at least two situations were the performance improvements are present without Proton, hence you cannot logically claim they’re due to Proton, even indirectly.
Logically the place most likely to yield performance improvements is the full implemention of a rendering stack directly on top of the hardward which even has its own architecture - Vulkan - since there’s a lot more room to improve usage of hardware resources at that level, though things like pre-conversion and caching of Vulkan shaders from DirectX shaders, which are done at a higher level (Proton or DXVK), can also improve performance.
It’s possible that Proton itself is delivering some performance improvements (for example, via the trick of, pre-converting shaders from DirectX to Vulkan before game start, uploading the generated shaders to the Steam servers and then other users just download the converted shaders and do not require that step, which should speed up game start tough I have at least one game were it actually can slow down A LOT game start because the generated shaders are massive) versus solutions using DXKV + Vulkan without Proton, but that’s not really enough to sustain a claim that the performance improvements are mainly thanks to Proton in the face of also seing the performance improvements when Proton isn’t there.
Cethin@lemmy.zip 2 months ago
Except these tests were almost certainly being run on SteamOS using WINE with Proton. We can’t know what the numbers would be with any other setup without doing it. Would a Protonless DXVK for WINE run just as well? We can’t know from these figure.
Also, Proton does not require running through WINE. I play Epic, GoG, and otherwise sources games with Proton not through Steam all the time. It’s also more than just DXVK. That’s a big part of it though.
No one is arguing that DXVK isn’t important or anything like that. They’re just saying Proton is a piece of this, which includes DXVK. I don’t know why you’re arguing.