X52 PRO Profile by Scuby
-
I just got back into BMS and love the profile but… how do you lock a target with the radar cursor? there is no key assigned to the keyboard or stick? im lost haha
Edit…. well now i feel dumb i figured it out haha…
-
I just got back into BMS and love the profile but… how do you lock a target with the radar cursor? there is no key assigned to the keyboard or stick? im lost haha
Hi!
Place your radar cursor over a contact, then, use TMS UP on your flightstick to bug the contact. I’d suggest further read in the manual.
Cheers,
Scub -
haha yup… i was looking too much into the key mapping… and they had some button labeled “radar-designate target” which i fixated on because it wasn’t mapped to anything… I read the Manuel and figured it out.
Thanks for the profile, and feedback!
-
Import the .key file into BMS.
Hi Scuby ! I have a simple question about importing the .key file : how do you do ? Thank you for sharing your profile ! -
Import the .key file into BMS.
Hi Scuby ! I have a simple question about importing the .key file : how do you do ? Thank you for sharing your profile !Copy the keyfile to the folder …. C:\Falcon BMS 4.32\User\Config
Start BMS; go to SETUP --> CONTROLLERS. On the lower right side choose LOAD. Select your keyfile from the list and LOAD. Choose SAVE.
Be sure to set up any axis controls in the ADVANCED area of the controller set up.
-
Thanks for profil file.
-
Update Jun/06/2015:
-Re-assigned keys for 1st and 2nd Trigger Detent
-Solves simultaneous key conflicts, e.g. allows manual-laser with VHF/UHFInstallation:
Download the updated package (.rar) here: http://bit.ly/scubyflying (Refresh the download page).
Replace the .pr0 file into your Saitek SST software.
Replace the .key file into BMS.Cheers,
Scub -
thanks a lot Scuby. Works like a charm. Beers on me buddy :drink:
-
I’m having trouble getting this to work. None of my joystick buttons are working… I’m sure I must have missed something obvious. I hope somebody can help!
I’m using an X52 Pro with the latest driver and profiling software downloaded from Saitek. I followed the instructions on how to install Scuby’s X52 Pro profile into the Saitek software and into BMS. I selected the pr0 file in the Saitek software, and loaded the .key file into BMS. Then I set up the axes in BMS as per the screenshots. I noted that the axes and rotation controls all appear to work correctly in the setup window, including the range and elevation controls. However most of the buttons don’t seem to do anything in the Setup window. In fact, the only response I can get is from the Saitek left MFD button (unassigned), and Shift-Trigger, which is mapped to HOTAS-CMS.
When in the air, I can control the plane (ailerons, elevator, rudder, throttle all work correctly), but none of the joystick or throttle buttons work. The radar elevation wheel control does work. However the range wheel control and the mouse/cursor don’t work.
The X52 Pro LCD display shows that it’s in F16 HOTAS mode, and the correct text appears on the LCD when I press any of the buttons.I’m using BMS 4.32 with updates 1-7, on Windows 7 Pro x64. I tried deleting and reinstalling BMS but still have the same problem.
I feel like I must have overlooked something really obvious. Does anyone have any ideas?
-
I’m having trouble getting this to work. None of my joystick buttons are working… I’m sure I must have missed something obvious. I hope somebody can help!
I’m using an X52 Pro with the latest driver and profiling software downloaded from Saitek. I followed the instructions on how to install Scuby’s X52 Pro profile into the Saitek software and into BMS. I selected the pr0 file in the Saitek software, and loaded the .key file into BMS. Then I set up the axes in BMS as per the screenshots. I noted that the axes and rotation controls all appear to work correctly in the setup window, including the range and elevation controls. However most of the buttons don’t seem to do anything in the Setup window. In fact, the only response I can get is from the Saitek left MFD button (unassigned), and Shift-Trigger, which is mapped to HOTAS-CMS.
When in the air, I can control the plane (ailerons, elevator, rudder, throttle all work correctly), but none of the joystick or throttle buttons work. The radar elevation wheel control does work. However the range wheel control and the mouse/cursor don’t work.
The X52 Pro LCD display shows that it’s in F16 HOTAS mode, and the correct text appears on the LCD when I press any of the buttons.I’m using BMS 4.32 with updates 1-7, on Windows 7 Pro x64. I tried deleting and reinstalling BMS but still have the same problem.
I feel like I must have overlooked something really obvious. Does anyone have any ideas?
Hi!
When the X52 Pro LCD shows it is in F16 HOTAS mode, it appears that you have loaded the .pr0 correctly.
If all the axis work than BMS recognizes the flightstick and throttle just fine.Going after what you explain about the HOTAS-CMS after pressing the trigger, Im concluding that probably the .key file is not loaded correctly in BMS.
If only the buttons are the problem then there are two things you need to check to be sure:(1) try reloading the .pr0 and don’t forget to click the load profile button in the software and/or in the taskbar menu.
Open a Microsoft Word or Notepad Window and see if the buttons result in actual keys being entered as text in this window. Now you know that the keys are working.(2) try reloading the .key in falcon bms, don’t forget to give it a courtesy save. Try ingame if the buttons respond correctly.
Hope this helps,
Cheers,
Scuby -
Thanks Scuby!
I tried viewing the button presses in Notepad, and found that this doesn’t work, although the button presses do work within the grid matrix in the SST tool. ( I made sure that the X52-BMS profile was selected within the taskbar menu. ) So this appears to be a Saitek driver issue.
In the Windows Device Manager, the “Programmable Root Enumerator” has a yellow warning triangle next to it, and is complaining that the driver is unsigned or corrupt. I’m assuming this isn’t normal. I tried uninstalling all the software and drivers, and reinstalling, using the latest software downloaded from Saitek’s website, but have the same problem. I also tried manually uninstalling all the Saitek-related drivers from the Device Manager before reinstalling but this didn’t help. I don’t know what to try next.
-
Thanks Scuby!
I tried viewing the button presses in Notepad, and found that this doesn’t work, although the button presses do work within the grid matrix in the SST tool. ( I made sure that the X52-BMS profile was selected within the taskbar menu. ) So this appears to be a Saitek driver issue.
In the Windows Device Manager, the “Programmable Root Enumerator” has a yellow warning triangle next to it, and is complaining that the driver is unsigned or corrupt. I’m assuming this isn’t normal. I tried uninstalling all the software and drivers, and reinstalling, using the latest software downloaded from Saitek’s website, but have the same problem. I also tried manually uninstalling all the Saitek-related drivers from the Device Manager before reinstalling but this didn’t help. I don’t know what to try next.
Indeed looks like something is wrong with your drivers. Make sure you have the latest and correct drivers for your windows version. Before executing, right click and try run as administrator.
Here is how the device managers looks on my side:
]’
Maybe virusscanner needs deactivation? Try another USB port?
Hope you get it running mate!
Scub
-
Thanks for this latest profile Scub.
-
Indeed looks like something is wrong with your drivers. Make sure you have the latest and correct drivers for your windows version. Before executing, right click and try run as administrator.
Here is how the device managers looks on my side:
Maybe virusscanner needs deactivation? Try another USB port?
<…>
Hope you get it running mate!Scub
I got in touch with Saitek support. They told me to uninstall the drivers and software and reinstall everything with Windows Update disabled. This seems to have worked. It appears that there’s a clash between the Microsoft drivers and the drivers supplied by Saitek. Apparently, turning off Windows Updates stops Windows from pulling in a Microsoft driver. Now the BMS profile is working correctly.
Thank you for your help, and for sharing the great profile
Rob
-
Thanks for sharing that important piece of information!
Hope you like the profile.
I’ll be uploading an updated version soon, which will include the Paddle Switch to the flightstick. Up to now I haven’t found much use for it, so now I better add it.
Cheers,
Scub -
Update Sep/21/2015:
-Updated X52PRO driver version: 7.0.40.9
-Added the Paddle Switch (AP disconnect)
-Added some ICP functions to NUMPAD keys in BMS Keyfile
-Moved one or two functions to different keyboard keys in BMS Keyfile
-Re-assigned TrackIR CENTER to: ALT + F7
-Re-assigned DWVAC TOGGLE to: L-CTRL + NUMPAD -Installation:
Download the updated package (.rar) here: http://bit.ly/scubyflying (Refresh the download page).
Replace the .pr0 file into your Saitek SST software.
Replace the .key file into BMS.
Don’t forget to update keys in TrackIR and DWVAC.Cheers,
Scub -
Scuby is there a chance(just saying maybe) you have a same profile for the X52?? Looks awsome in X52Pro by the way…
-
Scuby is there a chance(just saying maybe) you have a same profile for the X52?? Looks awsome in X52Pro by the way…
Hi!
I believe that the software and profile for X52 is different than the Pro, so I expect that profiles are not interchangeable. Maybe someone can recreate it? I do not own a X52.
Good luck!
Cheers
Scub -
I just got back thanks to BMS 4.33 and found your profile, aparently I can’t figure out how to get a Radar Lock.
I slew the cursor onto the target and what do I have to press then? Haven’t found the right key on the HOTAS to lock the target -
I just got back thanks to BMS 4.33 and found your profile, aparently I can’t figure out how to get a Radar Lock.
I slew the cursor onto the target and what do I have to press then? Haven’t found the right key on the HOTAS to lock the targetTMS up
TMS down = drop target, which would be your next question I guess