I'm undecided on what I think about this since... I frequently get bitten by reproducibility issues of pip packages.

Anything packaged in nixplgs generally rarely fails for me, especially in the more complex cases of cuda/pytorch.

I suppose I'm more likely to want "pytorch except" where that except is a newer dependency or build flag improving performance.

I'm not trying to prematurely optimize but my game worlds are very large, (I have a working to scale earth for example) (oops, forgot to mention, to get good large world behavior, compiling with double precision is a must! (https://godotengine.org/article/emulating-double-precision-g...)) so I've been watching lots of GDC and other talks from AAA titles and how they do their rendering pipelines, and my conclusion is that shaders are really the powerhouse of gamedev these days and anyone interested would do themselves a favor to start learning the quirks of your engines shader language now.

Have you tried CoreCtrl [0]?

> My 5800x3D and 6800XT deliver an outstanding Linux gaming experience.

I have a 7900XTX and performance under Linux has been at least on par with Windows, sometimes better (though not by much).

> May i ask what driver features are you missing?

I'm not GP but I'd love to see frame gen and stuff like anti-lag and upscaling integrated into amdgpu with some sort of official way of setting it (though looking at Adrenaline it might actually be best if it's left up to the community to create the GUIs).

[0] https://gitlab.com/corectrl/corectrl

I'm told it's better in Mesa 23.3 though, haven't tested.

From a quick search this is the best description of it I found: https://github.com/ValveSoftware/steam-runtime

Studios don't care about native GNU/Linux, despite the games being shipped with Android/NDK, PlayStation POSIX environment, and the available APIs on Switch OS.

All of them much easier than porting from Windows/XBox, almost straight ports if coming from Android/NDK.

Game studios aren't FOSS indie devs stressing out about 3D APIs.

They are used to specific hardware since the Atari and Magnavox.

I love Arch, but it is a demanding mistress. If you get behind on updates, you're asking for pain. Also it can be very disruptive to suddenly get a new major version of Gnome that breaks extensions you used, or applications, etc.

What we instead should say is not that Arch is "unstable" because I agree it's not, but rather that Arch requires a lot more care and feeding and if you don't do that, it can lead to instability

I switched to Gentoo and it fixed all the issues I was encountering with Arch, and was more stable. Now I'm on NixOS, which is far more stable than Arch or Gentoo were.

Now, that said, the way SteamOS uses it, I don't see any issues. With an immutable system, A/B updates, and tested images, the compatibility and update issues are solved. Using flatpak for user applications solves the rest of the noted issues. Would be ideal if I could install with Nix instead of Flatpak, but ran into some trouble there.

In various benchmarks Proton is now outperforming Windows. There is no need for it anymore, outside some niche applications.

Nvidia and Wayland are long-troubled friends. The age of the device may or may not contribute...

If you make the command line end with '%command% |& tee /tmp/game.log', you should get some info in '/tmp/game.log'. That may offer some insight

This is true for at least EAC/EasyAntiCheat. This covers a lot, sure, but not everything!

Linux hosts had GPU passthrough working well before commercial software had such options. Nowadays it's just work out-of-box with Virt-Manager that just run QEMU under KVM.

It's been working for years for 99.9% of games excluding some invasive anti-cheats that ban you for VMs, but there literally only a few games that have issue with virtualization.

But if you’re running a standard distro, there are guides for most them.

* Arch guide (excellent resource, applicable to all distros): https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF

* Ubuntu: https://ubuntu.com/server/docs/gpu-virtualization-with-qemu-...

* Gentoo: https://wiki.gentoo.org/wiki/GPU_passthrough_with_libvirt_qe...

You can also find countless blog posts and videos on setting up GPU passthrough.

One excellent resource for gaming use-cases in particular is this subreddit: https://www.reddit.com/r/VFIO/

Last thing to note is that your motherboard can make the process easier if it has good IOMMU support. Basically, you want a MB that puts your PCI slot in a separate IOMMU group. You can find examples by searching for “(MB name) IOMMU groups”.

> For Mirror's Edge, were you using Steam Input?

Yes. The problem lies in the fact that only the Xone driver properly supports the Xbox wireless adapter, but it doesn’t play nice with Mirror’s Edge. Xpad and XpadNeo do work, but those require USB or Bluetooth.

And me having to tweak a million things tells why gaming on Linux still sucks, aside from Deck’s blessed config. I don’t want to deal with a thousand papercuts, I want to boot my system and play. Windows is still closer to that experience than Linux.

You can install it upon Arch from AUR.

Putting that aside:

Windows users always find a reason not to switch to Linux because some missing feature. In two years? There will be another new feature or game on Windows. I remember people insisting on using Windows because it support their „3D-Shutter glasses“ or their card from Nvidia. Either you want use Linux or not :)

Why are many features initially only available on Windows?

First. That is wrong. Important features like cgroups, namespace and containers/Flatpak where novelly developed upon Linux.

Second? MBAs only look at past numbers. So Windows often get traditional Windows stuff first. You make guess it, innovative companies care about what will be possible in future. Valve for example.

The MBA style thinking is also in many consumers. Still buying Nvidia? Because they were faster in the paper sheet? I prefer the cards which works well with Linux, so AMD or Intel. Frames actually generated are more worth than problems with proprietary drivers.

PS: Linux has maybe won the war against drives. Seems like Nvidia open most stuff slowly and feature land in the nouveau-module or mesa. A decade to late. I’m already in Team AMD ;)

