Saitek X-52 Profile
-
@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.
-
@Hard~Deck:
Could be…
I would go over post’s 19-20 first, just to be sure.OK, it’s stump the dummy time. :O)
I see in your first picture (in post 19) that you have circled the “Fire” button in red and show it as “Unprogrammed” in the “Click to add shift command” selection to the right (in the profile editor). But I can’t figure out how to set the shift selection for EACH button Differently. My profile doesn’t have the “Unprogrammed” selection checked but when I select it and go on to the next button (e.g., “Fire C”) then the “Unprogrammed” selection is there for that button.
-
Are you calling me a DUMMY?
I’m not sure exactly what you mean…:-(
Are you saying it won’t let you place a check mark next to “Fall Back”?
I am going to jump on the 69th TS for a bit…I have to leave soon, but if you can jump on before then,
maybe I can help you out real quick.Otherwise, I can meet you around 9pm Pacific.
PM Sent.
-
Hey hard, real quick question for you. On your profile you have the Cat-1/cat-3 set to mode 2 and three. How would i go about changing that so that when im in mode 2 it will cycle my next steer point and when im in mode 3 it cycles backwards through the steer points.
Because i dont use the cat1/3 thing at all, i just click that in the cockpit itself.
-
Mode 2 is empty…
The commands for steerpoint increse/decrease are Page Up/Page Down respectively.
No need for an advanced command, just go into the SST and assign them where you want.
-
Hey Hard~Deck,
I think I found what was causing the problem. See this thread: https://www.benchmarksims.org/forum/showthread.php?8742-Thrustmaster-MFDs-may-cause-conflict-with-X52 -
Hard~Deck I downloaded your profile and installed it, went through all your pics of settings, loaded the keyfile but a lot of the keys are still unassigned. Do you have to go through and assign all the buttons in the setup menus in BMS? I already did the CMS, DMS, and TMS hats but there are a lot still not working. I don’t have track ir or cougar mfd’s. Also having some trouble locating some of the keys in the setup menu. Thanks for the profile it looks really good!
Edit: I also assigned the three rocker switches at the base of the throtle. Still have several on the stick and throttle to assign.
-
PM me and let me know when ou’re available to jump on Teamspeak.
I’ll do the best I can to help.
-
I’m having a bit of a problem here. there is no way i can Lock on \ off a target…
-
Make sure you have “BMS HD Final.pr0” loaded in your Saitek Profiler…also make sure you load the “BMS HD Final.key” loaded in the Setup/Controllers UI in Falcon.
One by one, go through and test TMS up, down, left, and right buttons to verify the assignments match the button mapping image that came with the download.