Grounded Thanks to Windows 10
-
I found that although Win 10 reordered my devices, they remained consistently in the same new order. Therefore by reassigning the DX numbers in the key file one time to reflect the new order, I had no further problems with devices. OK, sure it’s a PIA.
-
Goto your Windows Control Panel and right click on the joysticks and in order of desired precedence select remove device.
Do it in the order you wish for the joysticks to order as they will automatically reinstall if they are not unplugged when you click remove device. They will then be in the correct order and you won’t have to change your DX ordering in your key file.
Sometimes Windows reorders the devices after restarts or after it is shut down. It’s a common issue I have to reorder from time to time when Windows does this to keep my key file settings.
-
Goto your Windows Control Panel and right click on the joysticks and in order of desired precedence select remove device.
Do it in the order you wish for the joysticks to order as they will automatically reinstall if they are not unplugged when you click remove device. They will then be in the correct order and you won’t have to change your DX ordering in your key file.
Sometimes Windows reorders the devices after restarts or after it is shut down. It’s a common issue I have to reorder from time to time when Windows does this to keep my key file settings.
When I tried this procedure, Win 10 re-ordered the devices to its own liking at the next PC boot. I gave up and edited the key file.
-
What order should they be in?
Mine look like this?
ps. how to edit the key file for a key file noob. I’m using notepad++ All I can see is the “Flight Stick” section with a couple of settings in. Will go for a forum hunt.
-
All you need to know is in your …\Falcon BMS 4.33\Docs\Key Files & Input\ folder.
-
There’s no right device order intrinsically, just one which matches your key file. Device one gets buttons 1-32, device 2 buttons 33-64 and so on. Remember that in the keyfile, button 1 is called “0” and button 2 is called “1” and so on.
The button IDs in the keyfile are explained in the manual but simply they are the first number after the callback.
-
There aren’t even any references to any stick functions in Muds key file that I can see, (or In the BMS UI), other then the pinky switch and paddle. Nothing for TMS, DMS, trigger, CMS. Creating a keyfile from scratch would be OTT for this part timer
EDIT I found the “5.11 Flight stick” section in the keyfile with 24 commands there but only 3 show up as assignable In the BMS UI.
-
I think you can use the Excel keyfile editor to add DX callbacks to the key file, but I just do int manually. Attached are the DX callbacks for my Cougar MFD’s and HOTAS. I think this is also explained in the BMS Manual.Keep in mind that DX number groups of 32 correspond to the order listed by Windows: Device 1 = DX 0-31. Second device is DX 32-63, etc. Just edit as needed and add the text to the end of your .key file.
-
I think you can use the Excel keyfile editor to add DX callbacks to the key file, but I just do int manually. Attached are the DX callbacks for my Cougar MFD’s and HOTAS. I think this is also explained in the BMS Manual.Keep in mind that DX number groups of 32 correspond to the order listed by Windows: Device 1 = DX 0-31. Second device is DX 32-63, etc. Just edit as needed and add the text to the end of your .key file.
Hi! How about shifted layer? What do I have to change? Mine is first device is Saitech rudder. The second device is Hotas Cougar.
-
Do not confuse (virtual) windows device DX buttons with physical HOTAS buttons. The .key file assigns windows device DX buttons to specific callbacks (i.e. functions) in the sim. Assign DX buttons to a HOTAS physical button shifted layer the same way you would assign any other button on your HOTAS. So you can assign your HOTAS physical button 3 to DX3 and HOTAS shifted button 3 to DX4. HOTAS button 3 and shifted button 3 will then perform in the sim whatever functions you assigned DX3 and DX4 to in the .key file. If Cougar is second listed device windows will by default assign its physical buttons to DX buttons in the range 32-63. These default assignments can probably be altered by the Saitek HOTAS software.
-
I switched to Morphine’s’ profile and the stick works but now the throttle is all messed up. I will persevere. I may just manually setup the throttle. I must say, I never had this hassle in 4.32 / win7.
-
I switched to Morphine’s’ profile and the stick works but now the throttle is all messed up. I will persevere. I may just manually setup the throttle. I must say, I never had this hassle in 4.32 / win7.
Nobody did. Thank Micro$oft.
-
I had similar problems with windows 10. The order of my joysticks (X65, Edtracker, MFD1 and MFD2) get mixed up quite often. Now I will just check the current config and use my attached openoffice spreadsheet to generate a fresh keyfile. Maybe my sheet will help you too… it is much simpler and limited than the official excel file…
-
If only I knew how to use this file ! Newbie here. Windows 10, same problem as the rest.
-
With BMS 4.33.1 such work-arounds are no longer necessary. The manual explains how to overcome the device order problem.
-
If only I knew how to use this file ! Newbie here. Windows 10, same problem as the rest.
Check this thread and just configure your devices in the correct order for your keyfile etc.
Then…:bdance:
-
When I upgraded to Win10 from win7 the same thing happened to me. Apparently this isn’t b/c of windows 10 but something that was changed in Win8 and stay with windows. If you just wipe and reinstall your device drivers it will work fine again.
-
Hey guys,
I have fixed this problem, by simply reinstalling drivers (same as Trukeydriver; http://ts.thrustmaster.com/eng/index.php?pg=view_files&gid=1&fid=3&pid=311&cid=1) and have reorganized Morphine’s profile (as suggested bvy Sarg55). I am a happy camper (again ). All I need to finally conquer is Air-to-Air Refueling.
On a side-note, W10 seems to be stable and BMS is a joy to fly.
Cheers,
Andrej