Problem using X52 for Falcon BMS 4.36
-
Using Windows 11 now. I find it impossible to use my X52 for Falcon BMS 4.36 because the radar cursor moves constantly when I use a 4-way hat for this. Anyone have a solution for this?
This was not a problem with older Saitek drivers in Win10. -
What method are you using to make the HAT control the radar cursor?
Meaning, have you set this through Saitek programming software to press keyboard keys, or have you used a keyfile and manually edited in DX entries for this hat and callbacks to the radar cursor, or have you used Alternative Launcher to setup this HAT as radar cursor?
(I swear, that Win11 is just not ready for prime time - not just here at BMS, but several other support forums and discord channels … “I have Win11 and I have a problem…” - I absolutely feel for ya, and wanna say “Ditch it and go back to Win10”, but not in any condescending way, just that Win11 seems more like a headache and could use a year or two before it’s ready for gaming computer use)
-
I have used Saitek’s program in combination with BMS Keyfile.
Well, I was hoping someone had made a quick fix for this Win-11 problem, but guess I’ll have to do it myself the hard way.
The problem is that the radar cursors are programmed with “Shift + up, down, right and left arrow”.
If I enter Shift + up arrow on the keyboard, the radar cursor goes up, but if I release shift first, the cursor continues up until it has reached the maximum range . If I release the “up arrow” first, it’s ok. The Saitek software does not allow deciding which command is “released” first it seems. This applies to several commands such as DMS and TMS. I have tried all the possibilities.
I am now in the process of reprogramming a keyfile where these functions are programmed with single commands only.
Will probably build me an extra Win-10 pc Only for BMS.
Don’t know if it works to have both win-10 and 11 on the same PC.
It worked fine with earlier versions of windows.
Regards Ståle . . . -
@1Norwegian That’s exactly why I asked what method you’re using for the radar cursor binding(s).
I had that same problem. For that reason, I removed the “shift” from the callback for the radar cursor arrows, so that I could just use the arrow keys. This worked for me because all of my other controls are bound using DirectX in the keyfile, and so this change didn’t affect any other callbacks as set. Alternatively, we can just swap the ICP DED keybindings for the Radar Cursor keybindings, so the cursor is just arrows, and the ICP DED keys are “SHIFT+Arrows”.
Saitek’s software has been notoriously garbage for over a decade and hasn’t changed one bit, and never will. Because of this, I personally recommend using only DirectX bindings for all controls, and only use the Saitek software when absolutely necessary, such as the Radar Cursor callbacks into bands or binds that press keyboard keys when we move the mouse-ministick on the throttle - anything else can benefit greatly from eliminating the weakest link from that chain, being Saitek’s trash programming suite.
The change in Windows OS highlighting this flaw is likely more of a false-positive than anything else. I’m on Windows 10 and had your same issue until I eliminated the “shift” key from that set of callbacks for the radar cursor.
I am unsure if you are using your own keyfile or one of the existing keyfiles, you can add this to the bottom of your current keyfile - and of course, remove the “SHIFT” part of your HAT assignment in your Saitek profile so that HAT is just pressing the respective arrow key(s) and not trying to do a shift-key combo:
#==Altered callbacks for ICP DED as "SHIFT+Arrow Keys" SimICPDEDUP 120 0 0xC8 1 0 0 1 "ICP: DCS UP - Push" SimICPDEDDOWN 120 0 0xD0 1 0 0 1 "ICP: DCS DOWN - Push" SimICPDEDSEQ 120 0 0xCD 1 0 0 1 "ICP: DCS SEQ (Right) - Push" SimICPResetDED 120 0 0xCB 1 0 0 1 "ICP: DCS RTN (Left) - Push" #==Altered callbacks for Radar Cursor as "Arrow Keys" (only) SimCursorUp -1 0 0xC8 0 0 0 1 "TQS: RDR CURSOR - Up" SimCursorDown -1 0 0xD0 0 0 0 1 "TQS: RDR CURSOR - Down" SimCursorLeft -1 0 0xCB 0 0 0 1 "TQS: RDR CURSOR - Left" SimCursorRight -1 0 0xCD 0 0 0 1 "TQS: RDR CURSOR - Right"
(note: placing these at the bottom of a keyfile is sufficient, they will be read last and override any previously definitions for these same callbacks earlier in the keyfile - you do not need to hunt down and change/remove these from an existing keyfile)
-
I am using Logitech software which emulates keyboard presses when I am pressing a button.
I have created a profile allinged with BMS full keyfile and everything is fine but I have win10.
The interesting part is that with the Logitech software you can create macro command with keyboard presses. I mean that with this software you can define the order of the key that is pressed and released.
For the radar cursor now another solution is to redefine through the registry the axis and activate X Y axis on your microstick. By that way one existing axis will be lost (I chose the slider) as windows can see only 8 axis per device and x52 has 9. If you search there is a post explaining how to do it. Or else send me pm to fix this out.
-
To expand on the X52 mini-stick as Radar Cursor concept, this can also be achieved using bands on the mini-stick axes in the Saitek programming software without losing an axis. Either way, it’s better to use the HAT & POV on the X52 for F-16 controls as the F-16 needs so many HAT’s, and to use the X52 mouse mini-stick for the Radar Cursor.
-
@SemlerPDX
Thanks.
I will study this further.
I have managed to create a setup that I am testing now.regards
-
@Ironman3 Hello.
Thanks for the advice.
I have tried “macro”, “keypress” and “advanced” and so on with no luck in Win-11. But works fine in Win-10.
Greetings Ståle. . . -
If you’re OK with giving up an axis to gain use of the mini-stick, try following these instructions.
I was fine with giving up my twist rudder since I’m using a Warthog stick with X52pro throttles. Works great.