QuotePerhaps then, Australia might finally see a proper Steam Deck release?

Not bloody likely

View this comment - View article - View full comments

QuoteSteam Deck does not support BattlEye for GTA Online.

The opposite is true.

View this comment - View article - View full comments

Quoting: Cyba.Cowboythen the developers just aren't putting in as much effort for the Linux version.

(which wouldn't be the first time we've seen this)

Quoting: CatKillerIt's also exactly what you'd say if you couldn't be bothered to do something for a small audience and had necessarily-secret software to use as an excuse.

That's certainly true. I don't know enough about how it works to say whether an as-effective solution is feasible.

View this comment - View article - View full comments

Quoting: Cyba.CowboyYeah, but the thing is, as I understand it, a lot of the anti-cheat systems actually support Linux-based operating systems natively

But is the anticheat as effective as the Windows' counterpart? This has consistently been the reason companies provide for not enabling Linux support. And why both BattlEye and EAC make it optional—it's not as effective.

This article cites Rust developers experiencing more cheating after enabling Linux support.

So if the Linux equivalent is less effective and leads to an outsized impact on players compared to the marginal benefits more Linux players bring, why would you do it? If your choices are to upset the larger amount of players or a smaller amount of players, the majority wins every time.

I don't like it, but that seems to be the way it is.

View this comment - View article - View full comments

Quoting: enigmaxg2Clearly they won't give up easily on the kernel-level anticheat thing, that helps them to keep a grip on Linux gaming to prevent (or try to) it to take off.

I don't think Microsoft much cares one way or the other, but you'll need to pry kernel-level anticheat from the corpses of these corporations.

View this comment - View article - View full comments

Quoting: TheRiddick* Wayland color management protocol.

This another feature that only works on MESA drivers and not NVIDIA?

The protocol isn't even merged yet (which is why I'm surprised it's enabled by default??), but it does need implementations all across the stack. I can't find out whether NVIDIA has implemented anything for it yet.

Implementations in Vulkan might be enough.

View this comment - View article - View full comments

Quoting: nnohonsjnhtsylay

Quoting: pleasereadthemanualFor me, the biggest one has been multiple monitors with different resolutions. Just flat-out doesn't work on X. Works great on KDE Wayland, GNOME Wayland, and COSMIC. That one's been around for a while, though.

The biggest one in this post is the color management protocol support. Which...I'm surprised KDE is enabling??

What do you mean? you can just set different resolution, it works. Do you mean different dpi per monitor? qt supports it and kde does too on x11 (but in kde that per monitor dpi is hidden behind an environment variable for x11).

I don't know, but I just flat out could not get my graphics tablet + my monitor to work on GNOME or KDE with correct resolutions on X11. That's why I was forced to switch to Wayland. Now I have a third monitor, so it's even more impossible.

My primary monitor is 4K. My graphics tablet is 1920x1080. My graphics tablet needs 150% scaling; my primary monitor needs 200% scaling.

Whether it's GNOME or KDE, having different scaling options for different monitors in X11 just doesn't work. It's not possible.

This is because, as far back as the Xinerama days, X does not understand the concept of multiple monitors. The way Xinerama works is by treating all monitors as a single extended monitor. Having multiple display scales for a single monitor doesn't make sense.

But I really really need that feature because otherwise, one of my three monitors will be too small or far too large.

(and in any case, Wayland is a better experience for me aside from this, with the major exception of color accuracy)

View this comment - View article - View full comments

Quoting: Marlockinvesting in building a more complete ecosystem of trustable (necessarily FOSS) apps for which fine-grained permissions aren't necessary

As a proponent of permission prompts in Flatpak for some time now, I want to say this is not primarily about security, but usability.

We have a situation where developers distributing their software through Flatpak (e.g. Bottles) will choose tight security defaults that are actually broken for users, and they need to unbreak them with Flatseal or symlinks to get it to work. If Bottles would just prompt you when you wanted to access a new folder and dynamically alter the permissions, that would be far more usable!

I would really like to be prompted when a program wants to alter its manifest to get access to new permissions rather than needing to alter the permissions manually in Flatseal.

View this comment - View article - View full comments

Flatpak really needs this! It's good to see Canonical innovating with permission prompts, something sorely missing from Flatpaks.

View this comment - View article - View full comments

Quoting: Purple Library Guyactual user-facing software like DEs was starting to implement Wayland features that are new features they couldn't have under X.

For me, the biggest one has been multiple monitors with different resolutions. Just flat-out doesn't work on X. Works great on KDE Wayland, GNOME Wayland, and COSMIC. That one's been around for a while, though.

The biggest one in this post is the color management protocol support. Which...I'm surprised KDE is enabling??

View this comment - View article - View full comments