Saitek X52PRO radar cursor issues
-
Hello all. I’ve been experiencing a problem with the radar cursor on BMS. For some reason it only goes down and right. First thing i did was to go check on the control panel to make sure i didn’t have a hardware malfunction. Every key, switch and cursor was working, including the radar cursor on the throttle. But it seems when i go to BMS it’s not acknowledging the left or up movement on the radar cursor. I’m using a profile from Hard~Deck, which is what i used back in 4.32. Also i’m using Windows 10 and i’m using the Saitek beta drivers for it that i found somewhere around here. Has anyone else been experiencing the same issue or knows of a solution? Thanks.
-
I’ve got the same issues. I’m using win7 64bit. In the Thread: “Saitek X52 PRO issue” is by Shaeone (#13) said “maybe your problem is caused by ‘Direct Output’ process. Just go to the Windows Task Manager and kill the process. Give this a try, because I’ve got the same problem using TeamSpeak while flying, it’s a known issue.” but this didn’t helped me also. I hope somebody got a answer to this problem.
-
Disable tlsomthi g called keyboard and mouse only in team speak that might fix it.
-
I had the same issue in 4.32 when I upgraded to win10, but fixed it. Below are the things I did, hope it helps.
(Disclaimer, I don’t know if 4.33 will agree with 4.32 axismapping being copied across?)
I unnstalled all software/drivers and got new beta installed, rebooted then did this:- Went back to the 4.32 version and confirmed stick works as it should, note the loaded stick profile
- In the config folder, I copied the axismapping and Joystick reg entry(profile) and placed them in the config folder of the theatre I had issue’s with.
- It then worked for me.
Hope that works for you.
-
I use the X-55 and was having a problem with the radar cursor movement as was mapped with a key command in the SST software. Using the advanced command like in the attached pic solved the problem - I think the X-52 and X-55 use the same advanced command functionality. Seems like BMS doesn’t like SST using the shift key in some instances. Note that the entry in the press section is the button being pressed down and the release section is the button being released. Also the shift key should come at the end in the release section.
-
I’ve just formated the PC, fresh install of Windows 10, got the beta drivers from Saitek, didn’t install any others so there wouldn’t be any conflicts. Installed Falcon BMS, loaded up my old joystick profile, tested it, everything seemed perfect at first. Then i loaded up a campaign flight, and it got busted again, and it refuses to work, back to only moving down and right… I’m so sad
-
I had a VERY similar issue some time back. I could not effectively track down a cause. I thought it was my keyfile, my Saitek SST profile or a conflict with Teamspeak. I upgraded Saitek drivers, retrograded Saitek drivers, rebuilt keyfiles, etc., etc., etc.
Ultimately I deleted Teamspeak and installed it from scratch to a previous version that I know had worked with my setup. That is what worked for me (and is still working). I was put on to the Teamspeak track as the problem originally occurred after a TS update.
One thing is certain, in Teamspeak (if you’re using it), under SETTINGS –> OPTIONS --> HOTKEYS be sure to select “KEYBOARD & MOUSE ONLY” in the lower right.
My current Drivers/Software versions:
TS = v3.0.18
Saitek SST Software = v7.0.27.13
X52 Pro Driver = v7.0.34.109
-
A friend told me that same solution, it didn’t work… And when i unplugged my stick it really did a number on my Windows. Even tho it pains me to do it, with BMS 4.33 being out and all, i’ve decided to not mess with this until Saitek get their act together and release some proper drivers.
-
My problem is solved…… I unstalled the SST Software and the drivers. Very good cleaning of the pc (and by regedit). I followed the instructions of Gunshow at https://forums.frontier.co.uk/showthread.php?t=153006, thread #9.
Unplug X52Pro device from the computer and I installed first the drivers and after a reboot the software.
The software and the drivers i’ve got from ftp://ftp.saitek.com/pub/software/beta/Windows10/. It’s for Windows 10 but it worked for me with Windows 7 64bits. Now I’ve got my radar cursor by ministick.
I hope it helps others too.
I used:
Saitek_X52_Flight_Controller_7_0_42_12_x64_Software.exe &
Saitek_X52_Flight_Controller_7_0_42_12_x64_Drivers.exe.By the way, I use Flounder’s X52 Pro Keyfile-DX Profile for BMS 4.33. Thanks Agave_Blue.
-
Dont know it is what is causing your problems, but if you are using bands on the mouse coursor you have to have the middle neutral band the biggest going from around 15-20% to 80-85% so that any jitters that may be in the stick dont cause any problems and only your command sends a signal, i do the same with my slide on the x-52pro for the speed break, only the last 10% of the travel generate a command.
Hope it helps
-
So i went ahead and got rid of Windows 10 so i wouldn’t have to deal with anymore nonsense about beta drivers and non-compatible drivers from Saitek. Reverted back to Windows 8.1, did a fresh re-install of Falcon BMS, got the right drivers and software for my stick, re-downloaded Hard~Deck’s profile and everything is working fine except that in game i can’t get the throttle slider to operate my air brakes and the mini mouse to work at all. At first i though maybe my throttle was having problems, maybe something was broken, but when i go on the control panel to test it, everything works fine including the throttle slider and the mini mouse. It seems that it’s somehow in game that those functions aren’t being assigned to what they should be doing after i load up the profile.
-
So i went ahead and got rid of Windows 10 so i wouldn’t have to deal with anymore nonsense about beta drivers and non-compatible drivers from Saitek. Reverted back to Windows 8.1, did a fresh re-install of Falcon BMS, got the right drivers and software for my stick, re-downloaded Hard~Deck’s profile and everything is working fine except that in game i can’t get the throttle slider to operate my air brakes and the mini mouse to work at all. At first i though maybe my throttle was having problems, maybe something was broken, but when i go on the control panel to test it, everything works fine including the throttle slider and the mini mouse. It seems that it’s somehow in game that those functions aren’t being assigned to what they should be doing after i load up the profile.
If you’re using TEAMSPEAK MAKE SURE at the HOTKEYS tab the right down bottom scroll menu selected"mouse and keyboard only"…SST software conflicts and causes pitc problems and other issues when teamspeak hotkeys are set to “default”…Hope this helps
