Saitek X-52 Profile
-
Is it possible to have the Range knob actully do the CNTRL F4 and F3 buttons instead. I would like to use that Rotary knob to be able to zoom in and out the T-Pod. I thought i could just remap the key with the profile editor but it worked at first, but then i also noticed it kept changing the Gain on the left MFD. Making it extremly white. .
The Rotary 1, (without pinky), aka Range Knob, should already work as the TGP zoom.
.Pinky+Rotary 1 should be Sensor GainAlso was wandering if fire button A could be changed so that it cycles AA mode. I have Fire B cycling A-G mode but A wont change, just reverts back to centering my TrackIR.
That is because you need to set it to “unprogrammed” in the SST software, then assign it in-game.
Just so you know, the ICP is mimicked on the NumPad for this profile, along with A-A mode and A-G mode, which are, (respectively), the asterisk(*) and minus(-) buttons on the NumPad
-
@Hard~Deck:
The Rotary 1, (without pinky), aka Range Knob, should already work as the TGP zoom.
.Pinky+Rotary 1 should be Sensor GainThat is because you need to set it to “unprogrammed” in the SST software, then assign it in-game.
Just so you know, the ICP is mimicked on the NumPad for this profile, along with A-A mode and A-G mode, which are, Respectively), the asterisk(*) and minus(-) buttons on the NumPad
yes i actully figured this out after i reinstalled your profile…
But i can’t seem to get the TGP to lock into point mode with TMS up. Works fine in FCR in A2A mode. Is this intentional? or am i missing something
-
hey Hard do you know what may be causing your profile to not allow me to lock something up in point mode in the TGP. I can go into area mode but i can not press TMS up again to lock it into point mode.
On the air to air radar i can lock things up fully though. Any reason this might be?
-
here’s some handy info for transiotioning from X52 to X52 pro software:
use your old profiler that came with the X52 to profile the .dat file. Then it’ll create a .pr0 file.
This pr0 file doesn’t function completely in the new software, but you can load it.
Then you’ll find that all the functions are still as they were, i.e. the names and key-callbacks.
You’ll only have to select them from the right-click menu and put them in the right boxes for the buttons you want to assign them to.So, if you profiled it once, (more than) half the work is done, and you can enjoy your X52 pro in no-time.
I don’t know if it works the other way around, though.
@Sirbum: the TGP is not perfect in BMS. Point lock will only be possible when the contrast is high enough.
For me, it mostly works on vehicles, but not on buldings. The maverick has no problem finding the ‘hot spot’ on buildings though… (this is an area in the middle of the bottom of the building.)
-
Ok, need some help here please….
1. I definitely have a X-52 (not a Pro).
2. My BMS install is located in “C:\Falcon_BMS_4.32”
3. I placed the “BMS X52 HD.key” file in “C:\Falcon_BMS_4.32\User\Config” and it DOES show up in the sim setup.
4. I placed the “BMS X52 HD.pr0” file in “C:\Users\Public\Documents\Saitek SD6 Profiles” and it does show up Saitek profile application in the system tray. I have it set as the default profile upon bootup.
5. I am running Saitek driver version 6.0.4.1 and software version 7.0.2.7 (according to Saitek X52 Flight Controller) and these are the latest versions available for my PC which is a Windows 7 64-bit platform. I confirmed my installed software is for the 64-bit version of Windows 7.
6. I have selected the “BMS X52 HD.key” file for my controller keymap and applied it in BMS.
7. I’ve gone through the advanced controller options, per Hard Deck’s instructions, and set them accordingly.
Heres the problem. When I am in the sim I am not getting most of the functions shown in the “BMS X52 HD.png” image. For example, according to the supplied picture, when I press the Clutch Button on Rotary 2 on the Throttle I should get PTT on Teamspeak (yes I have Teamspeak3 set for PTT=Scroll Lock like the Saitek profile is set up for). But I don’t get that behavior. Instead, when I press the Clutch Button, the light in Rotary 2 (on throttle) blinks on & off AND ALSO the light on POV1 (joystick) blinks at the same time. Another example of the problem is when I press the Fire C button I should get Chaff/Flare but I’m not (yes I am set to Program 2 and my EWS was programmed before flight via the DTC). I’ve checked the in-sim settings and it shows “No assignment” in the key file. I then checked the assignment in the Saitek profile and it shows no assignment for the Fire C button so I am at a loss.
Any ideas on what’s wrong or what am I missing?
Thanks for any input in advance…
EDIT: Ok, I re-read Hard Decks first post and realized I hadn’t de-selected “the Clutch Settings in the MFD Tab of the Saitek Control Panel”. So I did that and it fixed my Clutch Button problem. But I still can’t do other functions as shown by the supplied image, e.g., chaff/flare.
-
Kneejo, thank you for trying to help Sirbum69. I hadn’t answered because I am still not that familiar with the mechanisation of the TGP just yet.
Sherlock, haven’t we flown AF together in the past? (not sure if there is more than one Sherlock)
Everything in Primary, (mode 1), that is not showing as programmed in the SST software, was mapped directly in-game….however, I have experienced, on occasion some commands somehow becoming un-mapped. I have absolutely no idea why. You can re-map it by locating the appropriate command in the Falcon BMS EXE / Setup /Controllers / commands list in the UI, then click on the command so that it turns blue, then press the button C on the side-stick.
I hope this works for you…. if not, let me know and I will be more than happy to help.
-
@Hard~Deck:
Kneejo, thank you for trying to help Sirbum69. I hadn’t answered because I am still not that familiar with the mechanisation of the TGP just yet.
Sherlock, haven’t we flown AF together in the past? (not sure if there is more than one Sherlock)
Everything in Primary, (mode 1), that is not showing as programmed in the SST software, was mapped directly in-game….however, I have experienced, on occasion some commands somehow becoming un-mapped. I have absolutely no idea why. You can re-map it by locating the appropriate command in the Controllers UI commands list, then click on the command so that it turns blue, then press the button C on the side-stick.
I hope this works for you…. if not, let me know and I will be more than happy to help.Hi HD,
Yes, I am the Sherlock from AF days. Thanks for making your profile available for the X52.
What I don’t understand is how, when I reload the “BMS HD X52.key” profile from a fresh download that the Fire C button still shows as having no function assigned.I am sure there are other functions not working but I am at work and don’t know them off the top of my head. I’ll post the more when I get time to get back to things at home.
-
thanks knee. Though i thought the problem i was having was on aircraft. I would have thought i could have locked those up. Ill try some more and see what happens. Otherwise i guess it really is not that big of a deal as i can still hit things in area mode, it just causes the cursor to move while you fly over the object and go around for a pass.
-
Any luck yet Sherlock?
-
@Hard~Deck:
Any luck yet Sherlock?
No luck with it. I don’t know what is wrong. I’m moving on to look at other profiles.
-
HD,
as we discussed, here is a little more on my problem:I have loaded the .key file in BMS and clicked “Apply”:
The “BMS X52 HD.key” file doesn’t assign anything for flares and assigns “Shift 0” for chaff:
I select the “BMS X52 HD” profile in my Saitek software (in fact, it is running as the only profile and the default on bootup):
My version of Saitek software and driver version (on Windows 7 64-bit):
I have de-selected the clutch mode as previously discussed so my teamspeak is working now:
But the Saitek profile shows nothing for mode 1 for the Fire C button. It should show “chaff/flare” release according to the image provided with your profile.
That is one example of a keystroke not working from the profile. When I get time I will try to post another one.
-
Fire C wont show anything in the profiler software because he did not profile it there. All the keys that work on mode 1 are done inside BMS itself. Another words if you look in the SST software all the keys on mode one should say not programmed or its unprogrammed. Anyways i just checked my version of Harddecks and mine also does not have anything for Fire C, but in the game it does drop what ever program i have up for EMS.
So in BMS under you keys, when you click on the Fire C button it should show ems something or fire chaff/flares…If it doesnt then all you need to do is map it in the game like you would any other Joystick.
He did this on purpose cause he felt it made it easier.
-
Fire C wont show anything in the profiler software because he did not profile it there. All the keys that work on mode 1 are done inside BMS itself. Another words if you look in the SST software all the keys on mode one should say not programmed or its unprogrammed. Anyways i just checked my version of Harddecks and mine also does not have anything for Fire C, but in the game it does drop what ever program i have up for EMS.
So in BMS under you keys, when you click on the Fire C button it should show ems something or fire chaff/flares…If it doesnt then all you need to do is map it in the game like you would any other Joystick.
He did this on purpose cause he felt it made it easier.
So shouldn’t it show up in the “BMS X52 HD.key” file in the setup screen for controllers then? As you can see in my 2nd picture it is not there.
-
Maybe he uses “drop programmed” callback and that might not be in the keyfile, then it won’t show in setup but it will work in game.
Cheers
-
EDIT:
Sherlock, here are some screenshots for comparison…
-
Following is a list of X52 INPUT(s) and the commands that should corrospond with them underneath
the key assignment list in the setup/controllers UI shown in the picture bove….Side Stick
B = Button 4 - Pinky Switch(FOV)
D = Button 7 - Left-OSB-7
E = Button 8 - UnCageT1 = Button 9 - Master Arm On
T2 = Button 10 - Master Arm Safe
T3 = Button 11 - Ext Lights Toggle
T4 = Button 12 - Lights Flash / Steady
T5 = Button 13 - Instrument Lights
T6 = Button 14 - Flood ConsolesPOV1 = DMS Up, Right, Down, Left
POV2
Button 16 - TMS Up
Button 17 - TMS Right
Button 18 - TMS Down
Button 19 - TMS LeftThrottle
POV3
Button 20 - UHF
Button 21 - IFF In
Button 22 - VHF
Button 23 - IFF Out -
After spending a few hours with Inquisitor dealing with a similar issue, it turned out that his drivers and software were out dated. However, installing new software and drivers did not work. He had to un-install both and delete everthing related to Saitek from the registry. Once that was done and he reinstalled his drivers and software everything worked perfectly.
-
@Hard~Deck:
After spending a few hours with Inquisitor dealing with a similar issue, it turned out that his drivers and software were out dated. However, installing new software and drivers did not work. He had to un-install both and delete everthing related to Saitek from the registry. Once that was done and he reinstalled his drivers and software everything worked perfectly.
So you think Inquisitor’s issue is similiar to mine too? Is he running Windows 7 64-bit like I am?
-
Hey Sherlock, what a bear it was troubleshooting this bugger. In BMS if I clicked on a button it should tell me what is assigned to that button and it wasnt for a ton of them. In the profiler if I hit a button the profiler would light up but I got random response from the config tester in the SST software. This was happening with any of the profiles I tried using, sooooo I uninstalled the SST software and saitek drivers cleaned the registry of everything saitek, downloaded fresh drivers and softwareand Viola! everything came up. And yes I am running Win7 64
-
So you think Inquisitor’s issue is similiar to mine too? Is he running Windows 7 64-bit like I am?
Could be…
I would go over post’s 19-20 first, just to be sure.