Open kralle71 opened 8 months ago
Now I tried in Windows. Steam recognizes the Flightstick. MSFS recognizes the Flightstick and everything works.
provided some screenshots https://imgur.com/a/TSYaEDt
as you can see. Linux Steam converts both my Flightstick and my Xbox Gamepad to "Generic X-BOX Pad"
Maybe the problem is because of the vendor "Turtle Beach"?
The logs say:
[2024-01-09 10:51:25] Local Device Found type: 10f5 7055 path: sdl://1 serial_number: - 0
Controller has an Invalid or missing unit serial number, setting to '10f5-7055-763380'
Confirming that I have the same issue using Flatpak Steam on NixOS 23.11 with the VelocityOne Flightstick.
Trying to run MSFS with Proton Experimental.
I tried slightly different udev rules:
KERNEL=="hidraw*", ATTRS{idVendor}=="10f5", ATTRS{idProduct}=="7055", MODE="0660", TAG+="uaccess"
KERNEL=="js*", ATTRS{idVendor}=="10f5", ATTRS{idProduct}=="7055", MODE="0660", TAG+="uaccess"
They didn't seem to change anything.
controller.txt
shows the following when I plug in the controller:
[2024-01-27 01:54:02] Local Device Found
type: 10f5 7055
path: sdl://13
serial_number: - 0
[2024-01-27 01:54:02] Manufacturer:
[2024-01-27 01:54:02] Product: Generic X-Box pad
[2024-01-27 01:54:02] Release: 111
[2024-01-27 01:54:02] Interface: -1
[2024-01-27 01:54:02] !! Steam controller device opened for index 0.
[2024-01-27 01:54:02] Steam Controller reserving XInput slot 0
[2024-01-27 01:54:02] Controller has an Invalid or missing unit serial number, setting to '10f5-7055-24364d6'
[2024-01-27 01:54:02] Controller PollState Changed from 0 to 1
[2024-01-27 01:54:03] BYieldingQueryAccountsRegisteredToController
[2024-01-27 01:54:03] CClientJobFetchPersonalizationFileID - AutoCloud
[2024-01-27 01:54:03] BYieldingRegisterSteamController
[2024-01-27 01:54:03] BYieldingCompleteSteamControllerRegistration
[2024-01-27 01:54:04] BYieldingCompleteSteamControllerRegistration - Error committing registration completion of controller & account pair: 10f5-7055-24364d6 Invalid Parameter
The controller does show up in the controller test window, with the correct vendor/product IDs, and the input does move the joysticks/triggers in the test window.
Probably worth mentioning that I have a Bottles installation running wine-ge-proton-8-25
, and the joystick shows up as expected in the wine control panel.
Tested X-Plane 12 running natively today and the flight stick works fine. Output in controller.txt is different:
[2024-02-02 05:11:48] Local Device Found
type: 10f5 7055
path: sdl://14
serial_number: - 0
[2024-02-02 05:11:48] Manufacturer:
[2024-02-02 05:11:48] Product: Generic X-Box pad
[2024-02-02 05:11:48] Release: 111
[2024-02-02 05:11:48] Interface: -1
[2024-02-02 05:11:48] !! Steam controller device opened for index 0.
[2024-02-02 05:11:48] Steam Controller reserving XInput slot 0
[2024-02-02 05:11:48] Controller has an Invalid or missing unit serial number, setting to '10f5-7055-24364d6'
[2024-02-02 05:11:48] Controller PollState Changed from 0 to 1
[2024-02-02 05:11:49] BYieldingQueryAccountsRegisteredToController
[2024-02-02 05:11:49] CClientJobFetchPersonalizationFileID - AutoCloud
[2024-02-02 05:12:03] Controller 0 mapping uses xinput : false
[2024-02-02 05:12:06] Controller 0 mapping uses xinput : false
[2024-02-02 05:12:06] Controller 0 mapping uses xinput : false
[2024-02-02 05:12:06] Controller 0 mapping uses xinput : false
The last four lines appear after launching the game.
I tested the joystick in DCS: A-10C Warthog and it also shows up as "Generic X-Box Pad". Seems to point to an issue with Proton games only - native games (at least X-Plane 12) work fine.
I have the same issue, running on Arch Linux with Arch repo Steam installation, also Turtle Beach Velocity One Flightstick. MSFS 2020 using Proton Experimental only picks up the joystick as a generic gamepad, leading to axes and buttons not being available. This seems like an issue with wine, after resetting the wine (proton) prefix for MSFS 2020 and applying these: https://www.reddit.com/user/xatrekak/comments/12hnz0d/fixing_vkb_and_virpil_hotas_running_on_linux/ steps, the joystick is correctly recognized as such.
Your system information
Please describe your issue in as much detail as possible:
I bought a new Joystick (TurtleBeach VelocityOne Flightstick) to play MSFS.
My OS recognizes it as intended. evtest, jstest, AntiMicroX all work.
Game is running fine but Steam converts my Joystick to a XBOX Controller. That leads to problems with axis mapping to the triggers, buttons are mapped to xbox buttons, missing axes.
I tried multiple games, all games recognize a controller, but no flightstick.
I tried Steam Repo Version (OpensuseTumbleweed) and Flatpak Version.
I tried to disable/enable Steam Input for per game settings.
I tried chmod 666 to
I tried to chown those.
I tried SDL_JOYSTICK_DISABLE_UDEV=1
I tried to modify
with
udevadmn gives:
udevadm info -an /dev/input/event4
Steam Logs:
steam-logs.tar.gz
cat .steam/steam/logs/controller.txt
Any idea how to use my flightstick?