Yes just what you have circled it what my problem was. Thank you.

Another realization of mine is that the Range Knob is actually used to adjust the zoom level of the TGP - and the gain level of the A-G radar instead of choosing HSD I will be able to increase the range (8-20-30…), or the FCR radar (10-20 -40…) as well

Here are my pictures of windows properties of the stick and Throttle
can’t use the Range in BMS
It seems that antenna is twice why ?
Can you help me
Thanksstick X65F.png

Hello Oak
Need your help about the radar cursor with ministick.
It works well but now I can’t use the range knob
Can you help me?
Thank you
Danpil

@Amadeus75 Ok issue sorted. I figured that there might not be other pre-set channels loaded. Are, I wonder if I need to load up the tape which wasn’t needed before. And so I loaded up the tape and the pre-sets are now available. Subtle little changes like this in updates does take a while to figure out. I have been online in F4, but that is pushing a quarter of a century ago.

@SemlerPDX Yes its solved and i dont have a clue how😳 Thank you

@Segwin

Have you tried doing it without extra software?

You could just map the ministick to cursor axis in the BMS setup.
(A deadzone is possible there as well.)

<p>@malpaso <br />its a video you made, great work, thanks.</p>

<p>@danpil To get @kungfoo 's attention, ask in this thread: <a href=“https://forum.falcon-bms.com/topic/19769/new-free-mfd-icp-app-to-control-falcon-bms-from-touch-devices/109” target=“_blank”>https://forum.falcon-bms.com/topic/19769/new-free-mfd-icp-app-to-control-falcon-bms-from-touch-devices/1</a><br /></p>

Ill give the Combat Pro Rudder Pedals software a go and see what happens.

Apart of the options missing in the system tray another weird thing that happens is that i keep loosing functionality on the 3 mode rotary knob. Its setup for Dogfight mode. Sometimes it works fine other times it puts me in one of the modes and changing the modes does nothing. Its definitely not the x52. It could be the SST or maybe a BMS thing. Not sure.

mine sometime after a dogfight is totaly out of neutral so i use alt+c and J to recenter the joystick . of course you need to leave the joystick neutral (and the aircraft free … )

Define “too sensitive”. I had the problem of firing multiple weapons at once (and sometimes it wouldn’t fire at all, unless you released the button and pressed again). A small delay (100 ms did it for me) in JG can solve the former (the larger problem), but not the latter.

I soved it entirely by mounting an additional button next to it and connecting it to an Arduino.
You could also solve it by opening the stick and replacing the button, but getting everything back in place afterwards isn’t easy and you need to solder very small parts (I believe it’s an SMD butoon)

Cool, Killroy,
Glad you got it working!

@sungad:

You can also adjust the corsor speed in the config.

@oakdesign:

You have 2 options
1. In the BMS configurator you can change the overall cursor speed.

😉

@oakdesign:

Even if the Pinky in SST is unassigned it makes a difference if its Latched or unlatched and I’m not sure if that is saved in pr0 or somehow handled directly through the driver

Unfortunately, the Pinkie being latched would only be possible through the .pr0 and is not handled directly through the driver, and these files in my Falconeer set are locked to ‘read only’, so can rule out any unknown accidental re-assignment or change being a factor here. Someone would definitely remember the procedure if they manually latched the Pinkie in one of my Falconeer profiles given that extra hassle. Gotta be something along these lines, for sure - there are only two places to tell the Pinkie what it can do: the .pr0 and the .key and I’ve gone over them twice now. Gotta leave it in the hands of fate now, nothing more I can really offer along the lines of help afaik

Any ideas definitely more than welcome - and thanks for helping oak!

Good approach, Semler!

Hi guys,

Just a heads up for those using Windows 10 64 / 32 There is a crash issue with the old Mad Catz software. I use the Saitek X52 Pro, couple of other pilots near me use X55 and 56.

There is a great replacement for the older software specifically designed and works with Windows 10 with no issues. Just go to the Logitech SIte (seeing as they now own the rights to the Saitek series of sticks and HOTAS)

www.logitech.com

The new set of drivers and Software are now registered with Microsoft, so there are few issues if any.

Those still using Windows 7 / 8, I havent got a 7 / 8 platform to test them on, so stick with what you know.

Everyone can use joy.cpl in your system to work out what the buttons / axis are numbered as for DirectX inputs if needed at the bottom of your keyfiles.

Hope this helps you out.

Stay safe and well

Jacal, did you try x52 Pro before x56 ? Which of them is best flying BMS ?

If nothing else works, use Joystick Gremlin + vJoy and map the hats to buttons on a virtual joystick.

@Sid9001:

Hi
What is the relationship with binding the DX buttons to Hotas and the saitek profile.
Does the profile on the mad cats software need to be adjusted with each change in the dx file.

Trying to swap POV functions with trim functions. Cockpit views pan wildly on single click of POV view .
Thx

Hi, Sid,
If I may make a suggestion, download the BMS Alternate Launcher and you will be real happy. Back in the x-65 days, I went from 99% SST to about 1% after getting AL. BTW, AL uses the BMS_Full keyfile