Linux (Fedora) Strum Not Working

[night mulch]

Hello, I tried a lot of troubleshooting myself, but have been running into issues trying to get my new polybar micro working in YARG. I followed the extra steps in the README and am still running into issues with the strum not being detected. The rest of the keys seem to all show up correctly. Any help is greatly appreciated!

[wild void]

you should make sure that you have the proper libraries installed - adding udev rules is not everything, you also have to install hidapi and libudev
on fedora that should be: dnf install hidapi systemd-libs

my friend was having this exact issue, and installing those libraries fixed the issue for him

[night mulch]

Thanks for the suggestion! I ran the install command and both were listed as installed. I uninstalled and reinstalled and rebooted my system and the problem persists

[night mulch]

I attempted to reinstall everything and ended up getting further. If I connect my polybar via bluetooth, my game crashes similar to https://github.com/YARC-Official/YARG/issues/985, but wired, things work as they did before - no strumming input is detected when setting up keybinds. I will keep digging

[random vortex]

you're missing one last crucial step here
rather than reciting this info, you should just link to the readme lol

[random vortex]

make sure you installed the udev rule file to allow YARG to access hidraw devices

if you're sure you've done that already, your log file would be helpful for troubleshooting

[silk thicket]

Log files contain debug information that can be helpful for developers when diagnosing problems or bugs.
Each log in the folder is listed with a date. Please send the relevant log, which in many cases will be the most recent one.

Accessing Logs From In-Game

• Go to YARG's settings menu
• Click on "All Settings" on the top
• Scroll down to "File Management" and click it
• Click on "Open Persistent Data Path"
• Navigate into the logs folder

Accessing Logs Without the Game

If for whatever reason you cannot open the game, here's how you can access the log folder:

• Windows: C:\Users\<you>\AppData\LocalLow\YARC\YARG\release\logs
  • You can get here quickly by pressing Windows Key + R then typing in exactly: %userprofile%\AppData\LocalLow\YARC\YARG\release\logs
• Mac: ~/Library/Application Support/YARC/YARG/release/logs
• Linux: ~/.config/unity3d/YARC/YARG/release/logs
  (if you're playing on a dev build, it may be in the dev folder instead of the release one)

[wild void]

yeah thats on me, although the op said that they have done the extra steps. still mb for reciting half of the steps lol

[random vortex]

i did miss that part myself lol, tweaked my response

[night mulch]

I had also linked the linux section in the README to show which steps I followed.

I had to connect with USB instead of BT because BT is still causing the crashing, but here is the log file

[random vortex]

hm, i don't see any errors in the log related to this issue

seems to be loading hidapi and libudev properly

[wild void]

i've got an idea, can you try doing the same thing but run the game executable without the launcher?

and also send the log again

the game actually inherits environment variables from the launcher which may cause some issues (and has caused issues in the past)