It is, I tested it on Windows as well (even with dxvk) and it works fine there.

View this comment - View article - View full comments

Can anyone send Epic an AMD GPU so that they test their fucking Unreal Engine on one? Jesus Christ, I'm so sick of this engine. Not only their Windows D3D11 part is annoying, no, this little Linux demo doesn't even work. Not on RADV (massive flickering everywhere), not on AMDVLK (flickering shadows), not on RadeonSI (crash).

And running it with validation layers enabled indicates that there are quite a few bugs in the Vulkan render path. Including invalid shaders, invalid image layout transitions, out-of-bounds image copies, all the fun stuff that leads to undefined behaviour. How does this even work on Nvidia?

View this comment - View article - View full comments

Quoting: jensBack on topic: "Better pipeline creation performance when there is a cache hit" sounds indeed interesting, I would be curious to know how much performance win it yields in real life scenarios.

The way they describe it, it's going to yield exactly 0% in scenarios where performance would actually matter.

Still a nice-to-have improvement since it might slightly reduce loading times in case you already have a populated shader cache for a given game, but that's basically it.

View this comment - View article - View full comments

Sadly the performance / stability of the Linux version isn't as good as the Windows one.

Heh? On my Ryzen system it actually runs faster on Linux than on Windows, apparently due to CPU scheduling issues. Stability has been fine for me as well as long as pulseaudio doesn't act up.

View this comment - View article - View full comments

Quoting: deathxxxDARK SOULS™ III, does not work for me.

Make sure you're using the correct graphics drivers as described here [External Link]. No, the Nvidia driver that ships with Ubuntu 18.04 or 18.10 is not good enough for Proton, it's too old.

View this comment - View article - View full comments

46231 Button tests for ideal size fail on Arabic locale on Windows

Bugs like this one are so weird. I'm surprised that anyone even found it, but these little things probably make wine development very annoying.

View this comment - View article - View full comments

[quote=Pikolo]

Quoting: GuestI was under the impression that MacOS isn't supported in SteamPlay. Has that changed, or was Mac support something they intended to work on after DXVK worked well on Linux?

Nothing has changed so far, in fact they have been removing Mac references from the Proton documentation that were once there.

I also don't see the point.
- Apple deprecated OpenGL, which to this date is the only API for which working D3D7-9 implementations exist, and their implementation is too old to support D3D11.
- Apple does not support Vulkan, none of the VK->Metal translation layers are able to run DXVK yet, and even if they did, performance would probably be terrible in most cases.
- Apple dropped support for 32-bit toolchains, and seem to be making it harder to run 32-bit stuff in general. Really bad news for Windows games because pretty much everything released before 2015 is 32-bit only, and even some modern games are 32-bit.

View this comment - View article - View full comments

Quoting: ShmerlI'm surprised they didn't mention Linux explicitly. With Tim Sweeney constantly complaining about MS lock-in, you would have expected him to put Linux front and center in the store announcement.

Except there's this tweet [External Link] which is basically a big fat "Nope".

View this comment - View article - View full comments

Damn, I didn't even know this was still being developed. I already played this like 15 years ago on some Suse machine that my dad had lying around at the time.

View this comment - View article - View full comments

It's not really a proper fix, it just takes the (incorrect) assumption that D3D11 command lists will only ever be used once one step further, which by the way also slightly improves performance in other games. This works because the vast majority of games do only use their command lists once.

Still, 2GB of VRAM won't cut it for Dark Souls 3, the game needs 4GB at the very least.

View this comment - View article - View full comments