Hmm, seems it's enabled by default?

https://gitlab.winehq.org/wine/wine/-/blob/master/configure#L4420

View this comment - View article - View full comments

Quoting: sobinsirilIf anyone is wondering how to run Wine using the Wayland Driver, prepend the wine command with the Environment Variable DISPLAY='' WAYLAND_DISPLAY='wayland-0' and run it.

Currently notepad.exe works for me :)

EDIT: Just found out that this is not working for me in the wine-staging 8.12 official arch package as it did in the wine-wl-git aur package :(

May be building it is behind some optional config key that's disabled by default?

View this comment - View article - View full comments

Quoting: pleasereadthemanualThanks for that script—that might become my preferred way of installing/updating dxvk outside of Lutris!

Note that the script is only building dxvk and vkd3d-proton (on Debian). You need to install them separately (and adjust the build scrript to your distro as needed).

I think winetrick verb copies dxvk dlls, while I prefer to use symlinks instead as above.

Quoting: pleasereadthemanualI was under the impression that VKD3D-Proton had some fixes/features that were specific to the Steam runtime. But if it's for general use, that's great.

It's OK for general use, it's not tied to Steam runtime.

View this comment - View article - View full comments

Quoting: pleasereadthemanualDo you know if there is a way to use VKD3D-Proton for non-Steam games? I very much doubt I'll have need of more advanced D3D12 features, but it would be good to know.

I simply build dxvk and vkd3d-proton periodically and have them enabled in the prefix (as symlinks). So once that is set, you don't need to update the prefix, just update the built dlls in whatever location you store them which will update them for all prefixes that linked them.

For building, I made this script:

https://gist.github.com/shmerl/3d49bee2ca04c1016f72366dca9438ce

But I think both dxvk and vkd3d proton provide periodic releases where you can get their DLLs if you don't want to build them yourself.

The issue with stock vkd3d is not simply lack of features - it's going to perform worse because it's not using all available Vulkan options.

View this comment - View article - View full comments

Quoting: GroganI've not heard anything more about that... just like you don't hear too much about them superseding dxvk anymore (and their vkd3d doesn't cut the mustard for DX12 gaming)

From what I've heard, their official vkd3d isn't meant as a replacement for vkd3d-proton, because they intend it to be usable on macOS over MoltenVK, so they are avoiding more advanced and recent Vulkan features that won't work there. In contrast vkd3d-proton is using whatever is available in Vulkan for best performance so I expect it to be always better (on Linux). Same goes for dxvk I assume.

winesync on the other hand was intended as a real successor to esync / fsync on Linux, but it seems to be stuck in some limbo.

View this comment - View article - View full comments

In that context, what happened to Wine's official winesync project that was supposed to supersede both esync and fsync? It never got to usable state?

View this comment - View article - View full comments

Quoting: Groganhttps://github.com/Frogging-Family/wine-tkg-git

I think I looked at that and its configuration files. But it looks convoluted and overcomplicated when I'm trying to simply get upstream Wine + fsync. I got close but not quite to just getting only fsync in addition, so I gave up on that.

In contrast, Wine staging patches are maintained as very straightforward patches over upstream Wine, so I'm using esync patchset from there.

View this comment - View article - View full comments

Quoting: GroganBut now everything I have in Lutris works perfectly with Wine 8.11 (TKG with Esync, Fsync) as my system wine including, most importantly, the EA app. Hopefully 8.12 will be equally fine.

Never tried using fsync since I didn't figure out a clean way to apply those patches to upstream Wine.

But I build Wine + esync (from staging patchset). It works well so far.

View this comment - View article - View full comments

Quoting: axredneckIs a question about proprietary/opensource driver still relevant?

Right now - not really. But it will become relevant for Nvidia once nvk and refactored nouveau will become usable. It would be interesting to see how they'll start replacing the blob.

For AMD I'd say it is just irrelevant.

View this comment - View article - View full comments

Thanks for posting it at the beginning of the month!

View this comment - View article - View full comments