Quoting: slaapliedjeOn FreeBSD 13, if you install it on a system with an Nvidia card, it still defaults to Wayland, but it just crashes when you try to log into KDE (can't remember if Gnome did it too), you have to switch to Xorg then it works fine. Weirdest thing as I'd think sddm wouldn't work as well, but it works fine..

Didn't knew that BSD had wayland too, I remember that the unfortunately side of Wayland was being linux exclusive, nice to know :smile:

View this comment - View article - View full comments

Quoting: scaineYou say that like everyone else has adopted it,

X.org developers adopted it, that's enough for me

Quoting: scaineand it's the new standard...?

It should already be, Nvidia drivers was the biggest hurdle in this story, but now that they're (somewhat) supporting gbm, things should go faster from now on (including bug fixes / missing features).

Quoting: scaineI'm on Pop 21.04 and there's no Wayland here.

I'm personally not familiar with Pop OS (I thought it was just another Ubuntu fork with a modified gnome and a easy nvidia installer, but I'm probably wrong) but I bet it is because of Nvidia drivers too. If that's the case, it may come once they rebase with Ubuntu 22.04.

Quoting: scaineIt feels like the technology that's permanently "just around the corner". I just wish it had some kind of selling point - something that made me want to try it, other than vague "better architecture" back-end stuff that I'm meant to care about, but don't, on my single-user system. Instead, there's a list of quirks relating to screen sharing, keyboard overlays, proprietary apps and Nvidia or KDE incompatibilities.

That's the unfortunately bad side of anything new in technology, not everything comes in stable packages and sometimes it requires a lot of different variables that can take a lot of time.

The good side is that you're not "forced" to use it right now if you don't want, but I'm happy that those who want to and were limited by it can now try it and maybe help to improve it, in order to make wayland feel like it "earned" the title of X11 replacement.

EDIT: So I've done a little research about Pop OS and they're from the same company that sells notebooks with Nvidia hardware [External Link], so they're in the same boat of Mint developers with their mint boxes [External Link]

View this comment - View article - View full comments

And I would like to welcome the Nvidia users friends to the wayland side of the force :smile:

I hope now the Linux Mint devs can stop pretending that Wayland is not a thing.

View this comment - View article - View full comments

Quoting: MayeulCAt least on wlroots compositor, but probably also on others, you can also use `xeyes`: it shouldn't follow your mouse over non-X windows.

I'm personally not a fan of this "method" (there's a word for that in my native language that I don't know how to express in english :grin:) but it works on both ways for kde.

The main point here is to make sure people are aware if the application is actually running through Wayland, since a lot of people have some xwayland bugs but they think the application is using wayland ootb.

View this comment - View article - View full comments

Quoting: ShmerlLooks like you had a typo.

Fixed, thank you Shmerl

Quoting: HolzkohlenSome browsers meaning almost pretty much all of them, or at least all chromium-based ones (which is a lot).
If you use fractional scaling chromium-based browsers become super blurry. You can set some options via terminal to use ozone to get around that, but then you get other issues. But hey, at least HiDPI support is slightly better on wayland :grin:

Firefox and Eletron-based programs too. The fact devs still didn't prepare the software to detect if a Wayland session is in use for dynamically change this is one of the factors that I think why Wayland session needs to become the default session in the main popular distros (using GNOME/KDE).

View this comment - View article - View full comments

For those people thinking about using the wayland session on kde, you can use the command qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole 
to check which programs are running using wayland and which are using x11 (xwayland)

Since some popular software like browsers still require some tweaks to use native wayland, this command can help you to identify it. Also make sure to change pulseaudio to pipewire for better compatibility.

View this comment - View article - View full comments

I wish paradox still support Magicka 2, that game could use a new sdl lib and some fixes for steam deck.

View this comment - View article - View full comments

Quoting: superboybotThat said, are there technical benefits to porting a game with DXVK Native versus using Proton? From my understanding, there's still overhead from using a translation layer.

Let's try to make an analogy on this case:

Imagine you need to watch a video without subtitles (windows game) where people on it only speaks my native language (windows api calls).

You (linux system) probably won't understand anything (since linux doesn't work with windows calls), but if I (dxvk) watch the video together with you, I can explain what they're saying at the same time (dxvk translating windows calls to linux calls)

Of course you'll understand better if there's a english version of the video (native linux game) or if you know how to speak my language (linux working natively with windows calls).

But since that's is not the case, you can still understand the video content (windows game working on linux) because I'm translating it to you (using proton). Sure I can make some mistakes (bugs) or we can have a little delay because I need to listen to what they're saying, before translate it to you (game stuttering) but it's still better than you not understanding anything at all (not being able to play).

So answering your question: The advantage is that you don't need to have 2 different versions of the same game (windows and linux builds) and dxvk native makes sure will be always be the same translator being used.

View this comment - View article - View full comments

Quoting: SolitaryYou keep calling it mark of shame and your whole argument stands on it.

You're missing the point worrying so much about this nickname (that wasn't me who started btw), but very well...

Quoting: SolitaryValve quite deliberately chose the ratings so it doesn't have negative connotations and just states the obvious truth, they don't even claim it doesn't run, it's just unsupported. Valve also never really says that it's the games fault (maybe with the exception of anticheat), they for the most part take that responsibility on themselves.

In my original point I was stating that users, unaware of steam deck subject, seeing games labeled as unsupported (happy now?) could think that there's something wrong with the game (even if there isn't) and this could cause some kind of backlash from developers claiming that this label could be giving wrong the idea to users about the game.

Quoting: SolitaryI would agree with you if it was "borked" or "broken" (ProtonDB), there you could make the argument much easier.

That's the point, for someone unaware seeing this "unsupported" label they can think that's something else (including broken), specially compared to other games with green / verified label.

Quoting: BielFPsOf course I'm not confirming that any of this will happen, but it is all in the realm of possibility.

View this comment - View article - View full comments

To protect your privacy, external media requires approval to load.

Source: uploads.golmedia.net

View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

I remember you can glitch this part by making the game not load Alyx and get you stuck :grin:

View this comment - View article - View full comments