@Louis-0
ofcourse, the newer version has better and enhanced ai, the f15 has starting to get custom avionics and is gonna keep getting updated

@mlm19390908 said in Logitech x52 pro programming with Joy ToKey for falcon-bms:

@Marge Hello Marge,
What I really interested in if there is any pilot using j2k for x52pro programming and how to make it work for bms. I programmed all buttons and slides etc. and pressing a button on x52pro I can see on j2k that it is a valid program. If I programmed a button as keyboard “B” that gives back programmed “B”. However, bms does not rekognize button press on flight and does not open airbrakes. As j2k only gives config files even if I copy this in the bms/user/config/basic file it does nothing as it is not a key file. I am looking for a pilot who used j2k and how it was made to work.

use UCR (universal control remapper) https://github.com/Snoothy/UCR#downloads

and VJOY to create a virtual joystick.

with UCR you can remap all the buttons you need and you can even remap the X-52’s minijoystick

@SemlerPDX said in Saitek X52 Pro radar cursor problem.:

@glajtman My “Falconeer” profile for X52 Pro (logitech or saitek) shows instructions on how to use the X52 profiler software along with an included profile file for using the mini-stick as ‘bands’ to control the RADAR cursor.

You don’t need to use my full profile, but you could dissect it and grab the bits from any of the included keyfiles for RADAR cursor and copy them over your existing keyfile (mine are set to use arrow keys, up/down/left/right) - and set the profiler to use the included profile with mini-stick bands:

forum.falcon-bms.com/…/semlerpdx-s-x52-pro-falconeer-hotas-profile-for-bms-4-35

(here’s the bit from the bms keyfile)

SimCursorUp -1 0 0xC8 0 0 0 1 "Mini-Stick: RDR CURSOR Up - (Arrow Up)" SimCursorRight -1 0 0xCD 0 0 0 1 "Mini-Stick: RDR CURSOR Right - (Arrow Right)" SimCursorDown -1 0 0xD0 0 0 0 1 "Mini-Stick: RDR CURSOR Down - (Arrow Down)" SimCursorLeft -1 0 0xCB 0 0 0 1 "Mini-Stick: RDR CURSOR Left - (Arrow Left)"

(and here’s the .pr0 file for X52 profiler software)
veterans-gaming.com/…/attachment.php
*this profile file also includes bands on the throttle slider, you’d want to remove that for this example

Thank you

@YellowHawk to answer your question tho, if you look at other threads on this mostly folks will save the registry-code lines to a text file (.reg extension) and double-click on it, to add/overwrite the necessary lines in the registry

doing it “by hand” is possible but will be a serious pain

(most of these threads are re X52 or X65… the PID and VID values are different, and maybe the special hex values differ too, idk)

https://forum.falcon-bms.com/search?term="Windows Registry Editor Version 5.00" HKEY_CURRENT_USER System CurrentControlSet Control MediaProperties PrivateProperties Joystick OEM&in=posts&matchWords=all&sortBy=relevance&sortDirection=desc&showAs=posts

@airtex2019
Well, I guess I have a bit of studying to do.
Thanks!

That’s the way I used to have it, but it stopped working correctly ~2 years ago (driver update? 4.36…?).

Either way, I did the registry edit method which removes the twist rudder, but adds real axises to the ministick which has been working great,
https://github.com/alex-smtv/X52-PRO-Mouse-Ministick-to-Axes

@101-Grizzly it is very unintuitive, and trips up many people… definite FAQ

@gwhitfield said in Pinky switch and joy.cpl:

Relatively new user here. I got Falcon 4.0 when it first came out, but got away from it for many years and was excited to realize it was still around and had developed into this incredible simulator. So since swapping out my Saitek ST290 with the X52 (not Pro) a couple months ago, I’ve had this issue with Pinky switch not being recognized in BMS. It wasn’t a real problem at first, I’ve had all I could handle just getting through the first few training scenarios. However, now that I’m getting a little more acclimated, it has become an issue in trying to refine my setup. I’m on a Windows 10 x64 box with BTW. Driver file I installed from Logitech is X52_HOTAS_x64_8_0_213_0.exe, though device properties indicate 8.0.116.0 for whatever reason.

Problem is that Pinky switch is consistently recognized in Control Panel app joy.cpl and Logitech programming interface, but it’s been very off and on (mostly off) once in BMS 4.35, 4.36, and 4.37, with or without Alt Launcher in use. I’ve done all kinds of things trying to figure out what was going on, uninstall/reinstalls, editing/swapping/removing anything that looks like a possible culprit. Yes, that’s crappy methodology I know, but its not like I was going to break anything that couldn’t be fixed with a re-install. This was driving me nuts and almost gave up having a shifted layer of joystick buttons.

Finally, just a few minutes ago, I hit on the way to consistently make BMS recognize the Pinky switch activity: Run joy.cpl and enter the Test tab (like I’m going to do a calibration), then start BMS with joy.cpl running in the background.

