Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PCSX2 Disables Wayland Support

github.com

Post reply on HN
Print view View original

71–80 of 208 posts

Re: PCSX2 Disables Wayland Support

#71

Post by [deleted] »

LtWorf wrote: post #62
k8svet wrote: post #58

Earlier quoted context omitted.

Sure, X11 "better", as long as you don't have high or mixed DPI screens, appreciate variable refresh rates, arbitrary scale factors, don't mind inconsistent tearing, aren't bothered by using a openly unmaintained, abandoned critical piece of desktop infra, etc. Otoh, if you're willing to buy a GPU from a vendor that doesn't snub Linux, or maybe god forbid change screenshot programs (doubt you even need to nowadays),…

I have never seen tearing on Xorg. I know in theory it might happen… but it's a non-issue since it doesn't happen.

[deleted]

Re: PCSX2 Disables Wayland Support

#72

Post by abrouwers »

CuriousCosmic wrote: post #6
iamcreasy wrote: post #2

> KDE isn't too buggy, GNOME is a complete disaster. What did the author mean by this? Don't know much about Wayland other than it is window system, replacing x11. KDE Plasma wiki[1] says, "KDE Plasma 5 is the fifth and current generation of the graphical workspaces environment created by KDE....KDE Plasma 5 uses the X Window System and Wayland." [1] https://en.wikipedia.org/wiki/KDE_Plasma_5

KDE and GNOME roll their own wayland libs for their compositor. These have varying levels of quality with their own unique quirks and bugs. The "gold standard" for wayland at the moment is wlroots which is what basically every other wayland compositor uses. PCSX2 apparently works perfectly fine on wlroots based compositors but has some quirks with KDE wayland and is nigh unusable with GNOME's super janky wayland impl…

Funny, I've used a wlroots environment recently (hyprland), and noticed tearing in animations that I don't have in gnome. So, I guess I'll take "janky" :-)

Re: PCSX2 Disables Wayland Support

#73

Post by keep_reading »

shmerl wrote: post #52

> NVIDIA just crashes in swap chain creation under Wayland I'd say ignore Nvidia, their Wayland support is junk (until nouveau+nvk catches up). It's not a Wayland problem, it's Nvidia problem. For dealing with CSD mess, there is libdecoration that SDL started using. In general - just use SDL for for DE integration, instead of trying to reinvent the wheel. Wayland is not broken. But if you are trying to reinvent the w…

He can't ignore NVIDIA, it's his job to make sure NVIDIA users can run his software by any means necessary.

Re: PCSX2 Disables Wayland Support

#74

Post by hashworks »

LtWorf wrote: post #59
hashworks wrote: post #50

Earlier quoted context omitted.

I guess I'm just hoping for some user that will be bugged enough by problems in Wayland that they decide to fix them. The chance of that increases with user count. I understand that the bulk "forest" of Linux users don't care about their window manager / desktop environment, but it's a higher number than in other operating systems. This approach wouldn't work in Windows or MacOS, in Linux it might.

Why learn about wayland and figure out how to fix things (and then probably have gnome developers never ever accept your fix) when you can just switch to Xorg in 3 seconds?

There are good reasons to switch to Wayland. Features, security Standards and it being in active development are some of them.

Of course no one has to use / switch to anything, but reaching a critical mass of users would be helpful in the long term.

Re: PCSX2 Disables Wayland Support

#75

Post by saghm »

dinosaurdynasty wrote: post #64
evanjrowley wrote: post #53

Due to the headline, it has dawned on me just now that the Steam Deck uses X11. Been using PCSX2 successfully on it for several months now. I never thought about whether it was using Wayland or X11 until reading this.

Steam Deck uses Wayland. It uses Xwayland to run X11 applications.

To be fair, that includes a huge portion of the games available on a Steam Deck right now, given that Wine (and by extension Proton) currently only support running via XWayland. On the other hand, that's argument in favor of Wayland from my perspective; if something I want to run doesn't support Wayland, it doesn't actually stop me from using it.

Re: PCSX2 Disables Wayland Support

#76

Post by k8svet »

Zambyte wrote: post #65
jdlyga wrote: post #7

Are we subjecting ourselves to the sunk cost fallacy with Wayland? It's been "almost ready" for 6 or 7 years at this point.

I think it's more interesting how Wayland has worked fine for me on AMD, Intel, and Nvidia for the last 4 years on my personal machines and work machines, and yet here we are still talking about if it works or not.

If you pay enough attention you'll start to notice the same users names across comments and threads. Hallmarked by ignoring any replies, repeating their pet peeve, repeating experiences from years ago as if they were recent re-tries, and ignoring the laundry list of features possible with Wayland that are impossible or declared as never happening with X11.

I made the mistake, I clicked the thread, and even replied. Meanwhile, I too have been using Wayland for years without issues. I'm on multiple video calls a day for work. I give screen share demos on Discord and Meet. Literally the only issue I've ever had was gamma ramp support, due to Nvidia, and they've even finally fixed that

Idk, see the Pipewire threads for more examples. And/or insert the link to the XKCD comic about the foot pedal. It's all so damn entitled too, from seeming OSS adjacent folks that apparently don't understand the first thing about OSS work. Those same people will never even acknowledge that "Wayland devs" ARE THE DAMN "X11 devs" and they've all declared X11 bankrupt. Buncha people here need to start ramping up on their non-XWayland X11 codebase knowledge if they think they're going to go the MATE route or something.

Re: PCSX2 Disables Wayland Support

#78

Post by gsich »

Laaas wrote: post #20

FWIW all the reasons seem like an aversion to complying with how Wayland works. Yes, you can't position windows absolutely, but that's because you're not supposed to do that. In any case I don't see how being able to position windows is relevant at all to PCXS2's functioning on Wayland? Just don't position windows if you can't? It's an incredibly dumb reason not to support the protocol. Xorg is mostly unmaintained AF…

Users who need this will disagree.

Re: PCSX2 Disables Wayland Support

#79

Post by rowanG077 »

Gigachad wrote: post #44
rowanG077 wrote: post #37

Earlier quoted context omitted.

Xwayland is instantly recognizable as shitty due to fractional scaling. Which almost everyone with a modern laptop uses.

I might not be up to date on this, but does fractional scaling work at all on Linux under any setup? Last I checked GTK just flat out didn't support it or something.

Yes wayland supports fractional scaling without issues. At least I have had no issues.

Re: PCSX2 Disables Wayland Support

#80

Post by notnullorvoid »

Gigachad wrote: post #25
askonomm wrote: post #18

Earlier quoted context omitted.

Ready ready on what? Select hardware? I've thrown 4 regular off the shelf laptops at various DE's using Wayland and they all suck in various ways to the point that they're not even usable. Meanwhile I can throw Windows on all of them, and they work flawlessly. I'm quite tired of Linux guys saying their stuff works just fine, without mentioning how extremely limited is the hardware support to actually run any of those…

It's ready for me in that it works better than X11 on my hardware. No it's not flawless like MacOS and to some extent Windows, but it's certainly an improvement over what we had.

I would hesitate to call MacOS flawless. When I had to use it (m1 pro), it had more issues than Fedora with gnome (which has virtually no issues on the 4 systems I have running it). MacOS wouldn't work with thunderbolt dock, wouldn't work with some monitors / resolutions, requires a paid app to get middle click on touch pad (which is beyond laughable, but goes to show Apple users will pay for anything). The settings GUIs have more legacy than Windows. The updates are terrible... it will uninstall dev tools after an update, and looking at the size of them it's like it downloads and reinstalls the entire OS each time.
Post reply on HN