X55 keyfile -BMS -Full DX Programmed
-
Thank you for the quick response. I will try it out this evening
-
I changed my previous answer because it is not correct .
Based on the log file of driver install i conclude that the driver installer is not determining device order.
So Windows itself will determine the device order imho and in registry it shows clearly where the devices are.
Are your joystick 1 and 2 are opposite of the picture? If so then I would try to uninstall the drivers and deleting the keys out of the registry and start your install over from the beginning.It’s trial and error as I’m searching for answers to on this subject.
Be careful and make backup! -
This post is deleted! -
Ok, I haven’t had a chance to play yet but it looks like we may have it working now. I deleted all drivers, deleted the joystick and throttle registry folders and did a completely clean install after a reboot. plugged in stick first and then throttle. At least the game UI seems to be recognizing the correct controllers now. I can try your other suggestion if this does not actually fix it but I think it did. Thanks again for the help
-
Interested in if your registry was swapped regarding joy 1 and 2 compared to mine as shown in pic ?
-
mine were reverse of the image you provided.
-
Then you will be good,
Cheers have fun!
-
Thanks again, great key profile
-
well, I thought we had it beat. for what ever reason after a few days, the id’s in the registry reverted to where they were before. Backwards. I am trying to figure out what happened. i will let you know if I can sort it out
-
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.