Anyone have a solution for Saitek X55 Rhino setup for 4.37 ?
-
In 4.36 my setup was based on the key file made by Snelle to 4.33. Everything was OK. I used the same key file to 4.37, but several things do not work. The mini-stick and radar cursor works grate, but not MRM/Dog fight override. I read buttun 158 and 159 in stead of 62 and 63. Weels up/down i read button 136 and 137 in stead of 41 and 40. They are all 96 apart.
Please be advised. -
@Killroy before 4.36, all the button-numbering was done 32-per-device
after 4.36, the default is now 128
for anyone with more than 1 device, this messes up legacy key files
no easy solution sorry … short-term, you can force it back to 32 with ‘falcon bms user.cfg’, but you will have to avoid the New Launcher and use old launcher, or launch BMS directly.
-
@airtex2019 Thank you for as usual a good answer. Ok, lets hope the new Launcher will be more correlated to the world out there of odd HOTAS equipment. Do you or (somebody else) have the possibility to link to a tread showing me how i can force 4.37 back to 32 per device with lines in Falcon BMS user.cfg, I would mutch apreciate that.
-
@Killroy for using a hand-managed key file, I recommend specifying all of the following in ‘falcon bms user.cfg’ so there’s no ambiguity and no chance of various tools or bms updates overwriting it and breaking things.
(double-check the right values for dx-shift magnitude… 256 used to be the default/standard, in the days of 32-button-per-device. also double-check the 8-way-hats)
also review your DeviceSorting.txt to make sure it’s what the key file expects … eg. joystick on line 1, throttle on line 2.
// // Input stuff set g_nButtonsPerDevice 32 set g_nHotasPinkyShiftMagnitude 256 set g_nNumOfPOVs 2 set g_nPOV1DeviceID 1 set g_nPOV1ID 0 set g_nPOV2DeviceID 2 set g_nPOV2ID 0
-
Magnefic!
You are a tru friend to Falcon BMS friends!Your solution for me needeed a small editing to get me satisfided.
//
// Input stuffset g_nButtonsPerDevice 32
set g_nHotasPinkyShiftMagnitude 256
set g_nNumOfPOVs 2
set g_nPOV1DeviceID 1
set g_nPOV1ID 0
set g_nPOV2DeviceID 2
set g_nPOV2ID 0My REM :
set g_nButtonsPerDevice 32
set g_nHotasPinkyShiftMagnitude 256
rem set g_nNumOfPOVs 2
set g_nPOV1DeviceID 1
rem set g_nPOV1ID 0
set g_nPOV2DeviceID 2
rem set g_nPOV2ID 0Thank You!
-
If you’re using the Key File Editor I have a small improvement to allocate the DX number correctly. Sorry I don’t have rights to post a picture.
Obviously all credit to the creators for the tool…You need to unprotect the sheet and modify the calculation for DX number in the respective sheet for your controller.
For me with X55 :
D15 make value 128.
Cell F22 change formula to =IF(ISERROR(F20*$D$15-$D$15),“n/a”,F20*$D$15-$D$15)
Cell F82 change formula to =IF(ISERROR(F21*$D$15-$D$15),“n/a”,F21*$D$15-$D$15)Happy Hunting.
EDIT: Changes are only to your controller’s callback allocation sheet. Column F will need to be unhidden obviously.