X55 keyfile -BMS -Full DX Programmed
-
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. -
A.S. thanks for the heads up, it will make life easier for those affected with swapped ID.
In the BMS manual page 50 this subject is explained in detail.
AS allways the same remains to be said :rtfm:Documentation is updated and the obsolete keyfiles are removed from package.
Download from first page to have the latest package, the Keyfile itself remains identical to v5.1. -
Hey Snelle,
I installed your profile and it works other than one weird thing. When I press the pickle or weapon step button they don’t work I have to hold them for a few seconds then they work. Is this normal?
Thanks
-
Hey Snelle,
I installed your profile and it works other than one weird thing. When I press the pickle or weapon step button they don’t work I have to hold them for a few seconds then they work. Is this normal?
Thanks
Yes that is normal and it depends of the vipers active weapon as well as the mastermode.
You can find relevant information in the //Docs/ dash34 manual e.g. HOC (page21), HOTAS functions (pages 148 >) and in the Weapon Delivery Procedures section (pages 206 >).
Cheers. -
I may sound stupid but i downloaded the 4.32 file i extracted i look to the read me and I cant figure where i need to drop those 2 files anyone can help me out on this please?!
-
You downloaded the keyfile version for BMS4.32, sure? In BMS 4.33 it works excactly the same so refer to the documention also available from first page.
WARNING: Don’t use a 4.32 complient keyfile in BMS 4.33 and v.v. ! -
Hi Snelle, I have a random issue with BMS and I am not sure whether it is your keyfile (using X55-BMS4.33-Snelle-5.5-NS, no sound) or BMS (4.33 U3) that is causing the issue. I’ve noticed that in the Tactical Engagement LGB tutorial (non ramp start), the laser will permanently lase when the following is done:
- Manually lase for a brief amount of time (Trigger + Button D on the x55 with this profile). Stop lasing.
- Continue flight. Drop LGB using CCRP release.
- At this point, regardless of the LASER ST TIME setting, the laser will begin firing as soon as the pickle button is held, and will continue firing indefinitely after pickle button release (Button A on x55).
The laser will never stop firing at this point. Even turning the laser on/off switch will result in the laser continuing firing as soon as it is back online.
If step 1 (a brief manual lase) is omitted, the laser functions as intended, doing the pre-lase when pickling, stopping lasing, and resuming lasing once the LGB is the set amount of seconds before computed impact (LASER ST TIME).
Not sure what the cause of this issue is, hopping you can help out?
-
I have no clue why the Laser acts wrong. I tested myself and once I noticed that the LAser started emitting after 36 seconds where 20 was the ST preset, and stopped after impact.
I noticed though a strange behaviour after copying the X55…NS keyfile to the config directory in BMS as some keys (in pit) where acting different then was planned by me, weird but so true it is really unbelievable ,e.g. pinkyshift/zoom became msl step. After removing several other keyfiles from //config dir with nearly identical names this issue was solved! BMS even came to a protesting crash from the this removal, so apparantly they where still in use somehow.
If you find the Key is not acting normal as it should I suggest to remove similar named keyfiles from // config, i.e. if there are any.
Hope this helps. -
Hello Snelle, really new to BMS (played Falcon AF back in the day). I’ve read through the entire thread and the documentation. I may have missed it, but is there a dummy proof noob walkthrough on how to do the registry fix (click this, then this)? I’ve never worked within the registry before and I don’t know if it is as simple as clicking on the regfix file or something else. I’ve been hesitant to mess with anything even with a backup. Everything else works great, thanks for this.