Quake3 and Overload (only sortof FPS) are the ones I play. Both have plenty of community servers and also community games. And both have linux native versions that run without wine. I’m by no means an expert in this area nor do I have a vast knowledge of what people play these days. Just sharing what I like.

universal-pidff is working on support for many wheels. I believe they are also working on upstreaming.

Thrustmaster hid-tmff2 is a module that supports some common belt drive wheels. (I had a t300 but upgraded, see below)

OpenFFBoard is fully supported without any extra drivers/modules in Linux. Even the configurator is just python+qt and works fine (This is the wheel I use).

Running the drivers in wine won’t work, or at least there is no benifit that I’ve seen. Oversteer provides some udev rules which improve logitech support, you should install that and reboot even if you don’t plan to use it. The udev rules initialize the wheel correctly, set permissions on the sysfs components, etc. AFAIK the Logitech Driving Force GT is fully supported by the in-tree logitec driver link. Can you post more details about the issues you are having, maybe with screenshots?

EDIT: I forgot that oversteer recommends using new-lg4ff for most logi wheels. So definitely give that a try as others said.

Lastly there’s sim community https://infosec.pub/c/[email protected] (the creator of openffboard is the mod of that community) if you’re interested. It doesn’t see that much action but there’s a little here and there.

Ok, I’m prepared to be downvoted today so here goes.

Nextcloud is an enterprise cloud suite. The one you run in docker on your rpi (or whatever) is the same one that is run at a company, albeit with more high availability and redundancy, but the same application, proxies, caching, db, etc. Nothing is stopping you from running the stable channel and testing your upgrades, or even rolling out specific stable client versions to your devices.

Said companies often have teams (more than one person) to run it, stage upgrades, automated testing, automated backups, monitoring, etc. They go to work and do just that, maybe not every day but at least a couple times a week their focus is Nextcloud and only Nextcloud.

What many people in the self hosting community do is spin up docker, without ever having touched docker before, and try to run Nextcloud, forget that it exists, and then upgrade it a year later across multiple versions without maintaining the database. Then they obsess about how fast an app loads by refreshing it a whole bunch, and then complain on internet forums that it sucks. This, like many posts, doesn’t have a specific problem for us to help with, no logs or stack traces have been posted, and the subject of the complaint shows just how terrible your understanding of application security is.

So, while there is legitimate criticism of some of Nextcloud’s design choices, this isn’t it. And at the risk of sounding a little gatekeepy, if you post “nextcloud updates break everything” with no context you probably should spend some time gaining a better understanding of how internet facing services work and make an attempt to fix the problem (probably misconfiguration, and in this desktop client case probably a heap of un-updated local software installed alongside the client), which I’m sure people would find if they did the bare minimum of reading a few log files or any of the other things that come with being an application admin.