Wine 8.12 brings more Wayland work and performance improvements

​With this wine version in my case steam..................



Back to work

Also can use depth bias control too



However in my case needs wait for staging 8.12 for see fix launching programs case appetizer

​


Last edited by mrdeathjr on 8 July 2023 at 3:07 pm UTC

I've only just gotten back on track with Wine 8.11. Since 8.7, I hadn't been able to use it. I use wine-tkg patchsets to get Fsync support and I figured that's what was breaking it (patches, compiles but fails to run any games). I kept going back to Wine 8.6.1 (and recompiled it to test my toolchains and ever changing system environment and it was all good).

When Wine 8.10 couldn't even run "wine notepad.exe" (not even winecfg would run to get that off the ground) with a bunch of dll errors an being unable to start the explorer shell, I tried a plain build of 8.10 and it was still broken.

I saw mrdeathjr post a similar error for Wine 8.10 and that's when I knew for sure it wasn't just me and my toolchains etc.

But 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.

P.S. For continuity, yes, Wine 8.12 TKG is good for me, same as 8.11. I've been using it for my system wine for a few days now and all my stuff in Lutris works the same.


Last edited by Grogan on 12 July 2023 at 12:37 am UTC

Update

In my case also fix keyboard input on atelier sophie non dx version aka DX9





In before wine versions only work space and 0 but dont keyboard arrows and for before dont be possible played with keyboard

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.

Quoting: ShmerlNever 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.

Unless it's just been rebased, I don't think it ever would. There's a lot of MacGyvering that goes on with TKG, like reverts so the patches will apply, for example.

I use the "frogging family" build system, especially for my Proton builds. I like it because it's native builds with my toolchains, not containerized tomfoolery with valve's environment.

https://github.com/Frogging-Family/wine-tkg-git

Kron4ek usually has a current wine staging already done up, ready to build (using that same build generator). Well, in a day or so it will be 8.12 probably.
https://github.com/Kron4ek/wine-tkg


Last edited by Grogan on 9 July 2023 at 6:30 am UTC

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.


Last edited by Shmerl on 9 July 2023 at 6:40 am UTC

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?


Last edited by Shmerl on 9 July 2023 at 6:42 am UTC

I'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)

The TKG patches are very complicated, and I get in over my head when things are broken.

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.


Last edited by Shmerl on 9 July 2023 at 7:21 am UTC

Quoting: Shmerl

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.

Do 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.

On the other hand, I've never understood what the point of disabling VKD3D in Lutris's options is...it ships with WINE, and it's the only compatibility layer WINE has for D3D12. I guess it might make more sense with their own runtime?