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/)F
Posts
1
Comments
1945
Joined
11 mo. ago

  • Yeah, it took me a while to figure out what the problem was. If you disable the steam overlay in the game's options, the controller should connect directly to the game (via SDL) instead failing to go through Steam Input.

  • Void Linux+Gnu

    Uhh, it's GNU SLASH Linux actually

  • The Gentoo wiki is pretty good too

  • Actual reenactment:

  • print variablename

  • All you need to know is that, whatever you pick, you made the wrong choice and you will be roasted if you ever attempt to explain your decision.

    Unless you use Arch, then you have chosen correctly.

  • I would like it to just work too. That would be amazing. Spending time fixing bluetooth or HDR issues is annoying, 100%. I understand your point.

    Like everything, it's about choosing the trade-off that's best for you.

    The reason that you don't have to fix these problems yourself in Apple/Microsoft products is that they invest millions of dollars in software engineering labor in order to cover every possible contingency and hardware configuration available and they expect a return on that investment. Instead of spending your time fixing bluetooth issues you can pay money to subsidize Microsoft/Apple fixing it. That has been, for quite a while, the best deal available in personal computing.

    Except now they don't just want to sell you a box with software in it that operates your computer. They also want to spy on you, lock down your device, prevent you from repairing your own system and trap you in a walled garden of subscription services and use their monopoly power to prevent any other alternatives from being able to offer better services.

    I don't like this new bargain, I'd rather write a script or read a wiki. The FOSS world is full of people who understand this dilemma and we're all working together to make computers better for everyone. Part of that is helping our fellow users come onboard and deal with the issues that they're facing, that's what I was aiming for (and even if you don't need the information, it may help some reader).

  • Why would you remove the french root, it is the source of all power in the GNU+Linux

  • Some Linux hardcores here might roll their eyes at that complaint, but I’m not afraid to admit that I prefer a GUI.

    Even most of the Linux hardcores use a GUI. Living 24/7 in a terminal environment is mostly a sysadmin/programmer flex.

    The important thing here is that you were able to figure out how to do what you wanted via the terminal, that's a huge first step since most people just give up as soon as they can't use a GUI (props to you). Now that you know the commands to do what you want, you can now do the most common useful Linux thing: make a script

    It sounds like Bluetooth works, but requires a configuration/setting that the GUI developer didn't forsee.

    What you need to do is to break down the individual tasks that you have to do in the command line (like, enable/disable bluetooth, connect to a device, etc) and type them into a text file instead (one command per line), add #!/bin/bash at the top. Save the file and make it executable (chmod +x filename). Then you can execute the script by typing (from the directory where the script is located) ./enablebluetooth.sh or ./connecttoheadphones.sh

    Once you know the scripts work, you can bind them to a hotkey in Plasma Settings under Keyboard Shortcuts -> Add New -> Command or Script -> select your script, and bind it to a hotkey combo. If you wanted to get a bit more advanced, you could probably create some UI buttons that would launch the script when clicked but I don't know how to do that off of the top of my head.

    Once you're comfortable with the workflow of 1. Figure out how to do it in the terminal, 2. Write a script, 3. Make the script convenient to use/automatic then you'll come to appreciate the flexibility of the terminal (because you can put it in a script and never have to use the terminal!)

    If you try and run into any issues just let me know and I'll try to get to you pointed in the right direction.

  • It isn't a controller issue. That still works through SDL.

    Steam Input uses the Steam overlay, it takes your controller input and allows for more custom remapping options, macros, etcetc. I primarily see it being used to let people use a controller to play games that were not designed to play with a controller (by remapping the controller to move the mouse cursor and send keyboard inputs with the controller buttons)

    I use Wayland and my xbox controllers work fine. I'd use Steam Input if I could, but most games are already designed to accept controller input directly so the damage is limited.

  • Absolutely. As long as your display is capable HDR and can output 600+ nits of brightness (1000+ preferred) and has high contrast (like an OLED display).

    It doesn't require any effort, it's a checkbox in the display settings and a command line option in Steam. Assuming you're using GE-Proton10, you just put this in the command line parameters of the game that you want to play as HDR.

     
            PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%
    
    
    
      

    You should pretty much always use the PROTON_ENABLE_WAYLAND flag, the default is for wine to use xwindows and unless you're on a non-mainstream distro then you're using Wayland and so the display out put has to go through a compatibility layer (xwayland). This can introduce weird frame time jitter and hitching in some games that won't occur when using Wayland directly.

    The game has to support HDR and there are some edge cases where the game won't detect that your machine is HDR capable so you can't enable the HDR option.

    You can go through gamescope to have it work, but that is a bit more effort (mostly just installing gamescope and using 'gamescope %command%' (with some switches for options, like resolution, refresh rate, etc). This is a bit more effort and can have some performance overhead, but is still worth it imo.

  • I’ve made peace with the fact that I won’t be able to play certain games. Their loss; there’s plenty of other games to buy with my money.

    Same.

    I have a backlog of games years long, the fact that I can't put Battlefield or Valorant on that list doesn't diminish my ability to play amazing games 24/7 if I wanted.

    Expedtion 33, Blue Prince, Hollow Knight, Silksong, Hades 2, ARC Raiders, Helldivers 2, Path of Exile 2, Deep Rock Galactic, etcetcetc.

    I have over 200 games in my Steam library and every single one works on Linux. I'll worry about the 5 kernel anti-cheat games once I get to the end of my list...

  • Well, then strippers should get better tax breaks than churches

  • His wife must really like dad jokes...

  •  
            Starcraft 1 - 33333333333333333333333333333333333333333333333333333333333333
    
    
      

    (for some reason all 3s worked)

  • OP be like:

  • I do not understand what took these people so fucking long to see what was right in front of them the whole time.

    That would be due to the billions of dollars of money dumped into pro-elite media propaganda over the past few decades on top of the concerted effort to kill public education.

  • Commissioned article

    It ain't much, but it's dis-honest work.

  • Ye Power Trippin' Bastards @lemmy.dbzer0.com

    Dogma and "Transphobia"