Saitek X-52 Profile
-
Thanks for the kind words guys.
And, a really big thank you to nomis for offering tech support while I was out having a few drinks. Friend request incoming mate! -
No problem buddy. “A few drinks” sounds fair…we deserve it
Friendship request accepted. Thanks!! -
Finally got it! It works. The problem was another joystick that was connected to my computer! Stupid me! I’ve should had figured it out earlier! Thanks anyway for your quick replies!
-
No, but you can free up a button fairly easily. I’d recommend unmapping the mouse wheel click (Radar standby & GM radar snowplow toggle), as these functions aren’t found on the real HOTAS anyway. Use wordpad to open whichever keyfile you use (BMS Saitek X-52.key or No TrackIR BMS Saitek X-52.key). You’ll see a list of all the keymappings. Near the bottom of the list, you’ll find the following two lines: SimRadarStandby 31 -1 -2 0 0x0 0 and SimRadarSnowplow 287 -1 -2 0 0x0 0. Delete both of those lines and save. Now, just map the mouse wheel click within TeamSpeak and you’re done.
Excuse the Noob question, I kind of have an Idea of how the mapping works, but what I can’t still grasp is how do I would know what number (in this case the 31 after SimRadarStandby) goes to what button on the joystick? (I am used to create the profiles from within the saitek editor but seems that these way works better…)
Great work on the profile by the way!!
Thanks
MSTNG
-
Still one question: where’s the button for dropping chaff and flares? Or it’s not mapped?
-
Still one question: where’s the button for dropping chaff and flares? Or it’s not mapped?
cms-up = programs 1-4 chaff/flares (hat-2 on stick with pinky held more than 0,5sec)
cms-left = chaff (hat-2 on stick with pinky held more than 0,5sec)
cms-down = ecm on (hat-2 on stick with pinky held more than 0,5sec)
cms-right = ecm off (hat-2 on stick with pinky held more than 0,5sec)
slap-switch = flare (fire d on the throttle with pinky held more than 0,5sec)Kalle
-
You can remap it from Falcon’s control setup screen. If you’re not sure how to do that, let me know.
Ok I figured that out. Ok now I’m trying to setup a key for Team Speak that isn’t being used, I was using Scroll lock but that seems to be warning light ack now. Is there any way to map say the IFF in or OUT on the HAT switch to something else that isn’t in use so I can map that for a push to talk key in TS? Thanks.
-
Hey guys. I guess I’m just an incompetent boob, but I just can’t get this profile to work. After perusing all eleven pages of this thread I still can’t put my finger on what I’m doing wrong. I downloaded the most recent update from mediafire yesterday, and have made sure I have the most current Saitek drivers and software. I unzipped the folder and placed the No TrackIR key file, BMS Saitek X-52.key (I hope the wife is getting me TIR5 for Christmas), axismapping.dat, and joystick.cal in the config folder. Then I placed the falcon BMS X-52.pr0 file in my profile directory and loaded it. Once I booted up BMS I loaded the No TIR X-52 key file but no matter which button I push on the stick or throttle none of them are associated with any command. I loaded the other Saitek X-52 key file, but still no luck. The only two commands that function are the radar range on the scroll wheel, and the radar cursor, which I know are done via the Saitek profile. I had to assign each axis manually as well, but that wasn’t that big of a chore. The only two things I haven’t done per the instructions is disable the clutch button, or enter the two lines for the pinkie switch in the config file (not a boycott of those instructions, just neglected to do them). Neither of which I would think would hinder the non shifted functions from working on the stick.
Also, just for information the only other peripheral I have connected to my PC are my CH Pro Pedals.
If I have time tonight I will reload the key files again for the third time and see what happens. I’ll also make sure to disable the clutch and insert the pinky switch lines this time. I’m expecting no joy however.
Any ideas? Thanks.
-
Finally got it! It works. The problem was another joystick that was connected to my computer! Stupid me! I’ve should had figured it out earlier! Thanks anyway for your quick replies!
Nice one!
-
Excuse the Noob question, I kind of have an Idea of how the mapping works, but what I can’t still grasp is how do I would know what number (in this case the 31 after SimRadarStandby) goes to what button on the joystick? (I am used to create the profiles from within the saitek editor but seems that these way works better…)
Great work on the profile by the way!!
Thanks
MSTNG
From the Falcon BMS setup screen, you can click any button on your joystick, and the button number will display on screen. The thing is though, that Falcon BMS numbers the buttons from 1-32, but DirectX assigns the ID numbers 0-31. So, the Trigger First Detent is button 0 as far as DirectX is concerned, but to Falcon BMS, it’s button 1.
Cheers. -
Ok I figured that out. Ok now I’m trying to setup a key for Team Speak that isn’t being used, I was using Scroll lock but that seems to be warning light ack now. Is there any way to map say the IFF in or OUT on the HAT switch to something else that isn’t in use so I can map that for a push to talk key in TS? Thanks.
There is, but keep in mind that the IFF IN & OUT mappings are essential for successful operation of the Datalink, and are part of the real HOTAS. I’d recommend ummapping the mouse-wheel-click, as Radar Standby Toggle isn’t something that appears on the real HOTAS.
Here’s how to unmap a button.
Open the keyfile you use with wordpad.
If you want to remove the mapping for SimRadarStandby, search for the line SimRadarStandby 31 -1 -2 0 0x0 0 and delete it and save.
If you want to remove the mappings for IFF IN & OUT, search for the following two lines SimCommsSwitchRight 20 -1 -2 0 0x0 0 and SimCommsSwitchLeft 22 -1 -2 0 0x0 0 and delete those and save.
Now you’re free to map within Teamspeak. -
Hey guys. I guess I’m just an incompetent boob, but I just can’t get this profile to work. After perusing all eleven pages of this thread I still can’t put my finger on what I’m doing wrong. I downloaded the most recent update from mediafire yesterday, and have made sure I have the most current Saitek drivers and software. I unzipped the folder and placed the No TrackIR key file, BMS Saitek X-52.key (I hope the wife is getting me TIR5 for Christmas), axismapping.dat, and joystick.cal in the config folder. Then I placed the falcon BMS X-52.pr0 file in my profile directory and loaded it. Once I booted up BMS I loaded the No TIR X-52 key file but no matter which button I push on the stick or throttle none of them are associated with any command. I loaded the other Saitek X-52 key file, but still no luck. The only two commands that function are the radar range on the scroll wheel, and the radar cursor, which I know are done via the Saitek profile. I had to assign each axis manually as well, but that wasn’t that big of a chore. The only two things I haven’t done per the instructions is disable the clutch button, or enter the two lines for the pinkie switch in the config file (not a boycott of those instructions, just neglected to do them). Neither of which I would think would hinder the non shifted functions from working on the stick.
Also, just for information the only other peripheral I have connected to my PC are my CH Pro Pedals.
If I have time tonight I will reload the key files again for the third time and see what happens. I’ll also make sure to disable the clutch and insert the pinky switch lines this time. I’m expecting no joy however.
Any ideas? Thanks.
My first guess would be that your CH Pro Pedals is set as Window’s preffered joystick (it has ID number 0). The simplest way to test would probably be to run Falcon with your pedals unplugged. If you unplug your pedals, before you run Falcon, re-copy axismapping.dat and joystick.cal from my zip file to Falcon’s config folder first, as these files may have been overwritten by Falcon. Now run the game and see if the buttons are responding. Let me know how this goes for you, we’ll get to the bottom of it.
p.s. Sorry for the late reply by the way, I haven’t logged in for a few days. I’ll keep an eye out for your response.
-
cms-up = programs 1-4 chaff/flares (hat-2 on stick with pinky held more than 0,5sec)
cms-left = chaff (hat-2 on stick with pinky held more than 0,5sec)
cms-down = ecm on (hat-2 on stick with pinky held more than 0,5sec)
cms-right = ecm off (hat-2 on stick with pinky held more than 0,5sec)
slap-switch = flare (fire d on the throttle with pinky held more than 0,5sec)Kalle
Thanks for the help Kalle. I know that it depends on how your Data Cartridge is set up, but I think that by default the slap switch drops 1 flare and 1 chaff bundle. Maybe I set that myself, I can’t remember.
-
My first guess would be that your CH Pro Pedals is set as Window’s preffered joystick (it has ID number 0). The simplest way to test would probably be to run Falcon with your pedals unplugged. If you unplug your pedals, before you run Falcon, re-copy axismapping.dat and joystick.cal from my zip file to Falcon’s config folder first, as these files may have been overwritten by Falcon. Now run the game and see if the buttons are responding. Let me know how this goes for you, we’ll get to the bottom of it.
p.s. Sorry for the late reply by the way, I haven’t logged in for a few days. I’ll keep an eye out for your response.
No problem Kes, thanks for getting back to me and for all your hard work setting up this great profile. I should hopefully be able to test this out tonight, and I already have a suspicion that you are right on about the problem.
Thanks again, and I’ll let you know how it turns out.
-
Well, the pedals were definitely the problem. Once I unplugged them and booted the sim the profile worked perfectly. I closed out BMS and plugged the pedals back in, went to windows control panel and made sure the X-52 was the preferred controller, then ran dxdiag and confirmed that the X-52 is controller 0, and the pedals set as 1. I rebooted the sim with both plugged in and it went right back to not recognizing any X-52 button commands. Long story short, all is good without the pedals attached, but I sure would like to use them :(.
-
Got it all sorted, unmapped the wheel click and mapped it to numlock for ts. Thanks.
-
Well, the pedals were definitely the problem. Once I unplugged them and booted the sim the profile worked perfectly. I closed out BMS and plugged the pedals back in, went to windows control panel and made sure the X-52 was the preferred controller, then ran dxdiag and confirmed that the X-52 is controller 0, and the pedals set as 1. I rebooted the sim with both plugged in and it went right back to not recognizing any X-52 button commands. Long story short, all is good without the pedals attached, but I sure would like to use them :(.
I have a similar situation myself. I have Saitek rudder pedals and Cougar MFDs, and Falcon doesn’t see my X-52 as the first joystick. I’ve tried a 3rd party app that claims to rearrange Window’s joystick ID numbers, but it doesn’t make a difference, Falcon always sees my X-52 as the third joystick.
Okay, here’s what it means. You’ll need to map each axis yourself from within the sim. As well as that, I’ll edit a key file for the button mappings, and PM it to you. Which version of the keyfile do you use? -
Got it all sorted, unmapped the wheel click and mapped it to numlock for ts. Thanks.
No problem. Glad you’re sorted.
-
I have a similar situation myself. I have Saitek rudder pedals and Cougar MFDs, and Falcon doesn’t see my X-52 as the first joystick. I’ve tried a 3rd party app that claims to rearrange Window’s joystick ID numbers, but it doesn’t make a difference, Falcon always sees my X-52 as the third joystick.
Okay, here’s what it means. You’ll need to map each axis yourself from within the sim. As well as that, I’ll edit a key file for the button mappings, and PM it to you. Which version of the keyfile do you use?You’re the man Kes, thanks for your help! As of now I’m using the No Track IR keyfile, but after Christmas I hope to have a TIR5 so I guess eventually I’ll need both.
Again, thank you for this great profile and the tech support you are providing for everyone.
-
First off, thanks KesMonkey for your work and support on this.
I’m going to work on my own for the X52 Pro, and had a question to anyone: the profile here uses DirectX buttons in BMS, with very little mapped in the Saitek software. Is doing it this way – as opposed to mapping everything in the Saitek software to keyboard presses that match the default BMS keys – preferred somehow (e.g. latency or other reasons)?
thanks!