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/)MR
Posts
3
Comments
86
Joined
2 yr. ago

  • 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/diysimulators@discuss.tchncs.de (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.

  • In addition to everything everyone else has said, the launch option: PROTON_LOG=1 %command% (from the wiki). It will create a steam-<gameid>.log in your homedir which can have lots of good wine/proton specific information in it.

    You can also rename the user-settings.sample.py file in a given proton version in $HOME/.steam/root/steamapps/common/Proton - <version>/ to user-settings.py and uncomment the additional wine debugging options (PROTON_LOG is already set in this file, but it is not active until it's renamed or passed directly on the Launch Options line).

  • Someone posted this https://webvm.io/alpine.html in another community and it made me think of this post. I've never used webvm and I suspect there are many downsides but seemed relevant and the demo seems to be able to run a full desktop environment. You have to find a CAD software that supports Linux though which is a controversial topic at best.

  • The really hilarious thing to me is that the NextPush app (unified push provider that can be run on your nextcloud server) is unsupported by nextcloud talk. But it is supported by a bunch of other competing applications.

  • works for me both on my archlinux machine and my steamdeck with steam and non-steam games. I've even played NFSU2 with it =] . I don't think it required any more configuration than just pairing for me, no special drivers or tools. Maybe it needs a firmware update (I don't know if that's a thing, just a thought)?

  • the qobuz webapp is hi-res too, I just use it in Firefox and my dac reports the same bit/sample rate that qobuz does. AFAIK there's no compression there though I haven't extensively verified that, only that the end result is 24bit/192kHz if that's what qobuz says is playing.

    EDIT: Also, qobuz is nice because there's very few things you can click on in the web interface which cause the music to stop playing. I really appreciate that feature.... looking at you bandcamp....

  • Ah, I should have been more clear. The CRITERIA section of the sway documentation states that class matches support regex, so instead of using a * as you did in your example you'd use a regex any .*. So I think (untested of course) that for_window [class="steam_app_.*"] allow_tearing yes should work.

    The comment in the code for allow_tearing notes that it must be enabled on the output as well. Here is the relevant output documentation. There are several other notes/recommendations there as well you should probably pay attention to.

  • Are your games all wine/proton games? For me in sway they all have the same class followed by some uid thing:

     
        
    ] > swaymsg -t get_tree
    [...]
      #92: output "DP-5"
        #70: workspace "21"
          #126: con "Automobilista 2" (xwayland, pid: 171976, instance: "steam_app_1066890", class: "steam_app_1066890", X11 window: 0x5400001)
    
      

    Or gamescope:

     
        
    ] > swaymsg -t get_tree
    [...]
      #92: output "DP-5"
        #70: workspace "21"
          #124: con "Assetto Corsa" (xdg_shell, pid: 170694, app_id: "gamescope")
    
      

    EDIT: Also allow_tearing was added to master 3 weeks ago, so this is definitely not in the current release. FYI to anyone who might try it.

  • I use a little oneliner with tofi (rofi/wofi would also work) to select the current output and avoid pavucontrol. It's mapped to a sway binding but would probably work in any wm/de:

     
        
    pactl set-default-sink $(pactl list short sinks |awk '{print $2}' |tofi $tofi_args)
    
    
      

    I'm using pipewire so the functionality of pactl is actually provided through pipewire-pulse I think

  • Gatgetbridge (your link) has a breakdown of devices they support https://gadgetbridge.org/gadgets/ . You can click through the vendors to find devices which are both "highly supported" and "no vendor-pair". Meaning most/all the features work without any reliance on the vendor app.

    As for the similarity you are asking about with pixel->GrapheneOS, there are very few watches that can run an alternative open source firmware or operating systems apart from the ones that are already open source, like bangle.js, pinetime, etc. Wearables are even more specialized than phones, they require specialized code designed specifically for them and would likely require pretty extreme effort to reverse-engineer.

    I use a pebble 2 HR with gadgetbridge but the watch it self runs the old pebble firmware which gadgetbridge talks to. This is fine for me, but if you are looking for a more modern watch you may have to make some compromises.

  • Interesting, it is working for me in wayland and the drop down menus are fine but I'm using sway which is a totally different wayland implementation than what KDE is doing. I'm glad you found a workaround.

  • Mechanical Keyboards @lemmy.ml

    looking for a US source for Gateron switches

    Mechanical Keyboards @lemmy.ml

    Seeking some input on long term experience with Krytox 205g0 or Tribosys 3204

    Linux @lemmy.ml

    xeyes 1.3.0 released yesterday now has "multi-ocular support"