08:03 <MrCooper> ivyl: does Proton 10 intentionally not build the Wine wayland driver? (Wine 10 builds it by default, the x11 driver takes precedence at runtime though, the user needs to opt into the wayland driver)

08:36 <ivyl> MrCooper: it's complicated. Steam Runtime SDK we are using lacks the dependencies in required version. We don't even pass a flag or rip out any code. It was conscious decision to not put any effort in enabling it though. See: https://social.treehouse.systems/@ivyl/114432399399208514

08:42 <MrCooper> it'll take longer for it to get ready if people can't try it

08:44 <ivyl> They can try it with upstream Wine or the myriad of Proton downstream that will eventually enable it

08:46 <MrCooper> the fact that there's already multiple downstreams which enable it makes the "it would be hard" claim somewhat dubious

08:47 <ivyl> ...

08:47 <ivyl> a lot of them skip Steam Runtime or use their own runtimes

08:49 <MrCooper> gotcha

08:49 <ivyl> and if it doesn't compile right now (not even tested) they will patch things up

08:53 <YaLTeR[m]> [@orowith2os:fedora.im](https://matrix.to/#/@orowith2os:fedora.im) would be good to get gtk opinion on xdg deco v2 so it doesn't turn out that it's again unwanted there

09:02 <MrCooper> ivyl: using a Proton downstream (let alone Wine upstream) is a significantly higher barrier than setting an environment variable in the Steam launch command line

09:05 <ivyl> That's intended. There's a lot of websites that just provide magic options and people keep pasting them without any reason. We still see folks using things that never existed or were deprecated 3+ years ago. This would just add confusion to bug reports.

09:05 <ivyl> Also downstream can keep winewayland.drv in sync with upstream Wine and take on bug reports and relying those.

09:06 <ivyl> Look, I get people are excited about Wayland. I'm using Wayland since early sway days. I was also the only person to reply to Alexandros that he should pursue winewayland.

09:07 <ivyl> We have spent a lot of time upstreaming Proton's fshack and making the behavior benefit winewayland. A lot of Proton devs are contributing to that area upstream.

09:08 <ivyl> It's currently bumpy enough with just winex11 and the extent of changes we pulled from upstream due to the above to add any extra work by (semi)supporting another driver.

09:08 <MrCooper> it's not about being excited, it's about e.g. Wayland supports HDR now, but looks like it'll be years until that'll be generally available to gamers (without gamescope's magic Wayland side channel)

09:17 <llyyr> what's missing from winewayland actually? I've been using it for non-Steam games for over a year now, and the only pain point is that it doesn't support cross process rendering, so games using CEF for ingame menus or login don't work

09:47 <zamundaaa[m]> llyyr: it doesn't have any controller support right now

14:20 <linkmauve> zamundaaa[m], uh, I’ve been using controllers with winewayland for years at this point.

14:20 <linkmauve> Is it a specific wine API that isn’t supported?

14:21 <linkmauve> I thought controllers were independent from the winsys, at least on Linux with evdev.

14:39 <zamundaaa[m]> linkmauve: sounds like you're using some patchset rather than upstream Wine

14:40 <zamundaaa[m]> I don't know how it's implemented under the hood in Wine, all I can tell you is that controllers definitely don't work

14:42 <zamundaaa[m]> Perhaps it is implemented and Steam input is interfering in my case, as it can't be turned off with the Steam controller

14:44 <linkmauve> zamundaaa[m], I’m using wine releases, and in the game Genshin Impact at least my PS3 controllers work just fine.

15:02 <llyyr> controllers work for me with just winewayland as well, not sure about with proton patches on top

17:38 <wlb> weston Merge request !1749 opened by Marius Vlad (mvlad) tests: Add xdg-client-helper library https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1749 [Testing]