It’s kernel level anticheat, it can do whatever it wants. It’s on the same level as the operating system.
Realistically? Nobody’s gonna bundle Linux filesystem drivers in malware just in case. If someone is to exploit Vanguard for malware I’d expect a credentials stealer to take your Steam and Discord accounts. Ransomware would likely spread to the NAS but that can be mitigated with readonly permissions where appropriate, and backups/shadow copies.
It should fix most of the flickering and stuttering particularly on NVIDIA Wayland, once every part of it gets merged.
Valve can’t distribute the codecs legally, but the community sort of can. VLC for example can get away with it because France doesn’t recognize software patents and in general has pretty good interoperability laws. So the codecs exist in open-source form that you can compile yourself. I think Proton-GE does bundle them, and if not I’m sure someone did or at least have instructions to compile with the codecs. We’ve dealt with wmv files in games well before Proton even existed, well before Valve even supported Linux at all.
For the shaders, it’s a normal and one-time thing. Once they’ve been compiled once they’re cached, and then afterwards it doesn’t need to recompile them and you don’t get stutters. What Valve does there is they collect the compiled shaders and distribute them to everyone so it’s faster. So it’ll be a stuttery mess for a couple minutes and it’ll progressively get smoother and smoother as new shaders will become rarer and rarer until they’ve all been seen once.
It’s all xwayland. Wayland support in Wine/Proton is barely usable yet. Even Valve’s gamescope, although a Wayland compositor/client, still only exposes xwayland by default.
I would guess both the game and discord are xwayland and since it all happens on that side that happens.
Seems like a similar thing to the xeyes trick to check if an app is really running on native Wayland: if the eyes don’t move, mouse events aren’t going to an xwayland client.
Which is basically the same thing. Gnome uses Mutter, which is a part of the Gnome project as a whole.
Wayland changes things a fair bit compared to Xorg. There’s no standard Wayland server, each DE implements their own to suit their needs. Some libraries have emerged to help with that, it’s relatively easy to get going with wlroots which Sway/Hyprland/Gamescope uses. But Gnome makes their own and so does KDE so it can integrate more deeply with the DE.
There’s non-desktop compositors too, like for VR for example where you can manage your windows in 3D space all around you. That’s where Wayland shines, that gets super complicated to do in Xorg but a breeze with Wayland.
Mine doesn’t show any pie charts, where do you find it? Does it only show if you played on more than one platform?
First step there would be to get some logs. Launch steam from a terminal and output to a file:
steam 2>&1 | tee steam.log
Launch a game and watch the terminal to see what happens.
If you moved games after launching them, clearing their Proton containers can help. I had some games set to extremely old Proton versions that couldn’t launch because the version jump was too big. I’ve also seen vanilla wine prefixes break when moved due to some symlinks.
But those are guesses, the logs will tell you. Sometimes it even actually tells you how to fix it!
The future is now if you have Intel or AMD. Unfortunately NVIDIA users are lagging behind on that one. But that’s fine, that’s how stuff works. Even on Xorg land, when composition was first introduced, it was a mess. Most drivers didn’t support it well, it was buggy. I think NVIDIA was the least bad one at the time. Eventually some DEs started switching on compositing on and people were annoyed because it didn’t work for everyone. It was once one of the most common “help my graphics are weird since I updated”. But those for whom it worked enjoyed their desktop effects and finally catching up graphically with Mac and OSX. And now unless you run XFCE or some other super lightweird DEs, you’re using a compositor.
By all means keep using Xorg if it works better for you. That’s why both are still going to be available for the foreseeable future. No big transition work by switching everyone overnight and everything goes flawlessly. People need to use it for important features that are missing to be found, and solutions to those to be found.
Same. Triple monitor has never been this smooth and not a clusterfuck. I can even (usually) unbind my second GPU (RX Vega 64) and pass it to my Windows and Mac VMs, shut down the VM and rebind the GPU on the host and the monitor pops right back in my desktop and I can play games on it, which gets displayed on my main monitor which is on my primary GPU (RX 570). And it mostly just fucking works.
Like sure okay I can’t disable vsync in my games, but since VRR also just works and my Vega 64 is aging anyway, it’s pretty nuts I can still do all of that. The Linux graphics stack is getting pretty darn impressive.
If you’re using it and it’s not even giving you enough trouble to check, then that’s a really good thing. If you use Gnome, you’re very likely to be using it as it’s been the default for a while on their side. KDE is also enabling it by default with Plasma 6.
It’s really awesome when it works well. It’s only a problem when it doesn’t but these days it’s rarer and rarer as the quirks are being ironed out. We’re even just about to get HDR.
At this point I have fewer problems with Wayland than I did with Xorg. Sure it’s not fully baked for everyone’s use case just yet, but for browsing, working and gaming it’s been great for me. I straight up forget I’m even on Wayland at times. It just works great out of the box!
And Plasma 6 is looking quite promising in that department too!
Meanwhile, me running my whole Steam library off ZFS over NFS 😅
For a CPU benchmark like this, something is definitely weird because wine shouldn’t be translating anything. I wonder if the benchmark might be doing weird things with the Windows API.
That sounds like you’re hitting an edge case and it might not be representative of the actual performance you can expect out of Wine.
Have you tried other benchmarks?
That shouldn’t be a problem, both Gnome and KDE gave decent accessibility features as far as I’m aware. Or at the very least, it’s got zoom, and the cursor can easily be changed to something of your liking. I think KDE’s also got the macOS “shake cursor to make it extra large so you can spot it” available.
I’m more concerned about
That’s not a lot of time, and if you’d rather not spend it tinkering I would stick with Windows.
I would at least make it a dual boot setup, so you can switch between Windows and Linux as needed. Don’t have time to tinker? Just do it in Windows until you have time.