Only Throttle shifted keys are not working (4.37)

janjan

This is the first time I am using the launcher.
I’ve always used the keyfile to generate the DX assignments.
I mapped all my stick and throttle keys, similar to 4.36.
I assigned a Shift and assigned the shifted keys.

The assignments for the stick, shifted and unshifted work fine and so do the keys for the throttle.
The problem is that the shifted keys for the throttle do not work at all.

If I copy paste my old DX assignment to the new keyfile and set :

set g_nButtonsPerDevice 32

in the cfg file (the launcher sets this to 128), the throttle shifted keys also work.

I can keep it like this but this prevents me from using the launcher.

Any idea what can cause it?

MaxWaldorf

just tick the box to override the new launcher settings…

That should give you ground to do what you want manuallly

airtex2019

@janjan said in Only Throttle shifted keys are not working (4.37):

I can keep it like this but this prevents me from using the launcher.

Using the Launcher, to launch? You can click the “don’t apply overrides” checkbox.

Using the Launcher, to maintain and modify key/dx bindings? Yes… there seems to be no easy path to “import” an older key file, esp. one built for multiple devices w/ 32 buttons-per-device.

Any idea what can cause it?

I think even in 4.36 era the AL imposed 128-buttons-per-device. It is the way forward, no doubt… but it is a pain for those of us with legacy key files.

janjan

@MaxWaldorf Thank,
I’ll try it.
What I don’t understand is why are the shifted keys not working for the throttle?

As I mentioned I mapped all teh keys, both to the throttle and stick, I use X56, and the keys for the stick work fine, both shifted and unshifted.
the keys for the throttle work but only for the unshifted assignments.

The mapping looks ok, taking to account the 128 buttons per device,
This is working: (stick)

SimTriggerSecondDetent 0 -1 -2 0 0x0 0
SimTriggerFirstDetent 256 -1 -2 0 0x0 0

And for the throttle:

SimCursorEnable 128 -1 -2 0 0x0 0
SimRadarCursorZero 384 -1 -2 0 0x0 0

