Quoting: Guestfor example Battlefield 1

Dx12 in Battlefield 1 is complete garbage. It's so bad that even the stuttery mess you get with DXVK in this game is better than the stuttery mess that is Dx12 on Windows.

Not the only game with straight-up terrible Dx12 though.

View this comment - View article - View full comments

Quoting: ArehandoroStar Control doesn't even launch for me :/

According to the guy who reported the rendering bug, you either need to use wine-git (or apply the stub posted here [External Link] to 3.17) because there's a function missing otherwise. Apparently the stub breaks Steam on Wine though.

View this comment - View article - View full comments

Quoting: ziabiceI suspect is a LLVM bug...

It is, LLVM 7 fixes that (and Arch already rolled that out).

View this comment - View article - View full comments

Mesa 18.2 should be fine, yes.

View this comment - View article - View full comments

Quoting: dubigrasuI played the demo today, and it runs very well but characters don't open their mouth when they speak. There's just some weird distortion around it.

Known LLVM bug on AMD. This doesn't happen with the proprietary Vulkan driver, or on Nvidia.

This might as well be the main reason why it is not whitelisted yet, since the game should otherwise run flawlessly.

View this comment - View article - View full comments

Quoting: jensDo you have a feeling about what you can gain with predication, assuming that it is actually possible to somehow translate this DX feature.

No idea, depends on the game. It can potentially avoid some GPU work (CPU is entirely unaffected).

It's a massive PITA to implement though, because it's tightly tied to queries in D3D11, and those really don't map well to Vulkan queries at all.

View this comment - View article - View full comments

Quoting: chancho_zombiewell done they fixed bug 666, must be a really diabolic bug.

Fixing that was actually a shitton of work, so it kind of lives up to its number I guess? On the bright side, it also makes depth-to-color image copies more efficient than they were before, so it wasn't exactly wasted effort.

More important is the other bug though, I thought it was quite rare, but apparently a lot of Lutris users started running into it as of late. FWIW, the fix for that bug was cherry-picked for the Proton build.

And yeah, things might be rather boring nowadays, but it's mostly feature complete and doesn't have a huge amount of optimization potential left.

View this comment - View article - View full comments

Quoting: LinasWith these rates we will have total world domination in no time. ;)

Imagine, in a year we'll be at 16.8%, and in two years we'll have a market share of over 470%!

Or maybe my math is a little off, that's a possibility too.

View this comment - View article - View full comments

If you forgot to remove the appmanifest, Steam probably got confused trying to update a non-existent Proton directory.

That might explain why I had trouble updating the Beta and had to restart Steam several times before it actually worked.

I'd still prefer if there was an option to specify where to install Proton, now I have one install in my home directory and one on my games partition. Slightly annoying.

View this comment - View article - View full comments

Quoting: GuestI think something like stream output support to stream it somewhere else in your house should be on LOW priority myself.

Stream Output is used to generate vertex data on your GPU, and I would assume that your GPU is in the same room as you are.

View this comment - View article - View full comments