Saitek X-52 Profile
-
Viking is helping everyone, even foreigners like me, and he did nothing but good work not opening a new thread! We own this guy a lot for his time and patience with new pilots and noobies. Viking has tons of free beers in Rio. Thanks for help bro!
+1, for all the same reasons above. Thanks a lot for the update, Viking.
With best regards,
-
I’m using the no Trackir profile and I’m not getting any input detected from the pinky switch, I’ve copied and pasted the two lines of code into the .config file and disabled clutch mode, and still nothing. Am I missing something?
-
I’m using the no Trackir profile and I’m not getting any input detected from the pinky switch, I’ve copied and pasted the two lines of code into the .config file and disabled clutch mode, and still nothing. Am I missing something?
When you fly you are not getting the expanded views in the MFD’s and shifting is not working?
The no TrackIR profile has not been updated to 4.33.1. I am not sure if it will work. If you want to use the updated profile for TrackIR then modify it to fit then I can help. Post #356
-
Do I edit the .key file to remap the radar cursor up, down, left, and right keys?
I’d like to keep the TIR keys at the default. Has anyone else already done this?
-
You can map the up, down, left, right keys to the radar slew but you cannot use shift or any other modifier. You then have to go into SST and change the keys to the ones you changed to in the key file. You will lose the ICP commands on the arrow keys, but you can do without them or map them somewhere else.
-
You can map the up, down, left, right keys to the radar slew but you cannot use shift or any other modifier. You then have to go into SST and change the keys to the ones you changed to in the key file. You will lose the ICP commands on the arrow keys, but you can do without them or map them somewhere else.
Modifiers work ok if using old saitek drivers. I posted about it a few days ago. Anyway, the easy option is indeed binding to single keystrokes. I’m using shift-arrows because they’re default, don’t cause any conflict and I don’t loose any functionality. Fully DX here…profile is just for tdc.
Enviado de meu LG-D802 usando Tapatalk
-
Thanks for the replies. Is it possible to map everything just using the Saitek software or is there some kind of limitation that I’ll run into if I do that.
-
Thanks for the replies. Is it possible to map everything just using the Saitek software or is there some kind of limitation that I’ll run into if I do that.
Better to avoid it, 'cause SST software is famous for the conflicts with other software for example Teamspeak settings…Make sure the hotkeys are set at “mouse and keyboard only” and not the default, or it’s 90% sure you’ll be facing pitch down issues in MP flight
-
I changed the radar cursor keys to another set of keys in BMS. Then I updated the SST software with the new set of keys.
The radar cursor moves (GOOD) but won’t stop moving (BAD) when I release the mini-stick.
Any ideas on what I did wrong?
-
You probably did nothing wrong. You just hit one of the many Saitek problems. Read this thread.
This forum also might help you
-
Thanks I see you had a similar problem. I’ll try those drivers.
-
KesMonkey’s profile is awesome and in honor of his wonderful work on this profile that I am so grateful for, I have updated it for the 4.33 Basic Key File. Follow all the directions that KeysMonkey included in his profile and simply add these files instead of his key file and pr0. It is for TrackIR. I added cockpit sounds to most of the callbacks and changed a few buttons.
Here are the button changes:-Fire A which was Cycle AA Hardpoints is now Paddle Switch. If someone comes up with a better function please let me know.
-T1 is toggle gear. T1 Shifted is Eject.
-T2 is CAT toggle. T2 Shifted is Wheel Brakes. I got rid of parking brake because I found that if you use pinky switch to shift then apply brakes and release pinky shift while holding the wheel brake the brakes will stay on even after releasing all buttons. Please test and let me know and I can help you add a parking break if you like.
-T3 is “Waypoint” or Steerpoint increase. T3 Shifted is TGP zoom in.
-T4 is Steerpoint decrease. T4 Shifted is TGP zoom out.
-T5 is 3D cockpit. T5 Shifted is Look Closer.
-T6 is Weapon View. T6 Shifted is Combat Autopilot.Let me know if you think something needs to be added or moved around.
There are also a couple outdated callbacks that were changed or removed or maybe a new one was added, so I matched that function with the new cockpit callback.
I would appreciate it if people took the time to check if the sounds I added match the cockpit sounds, so if you feel like checking to see if the callback makes the same sound as the mouse click in the cockpit I would like to hear back about them.I take no credit for this profile I only updated it. All the credit for the profile goes to KeysMonkey. I would also like to thank Snelle for his awesome work on the X55 profile which helped me to learn a lot.
I hope this stokes some people up as much as KeyMonkey’s original profile did for me.
Also, if someone wants to give me the DX numbers for a X52 Pro I could try to modify this to work for it.
Thanks again KeysMonkey!
Update:
-The CAT toggle was mapped wrong. It is now fixed.
-The FCR range inc./dec. was mapped wrong. It is now fixed.
-The mouse nipple was not working and it cannot be mapped to a shifted button so I mapped it back to F8,F9,F10,F11. Be aware of TrackIR buttons as you were with the original profile.
-I had to change the Falcon BMS X52.pr0 file to get everything to match with the 4.33 key file and work correctly.
-I tested everything and it all functions as advertised. Please let me know if you find anything wrong or have any suggestions.First of all thanks to all who have contributed to this thread. I’ve been trying to wade through the waters to immerse myself in BMS but I’m having a hard time getting out of the gate so I apologize for what is probably a noob question. So here’s what I’ve done so far:
- Downloaded the zip file for the updated profile (Key’s updated BMS 4.33.1 X52).
- Extracted the axismapping.dat, joystick.cal, and Vikings BMS 4.33 U1 X52.key to the E:/FalconBMS4.33U1/User/Config folder
- Extracted the Falcon BMS X-52.pr0 file to my Saitek folder
- Activated the pro file and confirmed that it’s displaying Falcon BMS X-52 in the Mode 1 in the display window
- Loaded the Vikings BMS 4.33 U1 X52.key file in the game
The problem I’m running into is that many of the mapped buttons are not showing or functioning in game. DMS up/down/left/right work. TMS up/down/left/right aren’t showing mapped as are Fire buttons A,B,C. The trigger isn’t showing mapped either. T1-T6 buttons aren’t showing mapped. Oddly enough Radar range increase/decrease are showing mapped on wheel mouse button 2.
Rather than attempt to try and map all these buttons I feel like the answer is probably a simple one but I’m close to banging my head in frustration in trying to figure this out. On a side note I did have a Logitech G13 controller running when I installed BMS. It recognized that device as my default joystick. I plugged in the X52 and after searching this thread I determined the X-52 was listed as “1” in the priority of joysticks. Unplugged the G13 and if memory serves me correctly I did a check of making the X52 as priority over “older” games. Either way the X-52 now shows up as “0” in the priority of joysticks (and the G13 remains unplugged for the time being). I deleted my config folder and tried a fresh start with my backup config folder (hey I read the install notes to make a backup!!!) now knowing that my X-52 was the priority. And that’s where I’m at currently. So mostly non functional but functional in small bits. And since it’s mostly non-functional I haven’t even tried to mess with the pinky functions (yet). Any help would be greatly appreciated.
-
First of all thanks to all who have contributed to this thread. I’ve been trying to wade through the waters to immerse myself in BMS but I’m having a hard time getting out of the gate so I apologize for what is probably a noob question. So here’s what I’ve done so far:
- Downloaded the zip file for the updated profile (Key’s updated BMS 4.33.1 X52).
- Extracted the axismapping.dat, joystick.cal, and Vikings BMS 4.33 U1 X52.key to the E:/FalconBMS4.33U1/User/Config folder
- Extracted the Falcon BMS X-52.pr0 file to my Saitek folder
- Activated the pro file and confirmed that it’s displaying Falcon BMS X-52 in the Mode 1 in the display window
- Loaded the Vikings BMS 4.33 U1 X52.key file in the game
The problem I’m running into is that many of the mapped buttons are not showing or functioning in game. DMS up/down/left/right work. TMS up/down/left/right aren’t showing mapped as are Fire buttons A,B,C. The trigger isn’t showing mapped either. T1-T6 buttons aren’t showing mapped. Oddly enough Radar range increase/decrease are showing mapped on wheel mouse button 2.
Rather than attempt to try and map all these buttons I feel like the answer is probably a simple one but I’m close to banging my head in frustration in trying to figure this out. On a side note I did have a Logitech G13 controller running when I installed BMS. It recognized that device as my default joystick. I plugged in the X52 and after searching this thread I determined the X-52 was listed as “1” in the priority of joysticks. Unplugged the G13 and if memory serves me correctly I did a check of making the X52 as priority over “older” games. Either way the X-52 now shows up as “0” in the priority of joysticks (and the G13 remains unplugged for the time being). I deleted my config folder and tried a fresh start with my backup config folder (hey I read the install notes to make a backup!!!) now knowing that my X-52 was the priority. And that’s where I’m at currently. So mostly non functional but functional in small bits. And since it’s mostly non-functional I haven’t even tried to mess with the pinky functions (yet). Any help would be greatly appreciated.
PM sent.
-
-
With Viking’s help (much obliged) the issue at hand seems to be the G13 is taking the priority joystick ID. I’ve confirmed that by using a default keybinding list and when I pull the trigger (which would normally be button 1) it lists it as button 33. I’ve tried using JoyID but that didn’t seem to fix the issue. As a temporary solution I’ve disabled the G13 in the device manager but would welcome anyone’s input on making the X52 the primary input followed by the G13.
-
The profile I posted has TGP zoom in and out. T3 shifted and T4 shifted.
SimRangeKnobUp 266 -1 -2 0 0x0 0
SimRangeKnobDown 267 -1 -2 0 0x0 0If you want to change the button you change the numbers 266 and 267. When shifted you add 256 to the DX button.
SimRangeKnobUp 266 -1 -2 0 0x0 0 “MAN RANGE Knob - Up - TGP” “But.11”
SimRangeKnobDown 267 -1 -2 0 0x0 0 “MAN RANGE Knob - Down - TGP” “But.12”I’m confused by this. Why make them keypresses, taking up DX button space, when they can assigned as an axis in the UI advanced settings?
(Sorry if this has been asked/answered, haven’t read more recent posts yet …. I was just here to get a link to provide a referral.)
-
I’m confused by this. Why make them keypresses, taking up DX button space, when they can assigned as an axis in the UI advanced settings?
(Sorry if this has been asked/answered, haven’t read more recent posts yet …. I was just here to get a link to provide a referral.)
You would have to ask KeysMonkey about that, and I haven’t seen him respond here in a long while. He had the HUD brightness as the rotary instead. I used that when I updated the profile in case people wanted it similar to his. I changed it back to TGP zoom to make the key file as similar to the HOTAS as possible. This thread has both key files. The latest one has TGP zoom as a rotary.
-
-
I got my X52 yesterday and downloaded the updated version of Viking’s mapping. I added all files like KesMonkey described and changed them with the Viking version. However, my ministick is has no effect whatsoever in the game. When I go to the control panel for Saitek I can see the input for the ministick so it’s obviously not broken, but I can’t get it to have any effect in the game, making me unable to use my radar. Does anyone have any tips? Thanks in advance!
-
It sounds like SST and your keyfile are not matching. Start over and only use the files in post #356. Follow the instructions from the readme in post #356. If you are still having problems then let me know. You can also make sure the keyfile and SST are mapped to the same buttons. IIRC they should be F8,F9,F10 and F11.