The last one, (SimRadarCursorZero 384 -1 -2 0 0x0 0 is not working.

airtex2019

@janjan verify your
g_nHotasPinkyShiftMagnitude setting?

(the New Launcher will write that into cfg file too … in general if you’re setting g_nButtonsPerDevice, you’ll want to set g_nHotasPinkyShiftMagnitude, too)

janjan

@airtex2019
When I do this manually, using the excel file and not using the launcher all is working well.
When I try to use the launcher I le it set those values and as I mentioned it working for the stick (shifted and unshifted) but for the throttle only unshifted.

GR_Macedon

@airtex2019 said in Only Throttle shifted keys are not working (4.37):

g_nButtonsPerDevice

Put this line to “Falcon BMS User.cfg” and it will work;

set g_nHotasPinkyShiftMagnitude 256

janjan

@GR_Macedon This is the default and is already set to 256.

As I wrote the shift IS working but only for the stick when set via the launcher.

GR_Macedon

@janjan don’t use the custom launcher.
Use the old one

janjan

@GR_Macedon
I’ve never used it and though to give it a try now but I’ll stick to the good old keyfile.
Or as was mentioned here, disable any changes by the launcher (this works)

airtex2019

@janjan said in Only Throttle shifted keys are not working (4.37):

@GR_Macedon This is the default and is already set to 256.

As I wrote the shift IS working but only for the stick when set via the launcher.

oh I see your point now … yes that is weird. not sure how that could happen, or how to debug further.

does this happen to you when starting from fresh new (empty, or default) key file in the New Launcher? if so, it’s maybe worth investigating further.

chihirobelmo

Give me BMS AUTO.key and cfg

janjan

@chihirobelmo
This is the last part:
It looks legit, the shift key is assigned as 4 & 260
4 + 256
The throttle are also defined good, assuming 128 assignment for each controller.

BTW, I just tried it again and now the throttle is not working at all.
If I set it to 32 again and use my old keyfile all is well.
I will simply not use teh launcher or use it without letting it change the keyfile and cfg

E.g.

SimCursorEnable 128 -1 -2 0 0x0 0
SimRadarCursorZero 384 -1 -2 0 0x0 0

128+256=384

SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "========= STICK UNSHIFTED ========="
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "========= STICK SHIFTED ========="
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "======== THROTTLE UNSHIFTED ========"
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "========== THROTTLE SHIFTED =========="

#======== X56 HOTAS Stick ========
SimTriggerSecondDetent 0 -1 -2 0 0x0 0
SimTriggerFirstDetent 256 -1 -2 0 0x0 0
SimPickle 1 -1 -2 0 0x0 0
SimMissileStep 2 -1 -2 0 0x0 0
SimFuelDoorToggle 258 -1 -2 0 0x0 0
SimHotasShift 4 -1 -2 0 0x0 0
SimHotasShift 260 -1 -2 0 0x0 0
SimAPOverride 5 -1 -2 0 0x0 0
SimEmergencyJettison 261 -1 -2 0 0x0 0
AFElevatorTrimUp 6 -1 -2 0 0x0 0
OTWVRZoomToggle 262 -1 -2 0 0x0 0
AFAileronTrimRight 7 -1 -2 0 0x0 0
AFElevatorTrimDown 8 -1 -2 0 0x0 0
OTWVRZoom 264 -1 -2 0 0x0 0
AFAileronTrimLeft 9 -1 -2 0 0x0 0
SimDMSUp 10 -1 -2 0 0x0 0
SimDMSRight 11 -1 -2 0 0x0 0
SimDMSDown 12 -1 -2 0 0x0 0
SimDMSLeft 13 -1 -2 0 0x0 0

#======== X56 HOTAS Stick : POV ========
SimTMSUp 0 -1 -3 0 0x0 0
SimEWSProgInc 2 -1 -3 0 0x0 0
SimDoNothing 0 -1 -3 1 0x0 0
SimDoNothing 2 -1 -3 1 0x0 0
SimTMSLeft 0 -1 -3 2 0x0 0
SimEWSPGMInc 2 -1 -3 2 0x0 0
SimDoNothing 0 -1 -3 3 0x0 0
SimDoNothing 2 -1 -3 3 0x0 0
SimTMSDown 0 -1 -3 4 0x0 0
SimEWSProgDec 2 -1 -3 4 0x0 0
SimDoNothing 0 -1 -3 5 0x0 0
SimDoNothing 2 -1 -3 5 0x0 0
SimTMSRight 0 -1 -3 6 0x0 0
SimEWSPGMDec 2 -1 -3 6 0x0 0
SimDoNothing 0 -1 -3 7 0x0 0
SimDoNothing 2 -1 -3 7 0x0 0

#======== X56 HOTAS Throttle ========
SimCursorEnable 128 -1 -2 0 0x0 0
SimRadarCursorZero 384 -1 -2 0 0x0 0
SimToggleMissileCage 129 -1 -2 0 0x0 0
SimCBEOSB_3L 130 -1 -2 0 0x0 0
SimRadarSnowplow 386 -1 -2 0 0x0 0
AFBrakesOut 131 -1 -2 0 0x0 0
SimWheelBrakes 387 -1 -2 0 0x0 0
AFBrakesIn 132 -1 -2 0 0x0 0
SimNextWaypoint 133 -1 -2 0 0x0 0
SimHsiCourseInc 389 -1 -2 0 0x0 0
SimPrevWaypoint 134 -1 -2 0 0x0 0
SimHsiCrsDecBy1 390 -1 -2 0 0x0 0
AFGearUp 135 -1 -2 0 0x0 0
SimParkingBrakeUp 391 -1 -2 0 0x0 0
AFGearDown 136 -1 -2 0 0x0 0
SimParkingBrakeDown 392 -1 -2 0 0x0 0
ExtinguishMasterCaution 137 -1 -2 0 0x0 0
SimCATSwitch 393 -1 -2 0 0x0 0
AFResetTrim 138 -1 -2 0 0x0 0
SimVisorToggle 394 -1 -2 0 0x0 0
SimToggleTFR 139 -1 -2 0 0x0 0
SimFLCSReset 395 -1 -2 0 0x0 0
SimAVTRToggle 140 -1 -2 0 0x0 0
SimManualFlyup 396 -1 -2 0 0x0 0
OTWSelect3DCockpitMode 147 -1 -2 0 0x0 0
RecenterTrackIR 403 -1 -2 0 0x0 0
OTWViewZoomIn 148 -1 -2 0 0x0 0
FOVDefault 404 -1 -2 0 0x0 0
OTWSelectOrbitMode 149 -1 -2 0 0x0 0
OTWTrackTargetToWeapon 405 -1 -2 0 0x0 0
OTWViewZoomOut 150 -1 -2 0 0x0 0
OTWSelectF3PadlockMode 406 -1 -2 0 0x0 0
SimICPAA 151 -1 -2 0 0x0 0
SimToggleMissileBoreSlave 407 -1 -2 0 0x0 0
SimDeselectOverride 408 -1 -2 0 0x0 0
SimICPAG 153 -1 -2 0 0x0 0
SimNextAGWeapon 409 -1 -2 0 0x0 0
SimSelectMRMOverride 154 -1 -2 0 0x0 0
OTWSelectF3PadlockModeAA 410 -1 -2 0 0x0 0
SimTransmitCom1 155 -1 -2 0 0x0 0
SimCommsSwitchLeft 411 -1 -2 0 0x0 0
SimTransmitCom2 156 -1 -2 0 0x0 0
SimCommsSwitchRight 412 -1 -2 0 0x0 0

#======== X56 HOTAS Throttle : POV ========
SimDoNothing 1 -1 -3 0 0x0 0
SimDoNothing 3 -1 -3 0 0x0 0
SimDoNothing 1 -1 -3 1 0x0 0
SimDoNothing 3 -1 -3 1 0x0 0
SimDoNothing 1 -1 -3 2 0x0 0
SimDoNothing 3 -1 -3 2 0x0 0
SimDoNothing 1 -1 -3 3 0x0 0
SimDoNothing 3 -1 -3 3 0x0 0
SimDoNothing 1 -1 -3 4 0x0 0
SimDoNothing 3 -1 -3 4 0x0 0
SimDoNothing 1 -1 -3 5 0x0 0
SimDoNothing 3 -1 -3 5 0x0 0
SimDoNothing 1 -1 -3 6 0x0 0
SimDoNothing 3 -1 -3 6 0x0 0
SimDoNothing 1 -1 -3 7 0x0 0
SimDoNothing 3 -1 -3 7 0x0 0

chihirobelmo

@janjan
How about falcon BMS.cfg? there should be launcher-generated options with // override comments setting g_nHotasPinkyShiftMagnitude g_nButtonsPerDevice , also check you are not re-defining g_nHotasPinkyShiftMagnitude g_nButtonsPerDevice at falcon bms user.cfg

in my case it is like this:

set g_nButtonsPerDevice 128          // SETUP OVERRIDE
set g_nHotasPinkyShiftMagnitude 384          // SETUP OVERRIDE
set g_bHotasDgftSelfCancel 0          // SETUP OVERRIDE
set g_b3DClickableCursorAnchored 1          // SETUP OVERRIDE
set g_nVRHMD 0          // SETUP OVERRIDE
set g_nNumOfPOVs 2      // SETUP OVERRIDE
set g_nPOV1DeviceID 2   // SETUP OVERRIDE
set g_nPOV1ID 0         // SETUP OVERRIDE
set g_nPOV2DeviceID 3   // SETUP OVERRIDE
set g_nPOV2ID 0         // SETUP OVERRIDE

janjan

@chihirobelmo Mine are similar apart from the g_nHotasPinkyShiftMagnitude.
The launcher, in my case set it to 256 and I can see in the keyfile that the shifted keys are really 256 steps apart.
How come your is 384? How many device are you using?

set g_nButtonsPerDevice 128          // SETUP OVERRIDE
set g_nHotasPinkyShiftMagnitude 256          // SETUP OVERRIDE
set g_bHotasDgftSelfCancel 1          // SETUP OVERRIDE
set g_b3DClickableCursorAnchored 1          // SETUP OVERRIDE
set g_nVRHMD 0          // SETUP OVERRIDE
set g_nNumOfPOVs 2      // SETUP OVERRIDE
set g_nPOV1DeviceID 2   // SETUP OVERRIDE
set g_nPOV1ID 0         // SETUP OVERRIDE
set g_nPOV2DeviceID 3   // SETUP OVERRIDE
set g_nPOV2ID 0         // SETUP OVERRID

chihirobelmo

set g_nButtonsPerDevice 128          // SETUP OVERRIDE
set g_nHotasPinkyShiftMagnitude 256          // SETUP OVERRIDE

if this is applied and these are not working

SimCursorEnable 128 -1 -2 0 0x0 0
SimRadarCursorZero 384 -1 -2 0 0x0 0

there are 2 possibilities:

Device sorting not properly generated
BMS code bug

janjan

@chihirobelmo
Device sorting is good.
I only have 2 devices and when I revert to the original cfg + my own keyfile with 32 buttons per device and all is working well.

I’ll just use my own keyfile and set the launcher to not change the keyfile nor the cfg.

All good

Only Throttle shifted keys are not working (4.37)

94

13.6k

19.1k

327.3k