X52 Pro problem.
-
I have a problem with x52 and keyboard commands that include two keystrokes for “X” (X being whatever command ie move radar cursor up).
In the BMS Full Key file the command for slew radar cursor is shift arrow down, shift arrow up etc. Another is trim nose down is alt /. The problem is that when I try to use these keystrokes, either by programming the stick while in Falcon or via the Logitech programming software, is that when I try to use a command it latches and becomes sticky. If I program the mouse on the throttle to slew the radar cursors the moment I try to use it in game it latches - I move the mouse up and let go but the cursors move up and never stop. If I use the pinky switch POV 1 up and release it trims the nose down to the limit.
If it is just one keystroke then everything works OK.
Hoping someone can help.
Thanks in advance guys.
Mac.
-
This post is deleted! -
There is no fix for this and it’s a semi-known issue. Most people use a registry edit to change which axis’s are available on the throttle.
Thanks for your reply. That’s too bad.
-
This post is deleted! -
I send you some screens of how I have configured my stick in x52pro to work as a radar cursor.
-
Segwin, one thing you can try is to reassign the command to a non compound keystroke, Saiteks can get wonky with those. What I mean is , instead of cursor up being shift+up arrow, assign it to something like }. : and " are good ones to use, too
-
There absolutely is a fix for this.
Assuming you’re trying to use the mouse nub for cursor slew, what you need to do is bind both the press and release events for each key in the proper order. So if cursor left is shift left arrow, your SST config should be:
(On Press)
Press shift
Press left arrow
(On Release)
Release left arrow
Release shiftThe mouse nub axes also need to be set to bands, with a good 50% dead zone in the middle.
Do not bind anything in SST except the mouse nub. Everything else should be done using the key file. BMS will accept any number of simultaneous DX inputs, so that is by far the superior way to bind buttons.
-
Ahoj přátelé …. Mám také problém s X-52pro na 4,34 … jezdec přestal pracovat, jsem nastavit FOV v pokročilé části na to, a pracoval dobře, ale najednou se zastavil. V kontrolních panelech av samotném sokolím řeknu, že to funguje správně, ale v 3d není žádná reakce … znáte někoho, kde bych mohl mít chybu? Díky
i5-2,8ghz … 18 gb ram … gforce 1060 6gb … hdd 1tr -
I simply do not understand how it works…
As long as I did not try to use “X52_Professional_HOTAS_x64_8_0_213_0” SW the MFD on the throttle was not on. The three state MODE selector on the stick worked as a selector between the two override modes and in middle mastermodes are working.
I installed this SW and since than MODE selector try acts as MODE selector and does not work in BMS4 as override selector.It does not matter what is set. The marked selector does not do anyting since the MDF is lighted up. When I use the selector MODE 1 2 3 are set instead changing the override modes.
How can turned off this ***** thing….? I was not able to find any manual or document why this is happened and how should be fixed. Because this is the only selector with three positions I cannot fix the HOTAS which after 6 hours of painful work I almost completed. Without this the situation is simply GAME OVER…
-
In the Excel table is the default setup that Mode 1/2/3 positions are used for override settings. Since the Saitek/Logitech software is installed that selector cannot be programmed any function. It is just a global “shift” button without you have to keep push down it.
I simply cannot understand how can be set up as way Excel table which makes unusable. Before in installed the Saitek/Logitech software the selector simply worked differently and did not change the X52Pro itself MODE 1 2 3. And this cannot be turned off no matter how I want to do it.
-
Hello,
Ideally, you should not use Saitek / Logitech software, in my humble opinion !!!
Implement DX commands. -
Hello,
Ideally, you should not use Saitek / Logitech software, in my humble opinion !!!
Implement DX commands.Ok, but I cannot revert back the effect of Logitech software. Even after removing it the MODE 1 2 3 selector is unusable to set override modes regardless is set with the Excel table.
-
molnibalage, a person who can help you, would be Agave_Blue, send MP, explaining your problem.
-
molnibalage, a person who can help you, would be Agave_Blue, send MP, explaining your problem.
Replied via PM, however, in case it might help someone else, below is the crux of my reply:
First, just so you know, I have not used the X52 Pro for a year or so. I’ve changed to the Warthog Stick (first), then added the WH throttle a bit later. Also, I’ve been flying DCS and so have not updated BMS to 4.34.
For your problem, the only thing I can think of is that the Saitek programming (SST) is setting the Mode Knob, thereby overriding or creating a conflict with the DX assignments you’ve made. However, I believe you posted that you are not loading a Saitek profile (*.pr0).
Which is very confusing since the SST should not assign the mode knob if no *.pr0 profile is loaded.
A few ideas:
-
Can you create a ‘dummy’ *.pr0 profile …. basically a blank profile … and load it. The idea would be to replace whatever is happening now with something you make that has no impact?
-
Can you completely remove the profiling/SST software from your PC and allow only the native Windows Device recognition? This would of course prevent any SST Key Emulation for any program, not just BMS.
-
Can you use a different version of the SST software? I don’t recall which version I had used successfully and I have several saved on my hard disk. The latest one looks to be Saitek_X52Pro_Flight_Controller_7_0_53_6_x64_Software .
-
-
One other thought ….
Use the Windows Game Controller panel (Control Panel --> Devices and Printers --> Right Click X52 Pro --> Choose Game Controller Settings --> Properties) and check that the Mode Switch is indeed recognized. It should appear functional and act as you change the knob. This should be true even if no SST software is loaded.
-
Molni,
take a look at the BMS Device Setup Guide located in …/Docs/01 Input Devices/03 HOTAS Setup chapter 5.2 MODE SELECTOR SWITCH on page 118.
You have to delete the modes in your .pr0 profile to use them as DX buttons. You can also use the BMS X-52pro_DX.pr0 which already has all the necessary settings
located in the Saitek X-52 Pro subfolder. -
Was able to solve the problem,molnibalage ??
-
Was able to solve the problem,molnibalage ??
I was able to learn to set as way the Logitech SW to make more usable as turning off but I also worked deleting all pre defined state in case MODE selector also could be programmed.
Thx. I’m heading now to flying.