I have no idea what to make of this, or how to troubleshoot BMS or Alt Launcher configs or settings to make running joy.cpl unnecessary. I honestly don’t care if joy.cpl is running in the background, there’s no performance hit as far as I can tell. It’s just the lack of understanding that’s bothering me, as well as the possibility that my finding with the pinky switch may be something that can lead to fix for myself and others in BMS.

Anyway, I’m looking to see if anyone has insight into what may be causing this, or wish to sound off with search result for a fix that I have missed. If it would be useful to others I’m fine with uninstalling everything BMS and re-installing to set up a pristine configuration for troubleshooting.

Thanks in advance for any (constructive) replies! 🙂

Uninstall the LOGITECH control program and drivers.
isntal only the drivers for windows only, DO NOT INSTALL THE LOGITECH CONTROL PROGRAM.

use UCR (universal control remapper) to intermediary between HOTAS and AL (alternative launcher)

with the UCR you can even assign the mini joystick of the X52 as CURSOR in the TQS.

https://github.com/Snoothy/UCR#downloads

If you’re using the Key File Editor I have a small improvement to allocate the DX number correctly. Sorry I don’t have rights to post a picture.
Obviously all credit to the creators for the tool…

You need to unprotect the sheet and modify the calculation for DX number in the respective sheet for your controller.
For me with X55 :
D15 make value 128.
Cell F22 change formula to =IF(ISERROR(F20*$D$15-$D$15),“n/a”,F20*$D$15-$D$15)
Cell F82 change formula to =IF(ISERROR(F21*$D$15-$D$15),“n/a”,F21*$D$15-$D$15)

Happy Hunting.

EDIT: Changes are only to your controller’s callback allocation sheet. Column F will need to be unhidden obviously.

@Badger The STT would be different depending on the stick plugged in, and iirc the X65-F has modes in STT for pinkie and the slider (geez that sounds like the name of an animaniacs spinoff show).

Make sure they don’t have any shift mode set for the pinkie in STT software. There are typically two columns shown when creating a new STT profile - the left column is unshifted, the right is shifted. Delete the shifted layer on the right and take steps to unbind or “default” any buttons which have assignments such as the pinkie or others. This way every button is only recognized as a DX button by BMS, doesn’t try to do its own thing according to STT rules. They’d save that “blank” profile and then make sure it is the active profile anytime they fly in BMS - the little joystick icon in the taskbar “green” and not greyed out.

@AIRBARBA

I think I’ve used that Flounder program as well. Will send you the SCUBY setup as soon as I can.

@Tiger78 Confirmed … mine is dated 1/17/2023…I did it!

Disregard post about 4.37 BasicDX X-52.Key file error. Turns out I created the error in my copy of that file while trying to map my HOTAS the old way using Launcher.exe. My apologies for the confusion and thanks to a member (Airtex2019) for notifying me.

@Amadeus75
My Saitek pro flight rudder pedals do not have such a switch

@airtex2019 Great! Thanks. I like the AL setup much better that the classic UI anyway. Thanks again.

If you’re OK with giving up an axis to gain use of the mini-stick, try following these instructions.

https://www.benchmarksims.org/forum/showthread.php?33116-Okay-I-m-confused&p=462968&viewfull=1#post462968

I was fine with giving up my twist rudder since I’m using a Warthog stick with X52pro throttles. Works great.

@Falket73 said in SemlerPDX's X52 Pro 'Falconeer' HOTAS Profile for BMS 4.35:

@SemlerPDX Thank you very much for your hyper-fast response.
I don’t know what I have to delete on the command string to disable the command of a key to avoid having two different functions with the same button.
Okey, in the section of the command line that makes the radar cursors work and in the air brakes command I don’t touch anything.
Now I try to create a profile with SST and see what happens.
Thanks for your patience.

If you edit the keyfile ‘Falconeer’ section pictured above, for example, “AFResetTrim” is a ‘callback’ (see line 1314) - this ‘callback’ word is the only difference between that line doing something else when we press the B button. You would seek out the callback of the function you’d want to replace in this button (for example) such as “SimMissileStep” and just replace the word “AFResetTrim” with the word “SimMissileStep”. After that, anytime you press the B button on the stick, in the unshifted state, you would be pressing the Missile Step button rather than the Trim Reset button in BMS.

Understand?

Note that these keyfiles are set to “Read Only” by default, and you should right-click on the file, select Properties, and uncheck the box for “Read Only” if you want to make your own custom Falconeer DX keyfile. It’s literally designed for this, and there is even a blank layout graphic link in the first post of this thread if you’d like to finalize your creation with a chart you can follow other than my default layout graphic.

☕
Happy to help if you want, just let me know. Any questions, feel free to ask.

Thank you all. As I am not versed in the teardown and repair I think I will try the Thrustmaster as the X52 is out of my price range.

@Kiwi
Thanks for your answer I fixed the problem by using the config of the 4.35 everything is OK now.