Controls locking
-
Ok, Im reasonably new to BMS, experience has been mostly good so far, had the software run on 4 - 5 computers succesfully in trying it out and setting it up for friends recently. But of course something had to go wrong…
The system I have the problems on runs windows 7, BMS 4.32 update 7, has 2 screens, 1 projector, 1 as a instrument panel and uses a saitek x52 to control it. Most of the controls are mapped through bms however certain controls like cursor and radar range are programmed to keystrokes through saiteks software. My control config is a slightly modified version of kesmonkeys profile - /forum/showthread.php?5855-Saitek-X-52-Profile
My problems seem to originate from the radar cursor, it is programmed to the ministick in saiteks software using bands on the axis which just simulates the appropriate keys being pressed. This works mostly however when I move the ministick to one of the left hand corners and sometimes the side, the keys become stuck until the stick is pushed into the appropriate corner and released again.
Sometimes, not sure if this is a related issue or not, all keystrokes or control inputs are ignored, even commands to exit the mission, while the aircraft still simulates, eventually the controls do come back but by then the aircraft is usually a pile of smoke.
Another completely unrelated issue I have being having on this simulator is that BMS doesn’t run in full screen, however this is probably down to my incompetence as I havn’t had chance to research that issue.
Would appreciate any help you guys can offer as it seams to be unusable in this state.
Thanks in advance! -
I don’t have an X52 stick but does the ministick on it register as a pair of Axis or only button presses. If an Axis the map the Cursor X & Y controls directly to the ministick and be done with the pseudo keypresses.
Just a thought
-
good thought, but unfortunately I’ve tried that, bms dosn’t seem to see the axis from the ministick even when it’s unprogrammed in saiteks software.
-
Is there some kind of lightweight tool that I can use to give a detailed log of all keystrokes put into the computer that I can run while I test it in bms to reproduce the issue and see if its on the saitek side or bms side? I know that some keyloggers exist but I dont know how detailed they are or what can be trusted!
-
The SST software has built-in keystroke monitoring.
-
Great! I will do some fiddling and poking tomorrow to see if I can get any closer to the root of the issue!
-
I recently had a similar problem when mapping the radar cursors to my X-65F throttle module’s ministick or a certain hat switch, neither of which is recognized by the sim’s Direct X mapping feature. I was also using Kolbe’s . . . min keystrokes file. While testing in flight, the cursors would continue to move after I released the mapped control. The mapping worked fine when using the keystrokes.key file.
After considerable teeth gnashing and hair pulling, I compared the key assignments in the aforementioned .key files. In the keystrokes.key file, the cursors were assigned to the <arrow>keys, whereas in the . . . min.key file, they were activated by Alt- <arrow>keypresses. I went into the latter .key file and edited the key assignments to match those of the keystrokes.key file. Actually, I traded key assignments, because the <arrow>keys were originally mapped to (I believe) the four-way toggle switch in the Up Front Control panel.
Anyway, I now have no problems moving the radar cursors with the X-65F’s ministick.</arrow></arrow></arrow>
-
good thought, but unfortunately I’ve tried that, bms dosn’t seem to see the axis from the ministick even when it’s unprogrammed in saiteks software.
If you are willing to lose the twist rudder axis, you can change it so that the mouse axes are seen as directX axis and that way, BMS can use them. Much more smooth than using keypresses, as you can move the cursors a little or a lot.
there is a registry edit file saved to my site for a few common saitek sticks, including the X52 and X52 Pro.
Anyway, I now have no problems moving the radar cursors with the X-65F’s ministick.
I also have a similar file for the X65F.
-
So in terms of the keys programmed, it uses the default f8 - f11 keys, I have the same keys programmed the same way but on a different system and the x52 pro instead and that works completely fine.
in terms of your reg edit blu3wolf, exactly what does it change and in what way, how would the process be reversed?
-
well, you can check exactly what it changes by opening it with notepad.
what it changes - edits the numbering of the axes declared to directinput in the registry, to make the twist rudder number 8 and adds two extra axes, which are set to the ministick. axis number 988 is not used sadly by directinput, but its there so that if you want to reverse it, you can manually (using regedit) change the numbering back so as to have the twist rudder back in its original number 2 (stick X and Y are 0 and 1).
End result of the changes are that your rudder is no longer seen by directX (although if you have the SST software installed it should still be able to see the rudder moving), and you get two new axes which correspond to the position of the ministick. You will need to go into the BMS setup and tell it that you want to assign those axes to the ministick, same way you would have set up the antenna elevation and or range knobs.in what way - its a .reg file, if you double click it it will add its entries to your registry. I think that file association is with regedit?
How would the process be reversed - two ways, if you are comfortable with registry editing you change the numbers of the axes back, if you are not comfortably with registry editing you just delete the joystick keys from your registry entirely and plug the stick back in, install it again, etc.
the exact changes vary depending on which file and thus which joystick you want to change.
-
Right, good news, sort of, I have pretty much determined that for whatever reason the left hand cursor key on that sim likes to lock up my controls. I installed your reg patch and it worked a charm for me, so the cursor now works and didnt experience any complete lock ups, did not do extensive testing though.
Thank you for your help!
-
Glad to hear its working for you!
-
I use a Saitek 52 original mark one and I had the same issues. I cured mine after some messing about and found that the HOTAS will NOT function orrectly if it is plugged into a USB 3 socket, (usually the one surrounded in blue) the drivers for certain parts uninstall themselves dunno why. The cure, save your logbook out of the user/config file and your keyfile youve been using. If you use the BMS.key file that one is set up for use with the Cougar Hotas and thrustmaster series in general.
Next sorry but its a reinstall falcon. Not a massive job. Uninstall it. then power off your PC. If the Saitek is plugged into a USB socket with a BLUE bar youll have to move things around to get it in one of the BLACK bar sockets. Once thats done, restart your machine, then reinstall the Saitek drivers and the SST software. Your profile should have been stored in the documents library so it will be fine. Once reinstalled go through the entire movement arcade in the control panel and move everything to its limits and back again at least 5 times to get it all synced up in the drivers.Now just reinstall BMS and check your profile on the SST is working. USB3 causes mayhem with the SST software it took me 3 weeks to find what had been going wrong. If you need to amend your SST profile then do so. If you have to modify any keystrokes I would suggest you use a text editor like notepad and do it that way to change anything. Use a copy oof Red Dogs callbacks manual to assist if needed and the key selections are easy enough to change.
Hope this suggestion works for you although a little intence and a bit of reading up is required. But you can assign all the major commands directly to the DirectX portion of the key file right at the bottom, you have 32 selections in there that get mapped straight to the game. Plenty of posts on the forum regarding that so youll have no trouble finding info.
-
My X52 is plugged into a USB3 Socket with no problems whatsoever.
-
I use a Saitek 52 original mark one and I had the same issues. I cured mine after some messing about and found that the HOTAS will NOT function orrectly if it is plugged into a USB 3 socket, (usually the one surrounded in blue) the drivers for certain parts uninstall themselves dunno why. The cure, save your logbook out of the user/config file and your keyfile youve been using. If you use the BMS.key file that one is set up for use with the Cougar Hotas and thrustmaster series in general.
Next sorry but its a reinstall falcon. Not a massive job. Uninstall it. then power off your PC. If the Saitek is plugged into a USB socket with a BLUE bar youll have to move things around to get it in one of the BLACK bar sockets. Once thats done, restart your machine, then reinstall the Saitek drivers and the SST software. Your profile should have been stored in the documents library so it will be fine. Once reinstalled go through the entire movement arcade in the control panel and move everything to its limits and back again at least 5 times to get it all synced up in the drivers.Now just reinstall BMS and check your profile on the SST is working. USB3 causes mayhem with the SST software it took me 3 weeks to find what had been going wrong. If you need to amend your SST profile then do so. If you have to modify any keystrokes I would suggest you use a text editor like notepad and do it that way to change anything. Use a copy oof Red Dogs callbacks manual to assist if needed and the key selections are easy enough to change.
Hope this suggestion works for you although a little intence and a bit of reading up is required. But you can assign all the major commands directly to the DirectX portion of the key file right at the bottom, you have 32 selections in there that get mapped straight to the game. Plenty of posts on the forum regarding that so youll have no trouble finding info.
XD
uninstall? for screwy joystick drivers?
And you call yourself a dev?