Saitek X-52 Profile
-
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.
-
I sent you a PM. Furthermore, I just noticed that if I press the mousewheel button on the controller it activates the RF cycle, which is mapped to ctrl+r in the keyfile. However, according to the profile it should press the home button (radar stdby), so there seems to be some discrepancy between the button the SST is supposed to activate and the one it actually activates?
-
thank you
-
Hey, Thanks KesMonkey and Viking for making these setups and profiles for the X52!
My problem seems to be that my mouse stick on the throttle does not work as a slew button for my radar, and it acts differently from time to time it seems, sometimes it does nothing, and sometimes it just functions as a mouse ingame. Regardless, it never actually lets me slew the radar.
I have disabled the clutch function trough windows, but im wondering if the clutch function in the Proflight X52 profile program might have something to do with this?
Or if theres some settings i need to fix within the Profile software itself.
Any help would be much appreciated. -
Hey, Thanks KesMonkey and Viking for making these setups and profiles for the X52!
My problem seems to be that my mouse stick on the throttle does not work as a slew button for my radar, and it acts differently from time to time it seems, sometimes it does nothing, and sometimes it just functions as a mouse ingame. Regardless, it never actually lets me slew the radar.
I have disabled the clutch function trough windows, but im wondering if the clutch function in the Proflight X52 profile program might have something to do with this?
Or if theres some settings i need to fix within the Profile software itself.
Any help would be much appreciated.I would suggest downloading the file from post 356 again then following the readme exactly. If that doesn’t fix it let me know and we will try to figure it out.
-
It didnt fix it.
I will troubleshoot some more and get back to you if i cant find any solution. -
It didnt fix it.
I will troubleshoot some more and get back to you if i cant find any solution.If you open the .pr0 file in the profiler, does it say the Ministick X and Y axis are configured as bands?
-
EDIT: Yes both “Ministick X axis = Bands” and “Ministick Y axis = Bands”
-
Allright, i got it working, i had to adjust my deadzones on the mouse stick within the control panel.
Thanks for all the help guys! this is a really great community! -
Allright, i got it working, i had to adjust my deadzones on the mouse stick within the control panel.
Thanks for all the help guys! this is a really great community!Glad you got it to work mate! Happy flying
-
And now i cant get my ministick to slew the radar anymore.
Within the Falcon BMS X-52.Pr0, the following lines say:
[axis=0x00050024 name=‘Ministick X Axis’]
[axis=0x00050026 name=‘Ministick Y Axis’]]Then further down i have:
[axis=0x00050024 role=bands
[mouse-x=15]
[bands
[band=40 command=425a93e2-34f2-4023-8ca9-910cc2eb4081]
[band=60]
[band=100 command=0e319f29-4484-449d-984d-fedb13342447]]]
[axis=0x00050026 role=bands
[mouse-y=15]
[bandsDoes this look correct?
I had it working before the summer, than when i came back home i couldnt get it to work. ive done the whole process several times and cant get it to work. I feel like BMS doesnt want to pick up on the fact that the Saitek software has the ministick x\y axis translated into F8-11. And ingame if i press the F8-11 keys the radar slews, but the ministick wont work.
Ive also fiddeled around with the deadzones on the ministick, but it does not work.Any help?
-
Thank you for this profile, I have been using it all summer to learn the game. Its fantastic.
One problem I have run into is that the wheel mouse button 2 is not increasing or decreasing my radar ranges. I checked the controller and everything is functioning well. Any ideas? For now I’m just using the mouse to click on the appropriate cockpit buttons.
Another problem is that rotarty 2 is not adjusting my Hud brightness.
Thanks,
Scott
-
Thank you for this profile, I have been using it all summer to learn the game. Its fantastic.
One problem I have run into is that the wheel mouse button 2 is not increasing or decreasing my radar ranges. I checked the controller and everything is functioning well. Any ideas? For now I’m just using the mouse to click on the appropriate cockpit buttons.
Another problem is that rotarty 2 is not adjusting my Hud brightness.
Thanks,
Scott
The precision slider is HUD brightness and the rotary is TGP zoom. For the FRC range, load your pr0 and roll the scroll wheel and see what it says in SST. I believe the devs removed the callback for FCR range inc/dec. If so and you don’t like to walk the cursor to the next range like IRL, then bind osb 19 and 20 to scroll up and scroll down. I no longer have an X52 hooked up. Let me know how the range works out.
-
And now i cant get my ministick to slew the radar anymore.
Within the Falcon BMS X-52.Pr0, the following lines say:
[axis=0x00050024 name=‘Ministick X Axis’]
[axis=0x00050026 name=‘Ministick Y Axis’]]Then further down i have:
[axis=0x00050024 role=bands
[mouse-x=15]
[bands
[band=40 command=425a93e2-34f2-4023-8ca9-910cc2eb4081]
[band=60]
[band=100 command=0e319f29-4484-449d-984d-fedb13342447]]]
[axis=0x00050026 role=bands
[mouse-y=15]
[bandsDoes this look correct?
I had it working before the summer, than when i came back home i couldnt get it to work. ive done the whole process several times and cant get it to work. I feel like BMS doesnt want to pick up on the fact that the Saitek software has the ministick x\y axis translated into F8-11. And ingame if i press the F8-11 keys the radar slews, but the ministick wont work.
Ive also fiddeled around with the deadzones on the ministick, but it does not work.Any help?
You should edit the pr0 within SST. Open SST and move the ministick. Does it show it is bound to f8-f11?
-
Yes, if i slew the F8-11 keys light up.
-
Only use these files and follow these directions only. I doing this does not work let me know.
The read me is included in the zip. Here is the HOTAS mapping.