Confused on Steam Play and Proton? Be sure to check out our guide.
Latest Comments by Shmerl
Linux gaming performance display MangoHud v0.7.1 is out now
8 February 2024 at 10:19 pm UTC

Nice for them to add present_mode after I proposed that :) But it appears to be buggy and needs more investigation.

Linux gaming performance display MangoHud v0.7.1 is out now
8 February 2024 at 10:17 pm UTC

Quoting: M@GOidLast time I used this it wasn't playing nice with Vulkan and Wayland. How is it behaving now?

Works fine, but I think it doesn't anticipate Wine running in Wayland mode yet judging by some X11 related errors it shows in that case. But it still works.

OBS Studio 30.1 Beta 1 adds Video Capture Device (PipeWire) source, plus more AV1 support
4 February 2024 at 1:34 am UTC

AV1 VAAPI support in OBS is a long awaited addition.

What to Expect From Wine on Wayland in 2024
31 January 2024 at 9:01 pm UTC Likes: 2

I tried it, but it has an annoying bug - you sometimes get half refresh rate on the monitor while game has double the framerate.

It's some subtle bug between Wine, KWin, radv (Mesa) and amdgpu (kernel). I'll revisit it once KDE Plasma 6.0 comes out, since it has a major KWin overhaul and it might be a waste of time chasing that bug before that.

Eidos-Montréal cut nearly 100 staff with new Deus Ex reportedly cancelled
31 January 2024 at 8:54 pm UTC Likes: 2

Quoting: TheRiddickAND the IP goes back into The Vault for another 20years.

Someone should break into the vault 😄

Sort of ironic that a game about dealing with anti-utopian corpo politics is suffering from bad corpo decisions.

Eidos-Montréal cut nearly 100 staff with new Deus Ex reportedly cancelled
29 January 2024 at 8:28 pm UTC Likes: 7

I like Deus Ex: Mankind Divided. And it did feel unfinished, so it would be a waste if they'll never make a sequel now.

Wine 9.1 released starting off another year of development
28 January 2024 at 2:02 am UTC Likes: 5

Quoting: LinasWayland when?

Getting close. It's already somewhat usable, but some issues need investigating.

Proposed Windows NT sync driver brings big Wine / Proton performance improvements
24 January 2024 at 7:20 pm UTC Likes: 2

Quoting: satorideponI watched the presentation and didn't really understood the point of it. Apparently, the only reason this gets picked over fsync is because a few methods that are not commonly used by Windows applications, especially the modern ones, cannot be emulated with fsync/esync. But if they're not commonly used, why not just leave them working through this old RPC mechanism?

Yes, that's right. It's more of a formality, but I suppose it's driven by Wine having such formal requirement - to correctly replicate Windows behavior in upstreamed code. And it was the reason neither esync nor fsync were accepted in Wine proper.

I wasn't clear why mixing things wasn't doable either, but I suppose it had some issue.

Proposed Windows NT sync driver brings big Wine / Proton performance improvements
24 January 2024 at 4:58 pm UTC Likes: 1

Quoting: sonic2kkTo this point, most custom kernels (i.e. Tkg, Zen) already have fsync too! It is disabled for some games when Proton auto-detects them though, for example Yakuza 0 does not use fsync (uses option `nofsync`), but NieR:Automata does (you can check if a game is using esync/fsync and what options it has by inspecting the Proton log, enabled in launch options with PROTON_LOG=1).

You don't really need fsync anyway, since esync does mostly the same thing without the need for extra kernel interface. But still good to have a more formally correct approach that Wine can finally accept upstream.

Proposed Windows NT sync driver brings big Wine / Proton performance improvements
24 January 2024 at 4:34 pm UTC Likes: 4

Quoting: ToddLI can't wait to see these changes get added to the Linux kernel and SteamOS because if these numbers are any indication, it sounds like we're in for some awesome gaming experiences on the Steam Deck

Steam Deck is already using fsync with corresponding kernel API, so it already benefits from better than wineserver approach. I.e. this ntsync isn't going to improve performance over esync or fsync if I understood correctly. It will just make it more formally correct for edge cases.