When using T.Flight Hotas One, the throttle axis doesn’t work on some aircraft like Robin Cap 10.
I don’t have any issue with the throttle axis of my Hotas on some other aircraft.
The Xbox controller works fine (A / B).
Binding the Increase / Decrease throttle to Hotas A / B keys doesn’t work neither.
FREQUENCY OF ISSUE
Always with Robin Cap 10.
REPRODUCTION STEPS
Buy an T.Flight Hotas One
Buy a Robin Cap 10 in Career Mode
Try to use the throttle axis of the Hotas, or to control the throttle binding Increase / Decrease to any key of the Hotas
Try to create new aircraft
YOUR SETTINGS
Playing on Xbox, not in preview mode (but I used to have it installed)
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
I tried it on my setup, but I couldn’t reproduce this issue with the CAP-10.
My setup is as follows: a 3m cable ended with a USB hub, an Xbox controller, a keyboard, a mouse, and a T.Flight Hotas 1 connected on it.
I have an Xbox S and an Xbox X, and I tried it on both.
I tried in career mode, both as an employee and as a freelancer (I’ve a conpany that already own the CAP-10).
SU3 (1.5.27), deluxe version without additionnal aircraft/airports.
T.Flight has a specific configuration (for curves, buttons), but nothing specific to the CAP-10.
Unfortunately (or fortunately), the throttle works perfectly for me.
Edit: Nevertheless, I have a similar strange bug, with the SAAB-340 (available in Deluxe edition).
In freeflight mode, it works fine with the HOTAS-1 (all axis have no issue, SAAB-340 is flyable).
This aircraft is also available for some passengers flights, in career/employee mode.
But, when trying that, the X/Y and rudder axis are inoperative. Only the throttle works, and others buttons works fine too ! How is it possible ?
Sure, there is sometimes a terrible mess with XBOX + HOTAS-1, but it appears to be unpredicable.
Of course. In any case, it is impossible to put the switch XBOX/PC in the wrong position.
If the switch is in the PC position, the HOTAS-1 is not recognized by the Xbox.
Similarly, if the switch is in the XBOX position, the HOTAS-1 is not recognized by the PC as a game controller.
This is simply because the USB device doesn’t share the same PID (Peripheral ID) depending on whether the switch is on PC or Xbox.
In the Xbox mode, the PID is B86C.
In the PC mode, the PID is B86D.
This is clearly visible in Windows Device Manager, where the HOTAS-1 is only recognized as a “Game controler HID” when the switch is in the correct position.
So, at statrtup on PC, the driver is not loaded if the switch is on XBOX position.
It’s similar on XBOX, where the peripheral is not visible if the switch is on PC position.
