Can't remember any specific documentations, but based on what you commented, first, you need to check if the game requires either DirectX or Direct3D. If it does, you need to check if your computer is compatible with Vulkan (which wasn't a straight forward search, when I dug on that), and if it is, install DXVK (if it isn't, you need to hope that OpenGL won't be too laggy).
Regarding error logs. what I do is read through the log if things start misbehaving, and try to identify any oddities in the log (such as the aforementioned DLL not initializing), and try to fix by myself. And if I don't know how to proceed, I search for the error followed by either "wine" or the game's name on Google, and check places such as WineDB, Reddit (oopsie XD ), ProtonDB's page for the Steam version of a game (if available), Stack Overflow's satellite sites, game forums such as GOG's, Steam's, or even GameFAQS.
And if I can't get the game running properly or at all with Wine or its variants, I seek source ports, wrappers, engine emulators, etc., for that given game. Some may even be playable on Android, so possibly you can get them running on WSA equivalents on Linux, or even Android-x86 or BlissOS through VMs if you're adventurous.
Hey thanks for the response! While I wasn't asking about those games specifically (just giving example of bizarre things I have come across), you did give me some helpful hints on directions to go. I have used engine ports/wrapper on like the doom and quake games but didn't think that there might be others out there. I don't know how common it is to do that. I suppose I can always also ask here or on a Lutris/Proton specific magazine/community as well. Folks here in the fediverse seem helpful.
Oh, right, a few more things: Some times, there may be wrappers, source ports and/or emulators for engines (e.g. JoiPlay and GZDoom) or even overarching groups of games (e.g. for ScummVM). Also, you often find such tools on Github, Gitlab and/or Source Forge. But that makes you need to dig quite a lot, and often having to be mindful of engines used, as well as where and when the game was released.
And as a side note, maybe I should compile a list at some point, although that will be quite an expansive list, so it could take a while.
I'm on Fedora 38 (Workstation edition) and noticed Steam wouldn't let me interact with it when I woke from sleep this morning. It did not crash, though.
I noticed they pushed out a new version today—a UI overhaul. Make sure your client is updated, and maybe it's fixed. I know many problems I've experienced have been due to Wayland's weirdness too.
e.g. use lsusb to identify usb device (e.g. bluetooth receiver) and then edit e.g. /sys/bus/usb/devices/usb7/power/wakeup (replacing "usb7" with the number from lsusb, less any leading zeroes -> e.g. Bus 007 > usb7), changing the word disabled to enabled and saving the file.
If your bluetooth receiver is integrated on mobo or via PCI etc rather than via USB dongle, some adjustments might be needed to get there.
You can try to set antimicrox (emulates keyboard keys on your controller, and that's the name of the package) to use an unused key from your controller as some key that doesn't affect your usage.
Alternatively, you can try to disable all power manager options for turning off the screen. Do mind, however, that at least on Xfce, if you just toggle settings off, the screen will keep turning off, so you need to put all sliders to 0 or the minimum possible before disabling the option.
My wife and I bought A Way Out after having a great experience on It Takes Two. It's been in our steam libraries for four months and this weekend we finally sat down and played it through. Great games from that house, shame they rely on EA launcher.
GNU/Linux Gaming on Kbin
Hot