X55 keyfile -BMS -Full DX Programmed
-
How would I edit it, since you can’t save it in the UI?
-
How would I edit it, since you can’t save it in the UI?
It is all much simpler then most think it is.
Open the key file with notepad and look at bottom section where all the magic is stored.
With someknowledge of DX programming you can also make the adjustmenst and keep you rudder attached.
Suggest you study the documentation of my keyfile and understand every word of it as a start.
Also do read the BMS keyfile manual and BMS keystrokes.pdf in docs section. -
I found this page a useful place to start as well: https://www.benchmarksims.org/forum/content.php?153-DirectX-Shifting-Facility
But personally I don’t need it anymore, as thanks to Snelle, I have a brilliant set of x55 mappings that I could get working in 10 minutes! (partly thanks also to my previous knowledge about stick/throttle ID’s and all the messing about I’d done with DX functions for my 4.32 keyfile) even my SLD switch and ministick now have a purpose
You sir, have saved me countless hours of headaches. Too bad I can only thank you once.
-
I’ve been continuing to fly with this profile for several months and am still loving it. I wanted to share some experience with it. I dran into a problem in a multiplayer flight a few weeks ago. During taxi I had to rapidly apply my wheelbrakes a few times due to unexpected deceleration from my flight lead. By the time I lined up on the runway my speedbrakes were slightly open (I apparently wasn’t giving the shift button enough time before pressing the wheelbrake button, and was instead just slightly opening the speedbrakes each time). I failed to recognized this and started my takeoff roll. I realized something was wrong, but by the time I had the speedbrakes retracted I was out of runway and crashed. Using the slider for speedbrakes is not ideal, as it doesn’t allow you to have fine control over opening / closing them which you need to AAR. I removed speedbrake open / close from the buttons H and I and rebound speedbrake open and close to forward and back on the upper throttle hat (the one labelled EWS) which originally would cycle countermeasure programs and modes. I removed the mode select from the hat as I don’t believe it is really on a HOTAS control in the jet, and I never found myself using it. This is also a similar location to the speedbrake switch in the jet. Now I have unshifted H bound to wheelbrake and unshifted I bound to trackIR recenter.
-Rabbit
-
@Rabbit: Though your setup seems perfectly reasonable, and is similar to what I was using in 4.32, isn’t Spdbrk open/close already bound unshifted to the two buttons on the front of the throttle? I’ve just used the slider since finding Snelle’s profile…
-
During taxi I had to rapidly apply my wheelbrakes a few times due to unexpected deceleration from my flight lead. By the time I lined up on the runway my speedbrakes were slightly open (I apparently wasn’t giving the shift button enough time before pressing the wheelbrake button, and was instead just slightly opening the speedbrakes each time).
-RabbitWith wheelbraking the nose dive is hard to miss imho, or when it does not occur u are not braking , anyway a cross check of the jet is mandetory before take off.
I agree that using buttons for a wheel brake is a significant trade off for not using feetrudder with brakes, but whatever button u use -including the feetrudder-the scenario remains the same.
At initial profiles the wheelbrake where located at shift/paddle, this would still be my first choice but unfortunately this gave throttle issues and I have no clue if that issue was solved in U1. -
hey bro, you still have x55 profile for bms 4331?
-
-
As a n00b, I am following the installation instructions 5.x, which are quite clear. I’m trying to do the ‘clean install’ to avoid any legacy issues.
I’ve uninstalled all Saitek/Mad Katz software. However, when I go to the Device Manager and try to uninstall the Programming Support, my system (WIN10, i5, 8GB, GTX760) hangs up. I can’t believe it takes over an hour to uninstall a small utility so I’ve had to turn it off and turn it back on again.
On re-starting, all programming support is yellow flagged but still there. They refuse to go.
I’ve re-installed the Rhino drivers (Rhino_7_0_55_13_x64_Drivers) and the programming software (Rhino_7_0_55_13_x64_Software & Smart Technology 7_0_27_13 64Bit) . I can load the profile onto the HOTAS through STT but BMS can’t see the key file (or any keyfiles). That part of BMS Setup on Controllers where the key files available used to be listed, is now blank.
What am I missing?
Update:
Found that if I disable the drivers first, then they can be uninstalled & deleted. Also ran CCleaner Registry Cleaner to remove traces.Back on track, but still no keyfiles!
Upodate 2:
I had removed the default key files into a backup directory, thinking that fewer is better. In practice, BMS seems to require these default files in the User/Config folder. As soon as I’d replaced them, all key files (including the Snelle one) were visible. -
Hi Moneil,
It shouldn’t be any problem assuming that your hardware X-55 is recognized in windows, in devices see the leds turning red when pressed?
next your Saitek is loaded in BMS correctly, choose the stick (not the throttle!)
Load the keyfile for BMS in controller setup,
that is all there is.
I don’t now what stuff you threw in the bin, but it is not a problem to have multiple keyfiles stored in the BMS directory, you can only chose one active. Leave it alone I suggest, just copy my kefile for BMS to it’s path.
If there is none showing up in BMS (controller setup) and your hardware is setup and functional I’m afraid you screwed up something in BMS therefore you are prone to and recommended for a clean install
Good luck. -
In regard to the upcoming Falcon Online event Battle for Sinai which will be flown with BMS 4.32 I want to point out that my keyfile (current v5.1) is for use with BMS 4.33. Using this version in 4.32 is not recommended!
I will post a 4.32 version within a few days.edit: Keyfile for BMS4.32 now downloadable first page or grab it here
-
Greetings Snelle
I am currently following your instructions for a clean install… In Device Manager/Programming Support I am attempting to delete all entries. Upon trying to delete the 1st entry, Programmable Hotkeys, the Device Uninstall box shows a green flowing bar, that appears stuck. Its been going for over 30 minutes.
Any idea’s?Edit: it continued all night… stopped uninstall process using Task Manager.
Win 10… latest updates -
The un-install instructions are Saitek’s, no credit for me
What happens if you install new drivers anyway, perhaps a different version?
Deleted the software via contral panel first before deleting via device manager?- clean the registry for errors: run cccleaner, choose registry and scan for issues.
If un-installing does not work and your system does not let you install new drivers you mightbe stuck here. Finding and deleting saitek’s drivers manually and cleaning your system for leftovers could possibly be your only choice.
Try unhooking all USB’s devices first befores deleting in device manager.
If you recently installed saitek’s/x-55 you could have a system restrore point, make a new one first!
Good luck. -
OMG! I think it ALL works! What an amazing job Snelle! Have to learn to fly all over again… but have been away for quite sometime, so won’t be that difficult.
I went thru the registry, deleting anything that said “Mad Catz”. Some would not delete, but pressed on thru. Then simply added the drivers and software… made the adjustments as per your advanced setting pic… and tried a quick landing TE… Everything including the cursor movements all worked well.
Thanks my friend… Again…GREAT job!Oh yes… also ran ccleaner several times prior to install… until no issues were found
-
Disregard.
I’m not a smart man.
-
Hi Snelle,
I have used your DX .key file before, all worked great. I have recently installed BMS 4.33_2 on SSD. I forgot to back up modded .key file I was using based on your V3 version.Now I have 4.33_2 installed, but also now have Crosswind V2 rudder pedals. My stick is device 2, throttle device 3. I’m presuming rudder pedals are device 1.
Don’t have any madcatz software installed.
Using standard drivers.
Joystick and throttle both work fine in DCS.
When I use V3 keyfile BMS crashes.
When I use V5 IDS version keyfile the stick is fine but not throttle.
When I changed throttle DX addresses to 65 to 94 it still doesn’t work.Does 4.33 Update 2 change anything?
Is it possible to change device numbers?Any advice you be appreciated, I’ve done alI i can remember but I’m missing something.
Thanks
Sent from my Nexus 7 using Tapatalk
-
I assume you are right on #2 & #3, assume you did check ID as explained in manual as it determines DX value needed in keyfile for device to work.
DCS and BMS work different, this keyfile is for BMS only.
obvious something is wrong indeed.
IDS assumes stick = #2, and throttle= #1… #1 is obvious in conflict with the rudder.
BMS DX#2=64-95. Basicly it should work, no raeson not to as I can see. what does not work and how did you test? send me (pm) copy of your DX work.
not for DX. -
I assume you are right on #2 & #3, assume you did check ID as explained in manual as it determines DX value needed in keyfile for device to work.
DCS and BMS work different, this keyfile is for BMS only.
obvious something is wrong indeed.
IDS assumes stick = #2, and throttle= #1… #1 is obvious in conflict with the rudder.
BMS DX#2=64-95. Basicly it should work, no raeson not to as I can see. what does not work and how did you test? send me (pm) copy of your DX work.
not for DX.
No.
Hi Snelle,
Thanks for the prompt reply. I’m too poorly to work on PC right now, but I checked thd DX addresses but pressing button 1 on joystick and throttle in the BMS UI as per your documentation.
I only mention DCS to show the joystick and throttle work OK in WinX.
When I feel better I’ll take up your offer of forwarding the keyfile to you for you to check when you have time. I did manage to program gear up/down toggle (SW1) flaps full (SW4) and flaps null (SW3) from the BMS UI. Those changes show in keyfile with ‘8’ in the code line as expected and all works fine.
Hopefully I’ll be in contact with you soon.
Thanks Richard
Sent from my Nexus 7 using Tapatalk
-
Happy New Year and that all of your dreams may come true. :bdance:
The download counter of my profiles is about to hit the 1.000 mark in total and that proofs me right spending time for making this BMS X-55 profile.
Cheers, and all the best for 2017.
-
Snelle, in case you missed it:
Make sure, that in the file “DeviceSorting.txt” under folder :\Falcon BMS 4.33\User\Config :
- your STICK IS in FIRST line
- your THRUTTLE IS in SECOND line
- and pedals (if used) in THIRD line
example:
{22150738-0000-0000-0000-504944564944} "Saitek Pro Flight X-55 Rhino Stick" {A2150738-0000-0000-0000-504944564944} "Saitek Pro Flight X-55 Rhino Throttle" {910E04D8-0000-0000-0000-504944564944} "Simped F-16 Plus"
This ensures, that BMS DirectX numbers are aligned IN ORDER for BMS, regardless what IDs are given in (by) Windows:
- Stick is 0-31
- Thruttle is 32-64
- Rest devices (if buttons are on them)
Windows can be “headache” in how it gives IDs to devices and there is only one tool i know off, what can swap windows-device IDs.
The “DeviceSorting” text file is the easier way and no need to make the same “.keystrokes” file with different IDs multiple times in order to share them.