Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)PO
Posts
8
Comments
292
Joined
1 yr. ago

  • I grew up with a Wii, and never held an n64 controller, so I always will wonder: How do you hold those? Do you hold it like a regular controller and then reach your thumb out to the joystick in the middle, or do you hold the middle grip and then one of the other outer ones, and have to reach as well? Is it subjective?

  • The trigger on the xbox one controller is loose and easy to take off, and it has a spring on it that flew off and I lost upon disassembling it. The 360's controllers will remain completely function even without any shell, but are also able to be disassembled.

  • If they have good scores on protondb, it's probably an issue with configuration. First, make sure you're running it with proton. Go to the game's configuration > compatibility and tick "force the use of a specific steam play compatibility tool." then select the highest version of proton available(don't choose experimental if your game is supported according to protondb). Then, click play. if needed, proton will install and this should solve your issue. If it doesn't, then you can delete steam(sudo pacman -R steam), and remove the .steam folder in your home folder. This deletes your configuration for steam, and might help resolve issues. Then, re-install steam(sudo pacman -S steam), and sign in again. Download your game and set up proton as I told you. If that still doesn't work, you'll want to make a post and share the log files.

  • I don't think your GPU is the issue here as well, I think your game might not work. If you want to try and diagnose the issue, I'd be happy to help. First, add the following to your Steam game options: PROTON_LOG=1 %command%. Then, run the game. This will make a log file in your home directory, with the prefix "steam-" and then your appid. If you want to upload the log or paste the output here, I can try and look at it and try to help.

  • I can't say for sure, but I'd assume that windows works differently that GNU/Linux at least slightly like this. In GNU, there is a hierarchy of displaying things and windows likely has a slightly different version of that.

  • First off, I'd recommend you use the nvidia-dkms package, because that can make upgrading kernels easier. Second, let me explain the hierarchy of GUIs on Linux. At the base level, you have the display server. In your case, you are using the X11 display server. The display server is at a very low level, and only handles the rendering of content. The three prominent display servers are X11 and Wayland. The second tier is the window manager. It's pretty much essential, and it lets you move around windows, stack them, etc. You're using i3. The third tier is desktop environment. The desktop environment is completely optional, and it controls things like taskbars, start menus, and system trays. DEs are not needed for computer use, but they can make things like customization easier.

    In your case, I don't believe your issue is with your window manager or display server, I believe it is with Steam or Proton. What game are you trying to play? Some games aren't able to be compatible with Proton, unfortunately.

    Edit: A few corrections that I just thought of. First off, the display server doesn't "just" handle rendering things. It handles input, and communicates to Linux, which will tell the hardware what to render. Second, I didn't explicitly mention this, but I thought that I should, a desktop environment still relies on a window manager for handling windows, it just adds functionality. Also note I wrote this reply partially in response to another commend, so sorry if I yapped a bit too much.