mranderson17

Not sure why all the downvotes, I use the note to self function for exactly this type of thing all the time. Though to be fair signal is both on my phone and on my computer basically all the time because I use it to talk to everyone too...

EDIT: oh, it's downvoted because this is the selfhosted community....

Thanks! I've seen your posts about your DIY cockpit panel. Looks awesome! What is your HOTAS setup like?

Here's what I did for sway, though I agree it took me a while to arrive at this solution:

In the file .config/sway/config:

input "type:keyboard" {
  # Use the following to remap single keys.
  # Weird letter codes are in /usr/share/X11/xkb/keycodes/evdev
  # Keysym names are in /usr/include/X11/keysymdef.h
  # xkb moded layout is in .xkb/symbols/qwerty_prtsc_to_menu in this repo
  #
  xkb_layout "qwerty_prtsc_to_menu"
  xkb_options caps:super
  repeat_delay 220
  repeat_rate 70
}

in the file .xkb/symbols/qwerty_prtsc_to_menu:

default partial alphanumeric_keys
xkb_symbols "basic" {
  include "us"
  replace key "replacewithlessthansymbol"PRSC"replacewithgreaterthansymbol" { [ Menu ] };
};

I'm pretty sure you can do xkb_layout with input device matching in hyprland though I stopped using hyprland a while back.

Some things like caps:super already exist in xkb_options, but less common ones require manually creating a layout. I found an xkb doc describing all these when I was working on this but I can't find it now. If I manage to locate it I'll update this comment.

EDIT: For the qwerty_prtsc_to_menu file above it's suppose to be the actual less than and greater than symbols however lemmy's code formatting is removing them when I save the comment, sorry about that

EDIT2: I didn't realize that you wanted a momentary layer, so this solution will not work for you exactly. However I believe this is possible with keymap switching like described here https://wiki.archlinux.org/title/sway#Keymap in addition to what I have suggested above.

lol, yeah I'll be honest, binding controls in Elite Dangerous is an activity that seems to never end. I played for a while just now and pretty much the whole session was changing my mind over and over about what should be bound where.

Interesting info on your experience with VR. I get queezy when racing in some sims even with the curved 37in monitor and I have astigmatism and wear glasses so I'm not sure VR would be for me, but I haven't tried it so I can't be sure.

Haha, I'm going to have to try this! The original quake might work better since you only have to look left and right, not up and down.

Nice! That warthog stick looks like it has much better build quality than the VKB stuff. Sounds like a really nice setup. I sometimes play Overload with a friend who has a TM T.Flight HOTAS and I believe he does pretty much the same thing you do for control assignments. I lose a lot when we play.... And by a lot I mean basically every time, he's very good.

heh, sometimes I try to convince my friends that use controllers to do 1:1 rally-x races in DR20, it's not pretty. That game is near impossible on a controller even with all the assists on.

Thanks! Between the two sticks I have there are 6 centered analog axes without removing your hands from the grips, 2 more on the analog hats operated with your thumb, and 2 uncentered axis on bases. I'm not sure about Elite Dangerous because I haven't played it that much (really only made it through the training thing and tested input devices) but in Overload I have more analog inputs than things I can assign them to and that's a 6DOF game.

I should try Elite Dangerous again sometime and really pay attention to what you need assigned to analogs. I really just want to fly around and shoot things, not really play a procedural game, so I didn't pursue it that much. Overload is like Quake3 with space ships =]. Sit down, start game, shoot everything that moves.

Thanks for the update!

After I sent this I did get it working pretty consistently however there's a DXVK bug in the version of DXVK supplied with proton 6.3-8 and older. Using a newer proton (or wine) results in broken FFB.

So at this moment there seems to be no way to have trees and FFB at the same time, but otherwise it works well. I did try creating my own FFB fixes based on those published by RSF but that's a fix for RSF it self, not related to wine, so it obviously didn't work:

] > cat t300rs.reg
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_044F&PID_B66E]
"OEMData"=hex:43,00,88,01,fe,00,00,00
"OEMName"="Thrustmaster T300RS Racing wheel"

Things seem to work best with the proton-6.1-GE-2 launcher, dxvk and VKD3D disabled in the bottles settings, and Virtual Desktop (not gamescope) configured in advanced display settings. The launcher and game start fine every time like this, but if you race for longer than 1min and 58 seconds all the trees vanish if your map has dynamic textures. Some maps don't and those remain fine but they don't look as good in general.

Gotta practice those hairpins =] . Looks like a lot of fun!

A previous post says you're doing some gaming on Ubuntu, did you mange to get RBR working there too? I tried for a short time with bottles but didn't put much effort into it. I'm curious what your approach was.

EDIT: I tried this again and I remember the issue I had now. I use the tmff2 Thrustmaster dkms driver. The game works fine in bottles, and running control from the wine console and using the force feedback test dialog works fine, I can get all the built in effects to work. However in the game FFB does not work nor do the in game tests. I've tried some of the RSF compatibility registry hacks but they don't seem to do anything. That's not surprising though since I think they are intended to match specific VID:PID device strings.

I'd really love to get this game working, I see so many cool videos and there's so much variety with all the mods. Maybe this will be the final push to build an OpenFFBoard wheel or something =].

We are in a weird state it seems where some stuff requires amdvlk and some stuff requires that amdvlk not be installed.... Like the latest gamescope doesn't work for me when it's installed unless you explicitly set the AMD_VULKAN_ICD=RADV env var but raytracinginvulkan requires the amdvlk package since it's not as mature of a project and makes too many assumptions.

Thanks, that's really great info! Aaaannd just like that the stack of keyboard boxes gets a little higher and my wallet gets a little lighter =]