X55 disable mode shifting
-
Hi
I’ve been using the X-55’s mode dial for SimICPNav, SimICPAA, SimICPAG (via custom keyboard shortcuts mapped in .key) which gives me a nicely visible mode i’m configured for.
Now, in the H.U.D. software it seems that you HAVE to assign a mode shift-button for Mode2 and Mode3 which to me means I lose two switches (please correct me if I’m wrong). I don’t have a need for shifts at the moment YMMV
I’ve been experimenting with a way around this by opening the .pr0 file and changing the mode’s buttoncombo to some fake value, i.e.
... [shift=c5d5facc-3147-4209-8bee-ea0864f09c02 fallback=346dbae3-9684-4b7d-9943-887e7a32d02c name=Mode2 [assignments ... [selectionset [buttoncombo [buttonhid=[B][color]0x0009FFFF[/color]]]]]]] [shift=952c5f2c-9187-4327-9132-32ea022f0d6d fallback=346dbae3-9684-4b7d-9943-887e7a32d02c name=Mode3 [assignments ... [selectionset [buttoncombo [buttonhid=[B][color]0x0009FFFF[/color]]]]]]] ...
This makes all buttons/switches/toggles available (no more shifting of course) and reading/storing the profile as well as editing in H.U.D. seems to work fine so far
just FYI, in case someone else has been pondering the same angle
Cheers
b4dshot -
I was using the x52pro before (+ profiler software).
With the x-55 i would recommend using direct DX assingments for BMS instead of using the HUD software.How to infos you can find in your install under: :\Falcon BMS 4.32\User\Joystick\Generic\Kolbe
Example (with Pinky SHIFT Tap and Hold and BMS ITSELF supports that function - so no need for external “shifting”)
Keystroke file code for picture above (mind you if your stick is device 2 under windows - if it is device 1 you just need to lower the values accordingly)
The 0XFFFFFFFF lines are not nessary and only there so the game can “display” the right calls if buttons are pressed in the UI.SimTransmitCom1 -1 0 0XFFFFFFFF 0 0 0 0 "TQS: COMMS Switch Up - UHF" SimTransmitCom1 91 8 -2 0 0x0 0 SimTransmitCom2 -1 0 0XFFFFFFFF 0 0 0 0 "TQS: COMMS Switch Down - VHF" SimTransmitCom2 92 8 -2 0 0x0 0 SimCommsSwitchLeft -1 0 0XFFFFFFFF 0 0 0 0 "TQS: COMMS Switch Left - IFF OUT" SimCommsSwitchLeft 347 8 -2 0 0x0 0 SimCommsSwitchRight -1 0 0XFFFFFFFF 0 0 0 0 "TQS: COMMS Switch Right - IFF IN" SimCommsSwitchRight 348 8 -2 0 0x0 0 SimToggleMissileCage -1 0 0XFFFFFFFF 0 0 0 0 "TQS: MAN RANGE Knob - UNCAGE" SimToggleMissileCage 65 8 -2 0 0x0 0 SimSelectSRMOverride -1 0 0XFFFFFFFF 0 0 0 0 "TQS: DOGFIGHT Switch - DF Override" SimSelectSRMOverride 94 8 -2 0 0x0 0 SimSelectMRMOverride -1 0 0XFFFFFFFF 0 0 0 0 "TQS: DOGFIGHT Switch - MRM Override" SimSelectMRMOverride 93 8 -2 0 0x0 0 SimDeselectOverride -1 0 0XFFFFFFFF 0 0 0 0 "TQS: DOGFIGHT Switch - MRM/DF Cancel" SimDeselectOverride 323 8 -2 0 0x0 0 AFBrakesOut -1 0 0XFFFFFFFF 0 0 0 0 "TQS: SPD BREAK Switch - Open" AFBrakesOut 68 8 -2 0 0x0 0 AFBrakesIn -1 0 0XFFFFFFFF 0 0 0 0 "TQS: SPD BREAK Switch - Close" AFBrakesIn 67 8 -2 0 0x0 0 SimCursorUp -1 0 0XFFFFFFFF 0 0 0 0 "TQS: RDR CURSOR - Up" SimCursorUp 87 8 -2 0 0x0 0 SimCursorDown -1 0 0XFFFFFFFF 0 0 0 0 "TQS: RDR CURSOR - Down" SimCursorDown 89 8 -2 0 0x0 0 SimCursorLeft -1 0 0XFFFFFFFF 0 0 0 0 "TQS: RDR CURSOR - Left" SimCursorLeft 90 8 -2 0 0x0 0 SimCursorRight -1 0 0XFFFFFFFF 0 0 0 0 "TQS: RDR CURSOR - Right" SimCursorRight 88 8 -2 0 0x0 0 SimCursorEnable -1 0 0XFFFFFFFF 0 0 0 0 "TQS: RDR CURSOR - Cursor Enable" SimCursorEnable 64 8 -2 0 0x0 0 SimRadarCursorZero -1 0 0XFFFFFFFF 0 0 0 0 "TQS: RDR CURSOR - Cursor Zero" SimRadarCursorZero 320 8 -2 0 0x0 0 SimToggleMissileSpotScan -1 0 0XFFFFFFFF 0 0 0 0 "Wpn-Sidewinder Spot/Scan" SimToggleMissileSpotScan 321 8 -2 0 0x0 0 SimDropProgrammed -1 0 0XFFFFFFFF 0 0 0 0 "HOTAS-Run Countermeasures Program"" SimDropProgrammed 66 8 -2 0 0x0 0 SimEWSProgInc -1 0 0XFFFFFFFF 0 0 0 0 "CMDS: PRGM Knob - Toggle Up" SimEWSProgInc 84 8 -2 0 0x0 0 SimEWSProgDec -1 0 0XFFFFFFFF 0 0 0 0 "CMDS: PRGM Knob - Toggle Down" SimEWSProgDec 86 8 -2 0 0x0 0 SimEWSPGMInc -1 0 0XFFFFFFFF 0 0 0 0 "CMDS: MODE Knob - Toggle Up" SimEWSPGMInc 83 8 -2 0 0x0 0 SimEWSPGMDec -1 0 0XFFFFFFFF 0 0 0 0 "CMDS: MODE Knob - Toggle Down" SimEWSPGMDec 85 8 -2 0 0x0 0 SimECMOn -1 0 0XFFFFFFFF 0 0 0 0 "HOTAS-ECM on - Consent Toggle" SimECMOn 322 8 -2 0 0x0 0 AFGearUp -1 0 0XFFFFFFFF 0 0 0 0 "GEAR: LG Handle - UP" AFGearUp 73 8 -2 0 0x0 0 AFGearDown -1 0 0XFFFFFFFF 0 0 0 0 "GEAR: LG Handle - DN" AFGearDown 74 8 -2 0 0x0 0 SimMPO -1 0 0XFFFFFFFF 0 0 0 0 "MPO: MANUAL PITCH Switch - Hold" SimMPO 75 8 -2 0 0x0 0 ToggleNVGMode -1 0 0XFFFFFFFF 0 0 0 0 "CKPIT: Nightvision - Toggle" ToggleNVGMode 79 8 -2 0 0x0 0 SimRadarStandby -1 0 0XFFFFFFFF 0 0 0 0 "Radar-standby" SimRadarStandby 77 8 -2 0 0x0 0 ToggleSmoke -1 0 0XFFFFFFFF 0 0 0 0 "CKPIT: Smoke - Toggle" ToggleSmoke 70 8 -2 0 0x0 0 SimNextAAWeapon -1 0 0XFFFFFFFF 0 0 0 0 "Wpn-A to A cycle" SimNextAAWeapon 298 8 -2 0 0x0 0 SimNextAGWeapon -1 0 0XFFFFFFFF 0 0 0 0 "Wpn-A to G cycle" SimNextAGWeapon 300 8 -2 0 0x0 0 SimTMSUp -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TMS Up" SimTMSUp 0 -1 -3 0 0x0 0 SimTMSDown -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TMS Down" SimTMSDown 0 -1 -3 4 0x0 0 SimTMSLeft -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TMS Left" SimTMSLeft 0 -1 -3 6 0x0 0 SimTMSRight -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TMS Right" SimTMSRight 0 -1 -3 2 0x0 0 SimDMSUp -1 0 0XFFFFFFFF 0 0 0 0 "STICK: DMS Up" SimDMSUp 42 8 -2 0 0x0 0 SimDMSDown -1 0 0XFFFFFFFF 0 0 0 0 "STICK: DMS Down" SimDMSDown 44 8 -2 0 0x0 0 SimDMSLeft -1 0 0XFFFFFFFF 0 0 0 0 "STICK: DMS Left" SimDMSLeft 45 8 -2 0 0x0 0 SimDMSRight -1 0 0XFFFFFFFF 0 0 0 0 "STICK: DMS Right" SimDMSRight 43 8 -2 0 0x0 0 AFElevatorTrimDown -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TRIM Nose Up" AFElevatorTrimDown 40 8 -2 0 0x0 0 AFElevatorTrimUp -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TRIM Nose Down" AFElevatorTrimUp 38 8 -2 0 0x0 0 AFAileronTrimLeft -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TRIM Roll Left" AFAileronTrimLeft 41 8 -2 0 0x0 0 AFAileronTrimRight -1 0 0XFFFFFFFF 0 0 0 0 "STICK: TRIM Roll Right" AFAileronTrimRight 39 8 -2 0 0x0 0 SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 0 "STICK: SECOND TRIGGER DETENT" SimTriggerSecondDetent 32 8 -2 0 0x0 0 SimPickle -1 0 0XFFFFFFFF 0 0 0 0 "STICK: WEAPON RELEASE (Pickle)" SimPickle 33 8 -2 0 0x0 0 SimMissileStep -1 0 0XFFFFFFFF 0 0 0 0 "STICK: NWS A/R DISC MSL STEP SWITCH" SimMissileStep 34 8 -2 0 0x0 0 SimHotasPinkyShift -1 0 0XFFFFFFFF 0 0 0 0 "STICK: PINKY SHIFT" SimHotasPinkyShift 36 8 -2 0 0x0 0 SimHotasPinkyShift 292 8 -2 0 0x0 0 SimRadarAzimuthScanChange -1 0 0XFFFFFFFF 0 0 0 0 "Radar-submodes/azimuth" SimRadarAzimuthScanChange 2 -1 -3 0 0x0 0 SimRadarBarScanChange -1 0 0XFFFFFFFF 0 0 0 0 "Radar Bar-Scan" SimRadarBarScanChange 2 -1 -3 4 0x0 0 SimFCCSubModeStep -1 0 0XFFFFFFFF 0 0 0 0 "Sim-FCC submodes" SimFCCSubModeStep 35 8 -2 0 0x0 0 AFResetTrim -1 0 0XFFFFFFFF 0 0 0 0 "CKPIT: Trim-Reset (Change here)" AFResetTrim 291 8 -2 0 0x0 0 SimRadarRangeStepDown -1 0 0XFFFFFFFF 0 0 0 0 "Radar-range decrease" SimRadarRangeStepDown 2 -1 -3 2 0x0 0 SimRadarRangeStepUp -1 0 0XFFFFFFFF 0 0 0 0 "Radar-range increase" SimRadarRangeStepUp 2 -1 -3 6 0x0 0 SimWheelBrakes -1 0 0XFFFFFFFF 0 0 0 0 "CKPIT: Wheel brakes - Hold" SimWheelBrakes 37 8 -2 0 0x0 0
Also get the latest driver: 7_0_32_81 (or higher if available meanwhile), because it has the “Calibration” option, which the first release has not.
From here: http://www.saitek.de/down/drivers.php -
i need to try learning to use pinky direct x for shifting within BMS.
-
Yeah, definitely, directx and shifting within BMS seems preferrable. My problem is that the mode button (position 2+3) and the speed brake toggle/slider don’t seem to be sensed as directx buttons at all, maybe that’s a problem with using Saitek’s H.U.D. in the first place?
Cheers -
i need to try learning to use pinky direct x for shifting within BMS.
Hit me up on TS and I can walk you through it. I think you’ll find that you can move 95+% of your commands to DirectX and immensely simplify your Saitek Profile.
Yeah, definitely, directx and shifting within BMS seems preferrable. My problem is that the mode button (position 2+3) and the speed brake toggle/slider don’t seem to be sensed as directx buttons at all, maybe that’s a problem with using Saitek’s H.U.D. in the first place?
CheersBMS has a limit on the number of recognized buttons per controller. I think it’s 32, but don’t hold me to that. On the X52 Pro there are a handful of buttons/switches/knobs that BMS does not ‘see’.
-
Hit me up on TS and I can walk you through it. I think you’ll find that you can move 95+% of your commands to DirectX and immensely simplify your Saitek Profile.
BMS has a limit on the number of recognized buttons per controller. I think it’s 32, but don’t hold me to that. On the X52 Pro there are a handful of buttons/switches/knobs that BMS does not ‘see’.
yeah ive moved as much as i can to direct x already.
the things i have left as SST-dependent are:
-radar cursor (as BMS wont see the mouse nub)
-speed brakes (i want them on the slider)
-trackir center (has to be a macro as far as i can tell)
-trim (mode 3 of the DMS hat)
-macro’d commands such as cat i /iii toggle, parking brakeif i could get as many of those from “mode + pinky” SST shift to BMS “pinky hold” shift, that would be glorious.
and yeah, i noticed the other day that for some reason it was picking up mode selector 1 position as a button (unexpectedly and undesirably) and not 2 and 3 positions. couldnt figure out how to clear/“unsee” the button, so i assigned it to ICP back so that it wouldnt interfere with anything.
-
TrackIR ReCenter =
RecenterTrackIR -1 0 0X3B 1 0 0 1 “Recenter TrackIR”
DX: RecenterTrackIR [DXButton#} -1 -2 0 0x0 0, for example shifted for me: RecenterTrackIR 258 -1 -2 0 0x0 0
-
i had tried assigning the button on my stick for center (assigned shift + F1 in SST) to that funtion in BMS controller screen, and it never seemed to work. I’ll have to mess with it some more
i really need to read up on the actual DX numbered commands shown here. hard to apply focus to it. brain sees numbers and code and goes “nope nope nope!”. bad compsci memories.
-
Y0UNGBL00D,
How do you have the brake mapped to the slider? I went into the Saitek software, mapped the slider as a button, and assigned the “B” key to it (the key to toggle airbrakes in Kolbe’s keyboard layout). When I go to test it even in the Saitek software, though, the slider doesn’t do anything, nor does it in BMS.
My software only allows me to set up the slider as a single button, rather than two (i.e., one that’s detected when it’s slid to the left and one detected when it’s slid to the right). Is this how you have yours set up too? How did you get yours set up so that the slider actually works? Thanks!
-
i downloaded (and have since heavilly modified) hard-deck’s X52 profile, and the way it is set up is timed macros set to percentage bands:
slider at 0-8% = v v v v v v v v (v held for 6 seconds, the time it takes to close breaks from full open)
slider at 9-91% = does nothing
slider at 92-100% = b b b b b b b (for however many seconds it takes to open brakes) -
i had tried assigning the button on my stick for center (assigned shift + F1 in SST) to that funtion in BMS controller screen, and it never seemed to work. I’ll have to mess with it some more
i really need to read up on the actual DX numbered commands shown here. hard to apply focus to it. brain sees numbers and code and goes “nope nope nope!”. bad compsci memories.
The tools to build a DX profile are included in to the BMS Docs. I’ll show you where and how to build the profile. Kolbe set it up so it’s mostly automated. You basically just select the functions you want.
-
righteous. i knew that stuff was in there, but i couldnt make heads or tails of it last i looked. which was admittedly probably during an SST-induced rage
-
How do you have the brake mapped to the slider?
While I haven’t mapped it to a slider I have mapped it to my TGL1 switch using an Advanced Command in the X-55 software. I like to be able to open and close the brake in increments. As an example for closing the air brake I have put the Ctrl B in the “Press” box for TGL 1 Up. I found it won’t work unless you highlight and delete the released keys. I’ve done the same for quite a few commands and for the most part it works. (Still having problems with assigning pitch and roll trim)
Hope that’s useful.
-
@A.S:
I was using the x52pro before (+ profiler software).
With the x-55 i would recommend using direct DX assingments for BMS instead of using the HUD software.How to infos you can find in your install under: :\Falcon BMS 4.32\User\Joystick\Generic\Kolbe
Hello,
I studied the BMS keymap from the adress from my Falcon , and because I am a rookie put a question : what means OTW ?
Regards,
Vladalex