Cursor radar
-
@bmebr
https://forum.falcon-bms.com/post/94384Applies to both the Pro and non-Pro versions of the X52. Again, I don’t understand why people insist on mapping their ministick to keyboard keys and experiencing this problem instead of using it as the analog axis it is and having a perfectly working radar cursor.
-
@justonce01 I will take a try! Thanks!
-
@bmebr let us know if it works buddy!
Greetings from Brazil
-
4.37U1 can move diagonally now but let say you were going “Down Right” but want to go “UP LEFT” you cant literally do it right away. You need to go back to neutral (no input) wait a bit then move. Otherwise it wont move at all
-
@gabrielwong1991 said in Cursor radar:
4.37U1 can move diagonally now but let say you were going “Down Right” but want to go “UP LEFT” you cant literally do it right away. You need to go back to neutral (no input) wait a bit then move. Otherwise it wont move at all
-
-
I think I got a solution to this problem : in the keyfile (I’m using the FULL one) you can see that TQS Radar cursor use Shift plus Arrows.
Perhaps Shift command is the problem, so I made modifications of this Keyfile, suppressing Shift and using only the Up, Down, Left and Right Arrows, so it’s working better. It’s not perfect but temporarily acceptable, waiting for a correction in next Update. -
@Marge said in Cursor radar:
I think I got a solution to this problem : in the keyfile (I’m using the FULL one) you can see that TQS Radar cursor use Shift plus Arrows.
Perhaps Shift command is the problem, so I made modifications of this Keyfile, suppressing Shift and using only the Up, Down, Left and Right Arrows, so it’s working better. It’s not perfect but temporarily acceptable, waiting for a correction in next Update.Hi, Marge, keep in mind that in 4.37 you are actually using BMS-Auto. The new, formerly Alternate, Launcher creates Auto as you set up your HOTAS
-
I don’t get it? I use absolute axis on my stick (VKB) and assigned it as an axis in Falcon for the cursor (it has X/Y axis, same as X52 ministick).
No problems here with it working.
It seems you’re using an axis to fire keybinds, and the keybinds are not releasing properly. I strongly suggest you do not use keybinds, but just use it as a straight axis for controlling the cursor.
-
@Tiger-0 +1 for VKB … the ministick quality is lovely. but the situation for X52 users is much tougher…
-
using ministick in analog mode puts them over 8 total axes so they have to give up another, eg. twist-rudder
-
the ministick seems to be either/both (a) very poor hardware quality or (b) maybe has incorrect HID device descriptors? judging from the way people describe it behaving as if “stuck in the lower quadrant” … (seems like the HID descriptor is saying it’s a 10-bit range but actual signal is 8-bit range … something like that)
-
the above means it requires a huge degree of range- and center-calibration … but the TM software for X52 Pro doesn’t install (or run?) on Windows 11 …
-
for some combination of the above reasons, X52 Pro folks are using it in digital-hat mode instead of analog-ministick mode… but then, it acts like a 4-way hat (like a console game controller d-pad) not an 8-way hat… so eg. when pressing up+right it sends simultaneous signal for ‘up’ and ‘right’ buttons depressed
-
and that is why they’re running into the new bug/quirk with BMS. apparently BMS used to respond well to up+right keys/buttons being depressed simultaneously, but now it doesn’t.
the main point of all this is… never give money to Saitek / Logitech. lol
there are some registry-key hacks… I don’t have X52 so can’t say if they work or not… and I don’t know all the gorey details, but it really sounds as if the device has screwed up default HID axis-range/resolution descriptors
-