Steam Input is rapidly becoming the Google Play Services of the desktop linux world. On Steam Deck for a long time you couldn't even use the touchpads without the Steam client running.

It isn't. If you play with people you don't know, some of them will cheat. If you don't want that, stop playing with strangers.

Automation and assist botting differs from outright cheating in that it still obeys the actual rules of the game.

Things are certainly not always as professional as they appear to be.

Visibility test is definitely feasible against wallhacks, it's not that expensive.

Aimbot is an assist cheat, which technically does not violate the physical rules of the game, so you are right that it's more difficult to detect. One solution to detect this class of cheating is to record the player's movement, and rely on a combination of outlier scores and outlier movement behavior to detect abuse. It's not watertight, but neither are any of these client side anti-cheat detection schemes.

So players of those games are sacrificing privacy for no security at all by the sounds of it.

I am glad that Bungie is going with fog of war for Marathon. And heck, given the features Marathon is getting, maybe someday Destiny can have those nice things too. We'll see...

I mean, hard to call cheating in a multiplayer game the same as cheating in a singleplayer game. The former ruins the experience of others, the latter just affects your own session. Hard to be against cheating in a singleplayer context.

> This is a really sad observation on the state of the Linux desktop. Still.

It seems like a somewhat odd observation, is it really necessary to have another user to do this? I can easily switch between Gnome, i3, and Sway on my system, I mean that’s going between X and Wayland, no issues… maybe KDE and Gnome have some specific incompatibility though? Odd.

Anyway, at least there’s a workaround. If Gnome is a hard requirement, how is Windows even a candidate?

The very same way that you'd do it on the client. If I run an aimbot on an nvidia jetson devkit, using HDMI in to get the screen image and USB emulation to send inputs, your anticheat has to do the same work regardless if it's on the client or the server.

And exactly. You cannot detect that with client-side anti-cheat nonsense either. Record on the HDMI and output a fake USB mouse, why not? Botting doesn't break the physical rules of the game, so you're right that it's hard to detect. One "solution" is to record player movement on the server and detect outliers in behavior and scores. Not perfect (and also very difficult), but just as unreliable as client-side anti cheat nonsense.

[1] Unless we're talking about captcha solving competitions, for now, maybe. :)

- DRM does not serve the consumer, but the producer.

- Anti-cheat only serves the consumer if it is well-designed. However, if someone is able to design a game (technically) well, anti-cheat is unnecessary. And if someone cannot design a game, their anti-cheat is often a disservice to the consumer.

I don't like either DRM or anti-cheat solutions, not because I am not willing to pay the producers, but because I have been burned too many times by dysfunctional solutions.

The best possible, most correct, most defensible, most world-improving advice to give for dealing with a user-hostile product or service, is to have the strength of will to reject it and live without it, and live the example to show that it's possible and you won't die.

Or at the very least, it is AT LEAST as defensible a stance as "The more pragmatic/adult approach is to give the bully whatever they want than to go without their product or service".

That philosophy is not remotely automatically more correct or more adult or nuanced or any of the self-serving words anyone typically uses to try to grant their idea more legitimacy than it deserves.

Calling the principled stance "hostile" is itself hostile.

You can phrase it in a way that sounds emotional and shortsighted and jeuvenile, and certainly there are many juveniles who are guilty of that.

Never the less, rejecting a bad deal is still fundamentally a reaction not an action, a defense not an offense.

The publisher promulgating a user-hostile deal is inarguably the offender, the initial hostile actor.

You can decide that the bad deal is tolerable for yourself, but that is entirely your weakness and does not make that policy smarter or more correct than that of those that decline.

Okay; anti-cheat is user-hostile.

> “Oh you do X, that’s stupid you should not be using the product like that”

Okay, the thing I want is to use a game that I paid for, play it on the machine I own, and run it without giving it any special privileges (certainly not modifying my kernel). I trust that you will support that and not be negative about the way I want to use it?

I suppose you could argue that games could offer an "anti-cheat free" version that can only be used in private matches. But I think you can imagine how many downloads that would get.

On Linux you could automate that task. How would you propose automating "open disk utility and click a few buttons" on Windows?

This is less of a "Linux can't" issue and more of a "I quickly know how to do it on Windows after years of experience and I don't know how to do it on Linux." Linux not being identical to Windows isn't a flaw. No one blames you for not wanting to relearn, but pretending like Linux is bad because your Windows muscle memory doesn't apply is nonsense.

In fact a lot of things are easier. On windows, you need a third party tool to install an iso onto a disk. On Gnome, you open disk manager, right click disk, click restore from image.

A player playing cs go at 1280×720 at 30 ps on a ball mouse will always loose to one on playing at 2560×1440 240fps with a high-quality mouse.

Now there's one more dimension of unfairness. But who cares? You're still going to be winning ~51% of the time, that's why matchmaking systems exist.

The design question is about software that abuses the game state, which is sent to the client, but not displayed to the player (e.g. wall-hacks), and software that sends impossible input (e.g. speed hacks). Anything that manipulates mouse input is very hard to counter.

In the end, all the technical solutions have limits and you need other means to solve the issue (e.g. play with friends/live events). However, anti-cheat software tries to counter many cases that can be solved by better implementations (e.g. servers that send very limited information to the client).

In fact, I'd like to see the same bots developed by cheaters be used for NPCs as well.

Yeah, with anti-cheat.

I think you have never seen destiny 2 PVP maps. They are small. The majority of times, you see the cheater and the cheater sees you. The difference, between cheaters and not-cheaters - you're dead by the time you ADS.