Solved Twin engine throttles don't work in 3D
-
-
Thanks
-
@MaxWaldorf Thanks, Max. I put the files into 4.37u3/user/config- I tested both the F-16 keyfile and the F-15, and used the Select Engine callbacks .Unfortunately, no change.
You got me thinking about Config, so I compared it to U2. I unchecked Idle Detent, like I had in U2-no change.
Update: SUCCESS. We’re also discussing this issue over on Discord. It was suggested to add set g_bUseXInput 0 to 4.37u3/user/Config/falcon bms.cfg. That fixed it.
I consider this a workaround. I’m LOVING what the Dev’s are starting with Other Jet avionics, and want to explore them. In the meantime, this gets us in the air -
@MaxWaldorf Issue is resolved, fix is set g_bUseXInput 0 .
-
-
-
@Rouge1512 @drtbkj thanks for the patience and help narrowing this down
Can you guys post your DeviceSorting.txt file contents?
I think we need to make xInput smarter about how it detects gamepad devices… maybe AL has a role to play in that too.
-
@airtex2019 said in Twin engine throttles don't work in 3D:
@Rouge1512 @drtbkj thanks for the patience and help narrowing this down
Can you guys post your DeviceSorting.txt file contents?
I think we need to make xInput smarter about how it detects gamepad devices… maybe AL has a role to play in that too.
Hi, Airtex. Thanks to you , tiag, okayasugf on Discord, and Max for the tips. Ain’t no problem we can’t solve together.
I can post the file, please refresh my memory where it is.
Right now my personal set up, besides set g_bUseXInput 0 is…- Max’s user.cfg and the xmls he posted above
- For testing I put
set g_bEnableWIPF18Avionics 0
set g_bEnableWIPF4Avionics 0
set g_bEnableWIPTornadoAvionics 0
if .cfg, as well, although I will be flying with them set to 1
-
@drtbkj said in Twin engine throttles don't work in 3D:
please refresh my memory where it is.
Should be right next to your cfg files… alphabetically
-
Here you are :
{0000046D-0000-0000-0000-504944564944} “Controller (Razer Xbox 360 Controller)”
{02441532-0000-0000-0000-504944564944} “Joystick (Razer Tartarus Pro)”
{200112E0-0000-0000-0000-504944564944} “FSSB R3L MJF SGRH”
{B68F044F-0000-0000-0000-504944564944} “T-Pendular-Rudder”
{FFFF044F-0000-0000-0000-504944564944} “Thrustmaster Virtual Game Controller (root)”
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{0407044F-0000-0000-0000-504944564944} “TCA Q-Eng 1&2”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{0412044F-0000-0000-0000-504944564944} “Viper TQS”Thanks a lot for your help.
-
@drtbkj airtex is the legend who made this possible, without his fix you’d be stuck on the tarmac
-
@okayasugf I got nothin to do with this one… just got wrapped up in the mystery of it
I’ll add a checkbox to AL to enable/disable xInput, and maybe make it “smart” default when it sees a mix of gamepad and higher end hotas devices
-
@okayasugf said in Twin engine throttles don't work in 3D:
@drtbkj airtex is the legend who made this possible, without his fix you’d be stuck on the tarmac
Yes, Compadre, but you were the one who pointed me to the the Discord post. Don’t worry, though, max kudos to Airtex!