X55 keyfile -BMS -Full DX Programmed
-
Swapped ID version is available on the first page for download.
-
wow, thanks again
-
This is outstanding. I never took the time to figure out DX bindings and it works great without having to mess with SST. This is a great way to get back into BMS with 4.33.
I upgraded to the X-55 from the X-52 pro and find myself missing the 2 stage trigger (both here in BMS and especially in DCS-A10C). The ability to manually fire the laser using the first trigger detente is useful. Could you add shift + trigger = first stage trigger?
Thanks again,
Rabbit
-
Could you add shift + trigger = first stage trigger?
Good call!
Keyfiles will be updated soon!
-
Version 5.0 is available at first page.
Added: IDS version, Keyfile for an ID Swapped situation in windows (Stick=#2 / Throttle=#1).
Added: Trigger Firstdetent.
Changed documentation, added artwork xray x55 and Dutch Demo Viper. -
Excellent work, and thanks for sharing and updating.
After months of searching to find a way to get the X55 mini mouse on the throttle to work, I can verify too that your registry edits worked. I was able see new X and Y axis in the BMS Advanced Controller page and get it to set for FCR cursor commands. Your documentation was very helpful in explaining the process.
Unfortunately, I have the same issue that many others have posted elsewhere on the web about erratic movement with the mini mouse. Typically the first command is recognized, but any movement after that randomly goes in different directions. So if I move the mini mouse up and then right, I may see the FCR cursor move up and then down……or up and then diagonal.
This is the same erratic movement I see in the HUD software when I tried the ‘bands’ setup, as well as in the windows calibration window. So I’ll assume this is a hardware or driver issue as many other posts on the web indicate. If anyone knows of how to overcome this I would be interested. I’ve reverted back to my throttle thumb 4 way for cursor movement, which does work just fine using the DX commands, and is a bit more ergonomic for my thumb position.
-
Unfortunately, I have the same issue that many others have posted elsewhere on the web about erratic movement with the mini mouse. I’ve reverted back to my throttle thumb 4 way for cursor movement, which does work just fine using the DX commands, and is a bit more ergonomic for my thumb position.
Actually I do not now much about the erratic mouse movement, but it sounds indeed like a hardware issue. One question though, was your mouse erratic all the time or only since the REG update?
I can’t imagine that you try an mouse axis x/y in combo with a HUD profile……but make sure you are not doubling the commands.
All together it is sure is a good reason for me to keep the v3.0 of my DX keyfile alive as it has mouse support on the H3 of the throttle. I will look into updating it conform the current 5.0 version. -
One question though, was your mouse erratic all the time or only since the REG update?
My issue with the erratic mouse has always been there and not related to your registry key suggestion. I also do not run the HUD software at all due to other issues I’ve had with it in the past, so it would not have been a conflict. Since I see the erratic issue with the Saitek software and without it on the windows controller calibration test screen, I have to assume it’s hardware of driver until someone can suggested another idea. Thanks for your reply.
-
This post is deleted! -
Hi,
I’m starting to get into BMS and tried to install your profile yesterday.
The buttons work -for most of them, the Throttle TGL 3 and 4 don’t- but I’m having huge issue with the axis configuration.
First loading I had “Roll/Pitch axis deadzone” bound to the X and Y throttle axis. And as I tried to un-bind them, I stumbled upon 2 issues :
- I can’t just put “keyboard” in the “Throttle - Advanced - Roll/Pitch axis deadzone” option to get rid of the deadzone use with the Throttle. For some reason there needs to be something there. I settled for “Move Up/Down | Left/Right Throttle” as it seems to be assigned to no axis/rotary on the X55 throttle…
- When in game (tried with Landing training mission), the first controller axis I move will be the only one I’m able to use. If I try to throttle up/down, I’m unable to move the aircraft with the joystick, and if I pitch/roll the aircraft, I’m unable to throttle up or down. Buttons all still work though. I can control the aircraft + press throttle’s buttons and vice-versa.
Any idea what’s the issue there?
-
Hi,
I’m starting to get into BMS and tried to install your profile yesterday.
The buttons work -for most of them, the Throttle TGL 3 and 4 don’t- but I’m having huge issue with the axis configuration.
First loading I had “Roll/Pitch axis deadzone” bound to the X and Y throttle axis. And as I tried to un-bind them, I stumbled upon 2 issues :
- I can’t just put “keyboard” in the “Throttle - Advanced - Roll/Pitch axis deadzone” option to get rid of the deadzone use with the Throttle. For some reason there needs to be something there. I settled for “Move Up/Down | Left/Right Throttle” as it seems to be assigned to no axis/rotary on the X55 throttle…
- When in game (tried with Landing training mission), the first controller axis I move will be the only one I’m able to use. If I try to throttle up/down, I’m unable to move the aircraft with the joystick, and if I pitch/roll the aircraft, I’m unable to throttle up or down. Buttons all still work though. I can control the aircraft + press throttle’s buttons and vice-versa.
Any idea what’s the issue there?
-Is everything ok according to windows controller stup and calibrated ? All buttons esp TGL3-4 lite up?
-No other Saitek profiles active?
-reload the Keyfile (fresh one), and do NOT edit or save anything in the UI.
TGL3 and TGL4 should work now just like the rest, these are the AP switches, you should see them move by INC or DEC, if not something else coulde be the reason.
-Go to the controllers in BMS en load STICK only, do not try to setup the throttle.FYI: axis are BMS/ hardware related and have nothing to do with DX key programming. If you can not figure it out consider a re-install of drivers HOTAS and or BMS and take it one step at the time. Make sure to use latest Saitek drivers and software.
-
-
Controllers work fine in DCS everything is calibrated. TGL3-4 are pressed but don’t trigger anything (AP DEC/INC don’t show up like it should when pressing a keybind corresponding to something).
-
I haven’t installed the Saitek profile for the nipple/slider (yet). Do they need to be active? I’ll try profiling it anyway just to be sure.
-I’m using the IDS one. I’ll try re-doing the setup from scratch when I get home and will post results here.
Also, what do you mean by not saving anything? Just the keybinds or also the axis? As I understand it they’re independant from your keyfile, and I’d still need to edit the axis (default when keyfile was loaded was Throttle up/down controlled Pitch+Roll and RTY 1 controlled Rudder).
-
-
- I haven’t installed the Saitek profile for the nipple/slider (yet). Do they need to be active? I’ll try profiling it anyway just to be sure.
Also, what do you mean by not saving anything? Just the keybinds or also the axis? As I understand it they’re independant from your keyfile, and I’d still need to edit the axis (default when keyfile was loaded was Throttle up/down controlled Pitch+Roll and RTY 1 controlled Rudder).
REGFIX is not manditory, but strongly advised and I only see advantage of mini stick as x/y.
If you do not want to use the ministick use v 3.0., it is downloadable main page.Saving: not any keybinds in controller UI, just press ok after loading the keyfile. Setup the axis as normal.
The IDS version is new, this is the first feedback on that one so I will check it out, but having said that: I can throw in the keyfile anything I want to, but then the axis in BSM should still work as normal.
-no other profiles active, blank nada zero nichts??
-in UI what message do you get from toggling TGL 3/4 ?? -
I may have had the default (empty) Saitek profile loaded when I started BMS or loaded the keyfile for the first time. Cleared it after messing with stuff. Will try again while being assured there’s none when starting BMS.
I’ll update tonight with the exact event when toggling TGL3/4. I know it still displayed the same previous keybind I input just before (typically it was Radar Stby from the TGL2 I had just tested), but I’m not 100% confident it changed the whole message or only the first part.
-
I may have had the default (empty) Saitek profile loaded when I started BMS or loaded the keyfile for the first time. Cleared it after messing with stuff. Will try again while being assured there’s none when starting BMS.
I’ll update tonight with the exact event when toggling TGL3/4. I know it still displayed the same previous keybind I input just before (typically it was Radar Stby from the TGL2 I had just tested), but I’m not 100% confident it changed the whole message or only the first part.
The “default” or “standard” is empty on creation but after that…… could have been programmed or saved by accident
-
Ok about the TGL3/4 : Input 16/17 and 18/19 is shown when toggling them, but the associated bind doesn’t show up underneath (either “No function assigned” or it says what the previously bound buttons was bound to).
No madcatz profile selected.
I still have the X/Y Throttle axis bound to Pitch Axis Deadzone / Roll Axis Deadzone. Rudder on Z Axis and Throttle on “Move Up/Down”. I’ll try changing the axis and pressing “OK”.
Edit: Toggles DO work in-game though. They properly change the AP switches.
Edit2: Found the issue with the axis. I loaded a mission with the Throttle selected in the BMS controller, didn’t touch a thing, and the stick wasn’t responding. Did the opposite, with joystick selected in the dropdown menu of the controllers, and only had the stick working … Seems like it’s picking either one or the other depending on the one selected in the menus wtf
Edit 3 : OK it’s all working now… I ended up selecting the joystick as controller in the menu and putting the Y Axis of the Throttle as throttle control… Sweet jesus that game isn’t user-friendly at all -
Sweet jesus that game isn’t user-friendly at all
Generally the mother of all FUC*ups come from bad reading habbits. :rtfm:
Cheers and have a good one.
-
I haven’t been able to get the MRM/DF override function to work. The rest of the shifted functions are just fine (including the trigger first detent -thanks!) I think the throttle picks up the “buttons” from the rotating wheel in an unusual way - the cancel appears to work if I hold the wheel between the “clicks” (there are subtle clicks you can feel when you rotate it), but then you’re right back into DF or MRM once you let go and it lands on a click. I dipped my toe into DX editing and changed the Snowplow key to DF/MRM override and that seems to work well.
Again, absolutely outstanding work. Your keyfiles should be included with the installs.
'Rabbit
-
I haven’t been able to get the MRM/DF override function to work. The rest of the shifted functions are just fine (including the trigger first detent -thanks!) I think the throttle picks up the “buttons” from the rotating wheel in an unusual way - the cancel appears to work if I hold the wheel between the “clicks” (there are subtle clicks you can feel when you rotate it), but then you’re right back into DF or MRM once you let go and it lands on a click. I dipped my toe into DX editing and changed the Snowplow key to DF/MRM override and that seems to work well.
Again, absolutely outstanding work. Your keyfiles should be included with the installs.
'Rabbit
Perhaps still some Saitek profile active, try right clickt SST and “erase” to make sure that all is out of memory, else it could be a hardware failure/ conflict. Try pulling out all USB and re-install as per documentation.
-
Pimped up the documentation for version 5.0. Download PDF