The game already supports Vulkan on Windows and runs fine there [External Link]. What are they having issues with?

View this comment - View article - View full comments

Quoting: NeverthelessSo even single threaded Vulkan is much more efficient than OpenGL. I guess DX11 performance might come single threaded Vulkan close.

Vulkan draw calls and friends are, for the most part, dirt cheap. There's very little (but still some) state tracking going on in the driver, and you as an engine developer can build thin abstractions that fit your needs, again with minimal state tracking, rather than using an overly generic abstraction that ends up doing way more than you actually need, and doesn't necessarily do it well, both in terms of CPU and GPU performance.

Unfortunately, the latter still seems to be a common pitfall, and we end up with games that run significantly worse on D3D12 than they do with D3D11, even when CPU limited. Latest prominent example of that being Resident Evil 2, which runs faster with D3D11->Vulkan translation than it does with their native D3D12 renderer on Windows. And that just shouldn't happen.

View this comment - View article - View full comments

Quoting: mylkabesides, hardware is better now and i think you can play TR with a mid range PC on ultra

My Ryzen 2700X might not be the best gaming CPU, but it's no slouch either and drops all the way to 20-25 FPS in more intensive areas like Shantytown or the village thing with the plane wreck. That might be somewhat playable, but not really enjoyable.

Proton never drops below 60 once the shaders are compiled. Sadly, compiling shaders is a bit of a problem here.

This game already has questionable performance on Windows, all things considered (like all the TR games on Dx11 really), the Feral port being so slow really doesn't help.

View this comment - View article - View full comments

The Steam version of Crysis 1 has been broken for me even on Windows for a while, not sure what it is they are shipping. Runs fine with 64-bit executables.

View this comment - View article - View full comments

Then again, not getting anywhere near 60 FPS on your kind of hardware isn't exactly excusable either.

Let's hope that VP gets to port a decent game for a change, soon, and do a better job than they apparently did with MXGP3 and this.

View this comment - View article - View full comments

FWIW since Liam is unable to run Rise of the Tomb Raider for reasons that are beyond me, I did a quick video [External Link] on Proton vs Native in that game. Things have improved a bit since Xpander made one back in April, but we're still miles behind, and considering how much better the native port runs than even native D3D11 on Windows (at least on my hardware), it's likely to stay that way.

Edit: And thanks for the tag.

View this comment - View article - View full comments

Quoting: KimyrielleIf I remember right, Valve already hired the person behind DXVK, so it's not that they aren't getting compensated for their work.

Literally me. That's why I mentioned it ;)

OpenGL is still fine for low graphics titles but for intensive games Vulkan is a must.

That's something you might want to tell VP.

Then again, if they are stuck porting terrible games with terrible sales expectations I can't really blame them either.

View this comment - View article - View full comments

Quoting: tuxintuxedoOn the other hand, people who work on Wine and components (or simply Proton) will never see that money while doing the work itself.

Well, it does give Valve more money to throw at the parties involved in Proton development.

View this comment - View article - View full comments

Quoting: morgancoxukCan you test rise of the Tomb raider as that uses Vulkan on native Linux and gets similar performance to Windows ?

The Feral port will blow Proton out of the water, and like TR2013, Proton will have massive amounts of stutter at first.

All of the Tomb Raider games have a **lot** of different shaders, which is something that DXVK just doesn't like at all and can make games completely unplayable, even if the frame rate is fine.

View this comment - View article - View full comments

Quoting: x_wingWeird that this problem doesn't affects Mesa if there is an error in the API usage by Unity.

Mesa does not implement glInvalidateFramebuffer (except the error handling bits). That's okay since this function doesn't *need* to have any observable side effects.

The other way around isn't exactly uncommon either (stupid shit running fine on Nvidia but not Mesa, like Divinity Original Sin). People are going to blame drivers either way though.

View this comment - View article - View full comments