T.Flight HOTAS One
45 posts
• Page 1 of 5 • 1, 2, 3, 4, 5
T.Flight HOTAS One
I created a new topic, as I didn't want to clutter the T.Flight One X (PC/PS4) thread and cause confusion with the T.Flight One X (Xbox One/PC) versions, as they appear to be different internally.
Running the stick in Xbox One mode shows very unusual behavior. The ABXY & Hat appear correct, but several other buttons are not.
Moving the throttle lever starts starts with all buttons zero. as you throttle up, first button 5 jumps to 100% all at once. At the detent (50% throttle, button 5 jumps to zero, button 8 goes to 100%. Past the detent both button 5 & 8 are at 100%
Rudder bar on throttle, twist stick, and pedals (if connected) do not register.
Pushing B3 on throttle makes button 8 go to 100.1%
Pushing B4 makes button 8 got to 200.20%
F2 button makes button 8 go to .2%
B2 button makes button 8 go to 50.05%
Trigger button makes button 8 go to .10%
B1 Button makes Button 8 go to 25.02%
B5 button makes button 8 go to 400.39%
Pressing multiple buttons make button add both numbers together. (F2 + B2) = 50.25%
When button 5 & 8 are activated by the throttle, pressing one of the buttons cancels out the button 5 & input.
Like I said, very weird. I have been using this flightstick in PC mode, it behaves more normally with the Titan 8 device in that mode.
Xbox Mode Descriptors:
Capture of USB Descriptors:
[USB DESCRIPTOR]
12 01 00 02 FF FF FF 40 4F 04 8C B6 00 01 01 02 03 01 09 02 20 00 01 01 00 A0 32 09 04 00 00 02 FF 47 D0 00 07 05 81 03 40 00 04 07 05 01 03 40 00 04
[STRING 1 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 01 04 09 00 1A
1A 03 54 00 68 00 72 00 75 00 73 00 74 00 6D 00 61 00 73 00 74 00 65 00 72 00
[STRING 2 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 02 04 09 00 26
26 03 54 00 2E 00 46 00 6C 00 69 00 67 00 68 00 74 00 20 00 48 00 6F 00 74 00 61 00 73 00 20 00 4F 00 6E 00 65 00
[STRING 3 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 03 04 09 00 22
22 03 30 00 30 00 30 00 30 00 45 00 45 00 32 00 31 00 39 00 36 00 38 00 39 00 33 00 39 00 32 00 37 00
PC mode has two settings. 4/6 Axis mode (Xbox On) & 5/8 mode (LED OFF)
In either PC mode, the Xbox button is used to change between them, it is not available for use on the titan two.
When the THRP pedals are connected, Toe brake left mapped to button 5, 100% unpressed, and falls to zero as the pedal is pushed.
Toe Brake Right is mapped to button 8, 100% when unpressed and falls to zero as the pedal is pushed in.
in 4/6 Axis mode, the Twist Stick, the Rudder bar, & the THRP optional rudder petals all map to Stick1_Y
in 5/8 Axis mode, the Twist Stick is Stick1_Y, and the rudder bar is mapped to Point 2_Y axis, the THRP rudders are mapped to Point2_X.
PC Mode Descriptors:
[USB DESCRIPTOR]
12 01 10 01 00 00 00 40 4F 04 8D B6 00 01 01 02 00 01 09 02 22 00 01 01 00 A0 32 09 04 00 00 01 03 00 00 00 09 21 11 01 00 01 22 74 00 07 05 81 03 40 00 05
[STRING 1 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 01 04 09 00 1A
1A 03 54 00 68 00 72 00 75 00 73 00 74 00 6D 00 61 00 73 00 74 00 65 00 72 00
[STRING 2 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 02 04 09 00 26
26 03 54 00 2E 00 46 00 6C 00 69 00 67 00 68 00 74 00 20 00 48 00 6F 00 74 00 61 00 73 00 20 00 4F 00 6E 00 65 00
[INTERFACE 0 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 00 00 74
05 01 09 04 A1 01 85 01 09 30 09 31 15 00 26 FF 03 75 10 95 02 81 02 09 32 09 35 09 33 09 34 09 36 09 37 15 00 26 FF 00 75 08 95 06 81 02 09 39 15 00 25 07 35 00 46 3B 01 65 14 75 04 95 01 81 42 65 00 05 09 19 01 29 0F 15 00 25 01 75 01 95 0F 81 02 75 05 95 01 81 01 06 00 FF 09 21 75 08 95 32 81 02 06 F0 FF 09 40 85 F2 09 47 75 08 95 3F B1 02 C0
Running the stick in Xbox One mode shows very unusual behavior. The ABXY & Hat appear correct, but several other buttons are not.
Moving the throttle lever starts starts with all buttons zero. as you throttle up, first button 5 jumps to 100% all at once. At the detent (50% throttle, button 5 jumps to zero, button 8 goes to 100%. Past the detent both button 5 & 8 are at 100%
Rudder bar on throttle, twist stick, and pedals (if connected) do not register.
Pushing B3 on throttle makes button 8 go to 100.1%
Pushing B4 makes button 8 got to 200.20%
F2 button makes button 8 go to .2%
B2 button makes button 8 go to 50.05%
Trigger button makes button 8 go to .10%
B1 Button makes Button 8 go to 25.02%
B5 button makes button 8 go to 400.39%
Pressing multiple buttons make button add both numbers together. (F2 + B2) = 50.25%
When button 5 & 8 are activated by the throttle, pressing one of the buttons cancels out the button 5 & input.
Like I said, very weird. I have been using this flightstick in PC mode, it behaves more normally with the Titan 8 device in that mode.
Xbox Mode Descriptors:
Capture of USB Descriptors:
[USB DESCRIPTOR]
12 01 00 02 FF FF FF 40 4F 04 8C B6 00 01 01 02 03 01 09 02 20 00 01 01 00 A0 32 09 04 00 00 02 FF 47 D0 00 07 05 81 03 40 00 04 07 05 01 03 40 00 04
[STRING 1 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 01 04 09 00 1A
1A 03 54 00 68 00 72 00 75 00 73 00 74 00 6D 00 61 00 73 00 74 00 65 00 72 00
[STRING 2 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 02 04 09 00 26
26 03 54 00 2E 00 46 00 6C 00 69 00 67 00 68 00 74 00 20 00 48 00 6F 00 74 00 61 00 73 00 20 00 4F 00 6E 00 65 00
[STRING 3 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 03 04 09 00 22
22 03 30 00 30 00 30 00 30 00 45 00 45 00 32 00 31 00 39 00 36 00 38 00 39 00 33 00 39 00 32 00 37 00
PC mode has two settings. 4/6 Axis mode (Xbox On) & 5/8 mode (LED OFF)
In either PC mode, the Xbox button is used to change between them, it is not available for use on the titan two.
When the THRP pedals are connected, Toe brake left mapped to button 5, 100% unpressed, and falls to zero as the pedal is pushed.
Toe Brake Right is mapped to button 8, 100% when unpressed and falls to zero as the pedal is pushed in.
in 4/6 Axis mode, the Twist Stick, the Rudder bar, & the THRP optional rudder petals all map to Stick1_Y
in 5/8 Axis mode, the Twist Stick is Stick1_Y, and the rudder bar is mapped to Point 2_Y axis, the THRP rudders are mapped to Point2_X.
PC Mode Descriptors:
[USB DESCRIPTOR]
12 01 10 01 00 00 00 40 4F 04 8D B6 00 01 01 02 00 01 09 02 22 00 01 01 00 A0 32 09 04 00 00 01 03 00 00 00 09 21 11 01 00 01 22 74 00 07 05 81 03 40 00 05
[STRING 1 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 01 04 09 00 1A
1A 03 54 00 68 00 72 00 75 00 73 00 74 00 6D 00 61 00 73 00 74 00 65 00 72 00
[STRING 2 DESCRIPTOR]
00 00 00 02 00 00 02 01 80 06 03 02 04 09 00 26
26 03 54 00 2E 00 46 00 6C 00 69 00 67 00 68 00 74 00 20 00 48 00 6F 00 74 00 61 00 73 00 20 00 4F 00 6E 00 65 00
[INTERFACE 0 HID DESCRIPTOR]
00 00 00 02 00 00 02 01 81 06 22 00 00 00 00 74
05 01 09 04 A1 01 85 01 09 30 09 31 15 00 26 FF 03 75 10 95 02 81 02 09 32 09 35 09 33 09 34 09 36 09 37 15 00 26 FF 00 75 08 95 06 81 02 09 39 15 00 25 07 35 00 46 3B 01 65 14 75 04 95 01 81 42 65 00 05 09 19 01 29 0F 15 00 25 01 75 01 95 0F 81 02 75 05 95 01 81 01 06 00 FF 09 21 75 08 95 32 81 02 06 F0 FF 09 40 85 F2 09 47 75 08 95 3F B1 02 C0
-
Capt moore - Sergeant Major
- Posts: 84
- Joined: Wed Nov 28, 2018 7:52 pm
Re: T.Flight HOTAS One
Hello, I was playing with this more, and was wondering if a firmware tweak could allow this to work in pass through mode (using the xbox one setting)?
First of all, the good news is that the flightstick does authenticate when connected to the Titan 2, and is recognized in some manor.
The bad thing is that it automatically goes full down stick on the menus, which means you can't actually control the xbox one enough to even launch a game. (This problem is not present if you plug the flightstick directly into the console.) I also tried to start a game with the flightstick, then disconnect and put the titan 2 device in the middle, with out any difference.
Another odd thing, normally the xbox one flightstick lights the white light above the xbox button, when plugged into the titan one it does not light up until you press the white xbox button. Looking at it through the Gtuner app, it doesn't register any inputs at all at all when the xbox light is off. I do see the usb A shows Xbox one in (full passthrough) along with usb -c Xbox one Out Full passthrough.
After I press the xbox button on the flightstick, it then registers I get lots of other problem of course, for example the throttle doesn't map correctly to any axis or button, button 5 & eight jump around, but only to 0 or 100, nothing in-between.
After I almost wonder if it's a power issue, although that doesn't make much sense to me as there is really nothing to draw much power. If i can find a compatible power source, I may try that and see if anything changes.
Is there any plans for ConsoleTuner to obtain a thrustmaster Hotas One ($80 on amazon) and look into the problem?
Thanks for any support.
First of all, the good news is that the flightstick does authenticate when connected to the Titan 2, and is recognized in some manor.
The bad thing is that it automatically goes full down stick on the menus, which means you can't actually control the xbox one enough to even launch a game. (This problem is not present if you plug the flightstick directly into the console.) I also tried to start a game with the flightstick, then disconnect and put the titan 2 device in the middle, with out any difference.
Another odd thing, normally the xbox one flightstick lights the white light above the xbox button, when plugged into the titan one it does not light up until you press the white xbox button. Looking at it through the Gtuner app, it doesn't register any inputs at all at all when the xbox light is off. I do see the usb A shows Xbox one in (full passthrough) along with usb -c Xbox one Out Full passthrough.
After I press the xbox button on the flightstick, it then registers I get lots of other problem of course, for example the throttle doesn't map correctly to any axis or button, button 5 & eight jump around, but only to 0 or 100, nothing in-between.
After I almost wonder if it's a power issue, although that doesn't make much sense to me as there is really nothing to draw much power. If i can find a compatible power source, I may try that and see if anything changes.
Is there any plans for ConsoleTuner to obtain a thrustmaster Hotas One ($80 on amazon) and look into the problem?
Thanks for any support.
-
Capt moore - Sergeant Major
- Posts: 84
- Joined: Wed Nov 28, 2018 7:52 pm
Re: T.Flight HOTAS One
One more weird thing. If I plug the flightstick into the titan two and the usb from the titan two to the program port the xbox light powers on fine. If I plug the titan two from the output port to the xbox, it does the whole no light above the xbox thing.
(If the flightstick is plugged directly into my imac, no light shows and the xbox button will not make the light turn on.)
I ordered a power supply on amazon to test, but I suspect lack of power is not the issue. My guess is something in the titan one at first makes the flight stick think it is not an xbox one. Somehow, pressing the xbox button makes it re-evaluate, then it turns on but is giving an output the titan two either can't understand, or the titan two is outputting it in a format that the xbox can't understand.
The odd thing is that it will authenticate thru the titan two, but then misbehaves with the xbox, even in pass thru mode.
(If the flightstick is plugged directly into my imac, no light shows and the xbox button will not make the light turn on.)
I ordered a power supply on amazon to test, but I suspect lack of power is not the issue. My guess is something in the titan one at first makes the flight stick think it is not an xbox one. Somehow, pressing the xbox button makes it re-evaluate, then it turns on but is giving an output the titan two either can't understand, or the titan two is outputting it in a format that the xbox can't understand.
The odd thing is that it will authenticate thru the titan two, but then misbehaves with the xbox, even in pass thru mode.
-
Capt moore - Sergeant Major
- Posts: 84
- Joined: Wed Nov 28, 2018 7:52 pm
Re: T.Flight HOTAS One
The descriptor in XB1 mode are the same as any Xbox One controller. However, based in your description it seems the HID packet format is not the same, that is why you are getting weird inputs.
In PC mode the decoded descriptors are:
Very similar to other Thrustmaster Flight sticks.
Do you have your Titan Two equipped with SD-Card? If yes, please try this for PC Mode:
On Gtuner IV installation folder, open the sub-folder named "configsd" and create a copy of the file "044FB10A.hid", renaming to "044FB68D.hid". With the titan Two connected to the computer, on Gtuner IV -> Device Configuration: click the button labeled "Configure". now plug the stick and check on device monitor the inputs.
In PC mode the decoded descriptors are:
- Code: Select all
[USB DESCRIPTOR]
12 bLength: 18
01 bDescriptorType: 1 - DEVICE
10 01 bcdUSB: 1.10
00 bDeviceClass: 0 (00)
00 bDeviceSubClass: 0 (00)
00 bDeviceProtocol: 0 (00)
40 bMaxPacketSize0: 64
4F 04 idVendor: 044F
8D B6 idProduct: B68D
00 01 bcdDevice: 1.00
01 iManufacturer: 1
02 iProduct: 2
00 iSerialNumber: 0
01 bNumConfigurations: 1
09 bLength: 9
02 bDescriptorType: 2 - CONFIGURATION
22 00 wTotalLength: 34
01 bNumInterfaces: 1
01 bConfigurationValue: 1
00 iConfiguration: 0
A0 bmAttributes: 160 (Bus Powered, Remote Wakeup)
32 MaxPower: 100mA
09 bLength: 9
04 bDescriptorType: 4 - INTERFACE
00 bInterfaceNumber: 0
00 bAlternateSetting: 0
01 bNumEndpoints: 1
03 bInterfaceClass: 3 (03)
00 bInterfaceSubClass: 0 (00)
00 bInterfaceProtocol: 0 (00)
00 iInterface: 0
09 bLength: 9
21 bDescriptorType: 33 - HID
11 01 bcdHID: 1.11
00 bCountryCode: 0
01 bNumDescriptors: 1
22 bDescriptorType: 34
74 00 wDescriptorLength: 116
07 bLength: 7
05 bDescriptorType: 5 - ENDPOINT
81 bEndpointAddress: 1 IN
03 bmAttributes: 3 (Interrupt, None, Data)
40 00 wMaxPacketSize: 64
05 bInterval: 5
[STRING 1 DESCRIPTOR]
Thrustmaster
[STRING 2 DESCRIPTOR]
T.Flight Hotas One
[INTERFACE 0 HID DESCRIPTOR]
05 01 (GLOBAL) USAGE_PAGE 0x0001 Generic Desktop Page
09 04 (LOCAL) USAGE 0x00010004 Joystick (CA=Application Collection)
A1 01 (MAIN) COLLECTION 0x01 Application (Usage=0x00010004: Page=Generic Desktop Page, Usage=Joystick, Type=CA)
85 01 (GLOBAL) REPORT_ID 0x01 (1)
09 30 (LOCAL) USAGE 0x00010030 X (DV=Dynamic Value)
09 31 (LOCAL) USAGE 0x00010031 Y (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
26 FF03 (GLOBAL) LOGICAL_MAXIMUM 0x03FF (1023)
75 10 (GLOBAL) REPORT_SIZE 0x10 (16) Number of bits per field
95 02 (GLOBAL) REPORT_COUNT 0x02 (2) Number of fields
81 02 (MAIN) INPUT 0x00000002 (2 fields x 16 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
09 32 (LOCAL) USAGE 0x00010032 Z (DV=Dynamic Value)
09 35 (LOCAL) USAGE 0x00010035 Rz (DV=Dynamic Value)
09 33 (LOCAL) USAGE 0x00010033 Rx (DV=Dynamic Value)
09 34 (LOCAL) USAGE 0x00010034 Ry (DV=Dynamic Value)
09 36 (LOCAL) USAGE 0x00010036 Slider (DV=Dynamic Value)
09 37 (LOCAL) USAGE 0x00010037 Dial (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
26 FF00 (GLOBAL) LOGICAL_MAXIMUM 0x00FF (255)
75 08 (GLOBAL) REPORT_SIZE 0x08 (8) Number of bits per field
95 06 (GLOBAL) REPORT_COUNT 0x06 (6) Number of fields
81 02 (MAIN) INPUT 0x00000002 (6 fields x 8 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
09 39 (LOCAL) USAGE 0x00010039 Hat switch (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
25 07 (GLOBAL) LOGICAL_MAXIMUM 0x07 (7)
35 00 (GLOBAL) PHYSICAL_MINIMUM 0x00 (0)
46 3B01 (GLOBAL) PHYSICAL_MAXIMUM 0x013B (315)
65 14 (GLOBAL) UNIT 0x00000014 Rotation in degrees [1° units] (4=System=English Rotation, 1=Rotation=Degrees)
75 04 (GLOBAL) REPORT_SIZE 0x04 (4) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 42 (MAIN) INPUT 0x00000042 (1 field x 4 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 1=Null 0=NonVolatile 0=Bitmap
65 00 (GLOBAL) UNIT 0x00000000 No unit (0=None)
05 09 (GLOBAL) USAGE_PAGE 0x0009 Button Page
19 01 (LOCAL) USAGE_MINIMUM 0x00090001 Button 1 Primary/trigger (MULTI=Selector, On/Off, Momentary, or One Shot)
29 0F (LOCAL) USAGE_MAXIMUM 0x0009000F Button 15 (MULTI=Selector, On/Off, Momentary, or One Shot)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
25 01 (GLOBAL) LOGICAL_MAXIMUM 0x01 (1)
75 01 (GLOBAL) REPORT_SIZE 0x01 (1) Number of bits per field
95 0F (GLOBAL) REPORT_COUNT 0x0F (15) Number of fields
81 02 (MAIN) INPUT 0x00000002 (15 fields x 1 bit) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
75 05 (GLOBAL) REPORT_SIZE 0x05 (5) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 01 (MAIN) INPUT 0x00000001 (1 field x 5 bits) 1=Constant 0=Array 0=Absolute 0=Ignored 0=Ignored 0=PrefState 0=NoNull
06 00FF (GLOBAL) USAGE_PAGE 0xFF00 Vendor-defined
09 21 (LOCAL) USAGE 0xFF000021
75 08 (GLOBAL) REPORT_SIZE 0x08 (8) Number of bits per field
95 32 (GLOBAL) REPORT_COUNT 0x32 (50) Number of fields
81 02 (MAIN) INPUT 0x00000002 (50 fields x 8 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
06 F0FF (GLOBAL) USAGE_PAGE 0xFFF0 Vendor-defined
09 40 (LOCAL) USAGE 0xFFF00040
85 F2 (GLOBAL) REPORT_ID 0xF2 (242)
09 47 (LOCAL) USAGE 0xFFF00047
75 08 (GLOBAL) REPORT_SIZE 0x08 (8) Number of bits per field
95 3F (GLOBAL) REPORT_COUNT 0x3F (63) Number of fields
B1 02 (MAIN) FEATURE 0x00000002 (63 fields x 8 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
C0 (MAIN) END_COLLECTION Application
Very similar to other Thrustmaster Flight sticks.
Do you have your Titan Two equipped with SD-Card? If yes, please try this for PC Mode:
On Gtuner IV installation folder, open the sub-folder named "configsd" and create a copy of the file "044FB10A.hid", renaming to "044FB68D.hid". With the titan Two connected to the computer, on Gtuner IV -> Device Configuration: click the button labeled "Configure". now plug the stick and check on device monitor the inputs.
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: T.Flight HOTAS One
J2Kbr wrote:The descriptor in XB1 mode are the same as any Xbox One controller. However, based in your description it seems the HID packet format is not the same, that is why you are getting weird inputs.
In PC mode the decoded descriptors are:
- Code: Select all
[USB DESCRIPTOR]
12 bLength: 18
01 bDescriptorType: 1 - DEVICE
10 01 bcdUSB: 1.10
00 bDeviceClass: 0 (00)
00 bDeviceSubClass: 0 (00)
00 bDeviceProtocol: 0 (00)
40 bMaxPacketSize0: 64
4F 04 idVendor: 044F
8D B6 idProduct: B68D
00 01 bcdDevice: 1.00
01 iManufacturer: 1
02 iProduct: 2
00 iSerialNumber: 0
01 bNumConfigurations: 1
09 bLength: 9
02 bDescriptorType: 2 - CONFIGURATION
22 00 wTotalLength: 34
01 bNumInterfaces: 1
01 bConfigurationValue: 1
00 iConfiguration: 0
A0 bmAttributes: 160 (Bus Powered, Remote Wakeup)
32 MaxPower: 100mA
09 bLength: 9
04 bDescriptorType: 4 - INTERFACE
00 bInterfaceNumber: 0
00 bAlternateSetting: 0
01 bNumEndpoints: 1
03 bInterfaceClass: 3 (03)
00 bInterfaceSubClass: 0 (00)
00 bInterfaceProtocol: 0 (00)
00 iInterface: 0
09 bLength: 9
21 bDescriptorType: 33 - HID
11 01 bcdHID: 1.11
00 bCountryCode: 0
01 bNumDescriptors: 1
22 bDescriptorType: 34
74 00 wDescriptorLength: 116
07 bLength: 7
05 bDescriptorType: 5 - ENDPOINT
81 bEndpointAddress: 1 IN
03 bmAttributes: 3 (Interrupt, None, Data)
40 00 wMaxPacketSize: 64
05 bInterval: 5
[STRING 1 DESCRIPTOR]
Thrustmaster
[STRING 2 DESCRIPTOR]
T.Flight Hotas One
[INTERFACE 0 HID DESCRIPTOR]
05 01 (GLOBAL) USAGE_PAGE 0x0001 Generic Desktop Page
09 04 (LOCAL) USAGE 0x00010004 Joystick (CA=Application Collection)
A1 01 (MAIN) COLLECTION 0x01 Application (Usage=0x00010004: Page=Generic Desktop Page, Usage=Joystick, Type=CA)
85 01 (GLOBAL) REPORT_ID 0x01 (1)
09 30 (LOCAL) USAGE 0x00010030 X (DV=Dynamic Value)
09 31 (LOCAL) USAGE 0x00010031 Y (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
26 FF03 (GLOBAL) LOGICAL_MAXIMUM 0x03FF (1023)
75 10 (GLOBAL) REPORT_SIZE 0x10 (16) Number of bits per field
95 02 (GLOBAL) REPORT_COUNT 0x02 (2) Number of fields
81 02 (MAIN) INPUT 0x00000002 (2 fields x 16 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
09 32 (LOCAL) USAGE 0x00010032 Z (DV=Dynamic Value)
09 35 (LOCAL) USAGE 0x00010035 Rz (DV=Dynamic Value)
09 33 (LOCAL) USAGE 0x00010033 Rx (DV=Dynamic Value)
09 34 (LOCAL) USAGE 0x00010034 Ry (DV=Dynamic Value)
09 36 (LOCAL) USAGE 0x00010036 Slider (DV=Dynamic Value)
09 37 (LOCAL) USAGE 0x00010037 Dial (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
26 FF00 (GLOBAL) LOGICAL_MAXIMUM 0x00FF (255)
75 08 (GLOBAL) REPORT_SIZE 0x08 (8) Number of bits per field
95 06 (GLOBAL) REPORT_COUNT 0x06 (6) Number of fields
81 02 (MAIN) INPUT 0x00000002 (6 fields x 8 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
09 39 (LOCAL) USAGE 0x00010039 Hat switch (DV=Dynamic Value)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
25 07 (GLOBAL) LOGICAL_MAXIMUM 0x07 (7)
35 00 (GLOBAL) PHYSICAL_MINIMUM 0x00 (0)
46 3B01 (GLOBAL) PHYSICAL_MAXIMUM 0x013B (315)
65 14 (GLOBAL) UNIT 0x00000014 Rotation in degrees [1° units] (4=System=English Rotation, 1=Rotation=Degrees)
75 04 (GLOBAL) REPORT_SIZE 0x04 (4) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 42 (MAIN) INPUT 0x00000042 (1 field x 4 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 1=Null 0=NonVolatile 0=Bitmap
65 00 (GLOBAL) UNIT 0x00000000 No unit (0=None)
05 09 (GLOBAL) USAGE_PAGE 0x0009 Button Page
19 01 (LOCAL) USAGE_MINIMUM 0x00090001 Button 1 Primary/trigger (MULTI=Selector, On/Off, Momentary, or One Shot)
29 0F (LOCAL) USAGE_MAXIMUM 0x0009000F Button 15 (MULTI=Selector, On/Off, Momentary, or One Shot)
15 00 (GLOBAL) LOGICAL_MINIMUM 0x00 (0)
25 01 (GLOBAL) LOGICAL_MAXIMUM 0x01 (1)
75 01 (GLOBAL) REPORT_SIZE 0x01 (1) Number of bits per field
95 0F (GLOBAL) REPORT_COUNT 0x0F (15) Number of fields
81 02 (MAIN) INPUT 0x00000002 (15 fields x 1 bit) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
75 05 (GLOBAL) REPORT_SIZE 0x05 (5) Number of bits per field
95 01 (GLOBAL) REPORT_COUNT 0x01 (1) Number of fields
81 01 (MAIN) INPUT 0x00000001 (1 field x 5 bits) 1=Constant 0=Array 0=Absolute 0=Ignored 0=Ignored 0=PrefState 0=NoNull
06 00FF (GLOBAL) USAGE_PAGE 0xFF00 Vendor-defined
09 21 (LOCAL) USAGE 0xFF000021
75 08 (GLOBAL) REPORT_SIZE 0x08 (8) Number of bits per field
95 32 (GLOBAL) REPORT_COUNT 0x32 (50) Number of fields
81 02 (MAIN) INPUT 0x00000002 (50 fields x 8 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
06 F0FF (GLOBAL) USAGE_PAGE 0xFFF0 Vendor-defined
09 40 (LOCAL) USAGE 0xFFF00040
85 F2 (GLOBAL) REPORT_ID 0xF2 (242)
09 47 (LOCAL) USAGE 0xFFF00047
75 08 (GLOBAL) REPORT_SIZE 0x08 (8) Number of bits per field
95 3F (GLOBAL) REPORT_COUNT 0x3F (63) Number of fields
B1 02 (MAIN) FEATURE 0x00000002 (63 fields x 8 bits) 0=Data 1=Variable 0=Absolute 0=NoWrap 0=Linear 0=PrefState 0=NoNull 0=NonVolatile 0=Bitmap
C0 (MAIN) END_COLLECTION Application
Very similar to other Thrustmaster Flight sticks.
Do you have your Titan Two equipped with SD-Card? If yes, please try this for PC Mode:
On Gtuner IV installation folder, open the sub-folder named "configsd" and create a copy of the file "044FB10A.hid", renaming to "044FB68D.hid". With the titan Two connected to the computer, on Gtuner IV -> Device Configuration: click the button labeled "Configure". now plug the stick and check on device monitor the inputs.
Pc mode works fine out of the box. That is what I have been using so far to “convert” the stick for Xbox one use.
I am interested in keeping the hotas in Xbox one mode, for the following reasons.
1. The flightstick will not authenticate as an Xbox controller in pc mode. (It will authenticate in Xbox mode.)
2. If I use another controller to authenticate, the various games set up the flightstick as a controller (digital buttons as rudder, vs analog axis, for example.)
3. It I want to do button swaps or other titan 2 “tricks” it should become much less complicated to not have to remap every control if I can keep it in Xbox mode.
Is there a way I can capture the raw usb packets into a file so you can see if is a simple tweak to change the the way the titan two passes thru them, or if something more complicated is going on?
-
Capt moore - Sergeant Major
- Posts: 84
- Joined: Wed Nov 28, 2018 7:52 pm
Re: T.Flight HOTAS One
I tried using the titan two with a power adapter, as I suspected it didn't help.
-
Capt moore - Sergeant Major
- Posts: 84
- Joined: Wed Nov 28, 2018 7:52 pm
Re: T.Flight HOTAS One
Understood. Please allow me few days to research about the HOTAS One XB1 protocol, maybe I can find some reference on the internet that can help add support for it in XB1 mode.
ConsoleTuner Support Team
-
J2Kbr - General of the Army
- Posts: 20323
- Joined: Tue Mar 18, 2014 1:39 pm
Re: T.Flight HOTAS One
J2Kbr wrote:Understood. Please allow me few days to research about the HOTAS One XB1 protocol, maybe I can find some reference on the internet that can help add support for it in XB1 mode.
Thanks. Let me know if there is a way for me to help.
-
Capt moore - Sergeant Major
- Posts: 84
- Joined: Wed Nov 28, 2018 7:52 pm
Re: T.Flight HOTAS One
J2Kbr wrote:Understood. Please allow me few days to research about the HOTAS One XB1 protocol, maybe I can find some reference on the internet that can help add support for it in XB1 mode.
Have you been able to research anything more about the xb1 flightstick protocol for the Hotas One?
Thanks.
-
Capt moore - Sergeant Major
- Posts: 84
- Joined: Wed Nov 28, 2018 7:52 pm
Re: T.Flight HOTAS One
Same question for the hotas4. Still hoping to get the throttle and rudder paddles recognised, and hopefully an output protocol so that people can use alternate throttle controllers for hotas4 supported games on the ps4:)
-
glenntidbury - Sergeant Major
- Posts: 98
- Joined: Thu May 24, 2018 4:34 pm
45 posts
• Page 1 of 5 • 1, 2, 3, 4, 5
Who is online
Users browsing this forum: No registered users and 171 guests