X52 PRO Profile by Scuby
-
Thanks for sharing that important piece of information!
Hope you like the profile.
I’ll be uploading an updated version soon, which will include the Paddle Switch to the flightstick. Up to now I haven’t found much use for it, so now I better add it.
Cheers,
Scub -
Update Sep/21/2015:
-Updated X52PRO driver version: 7.0.40.9
-Added the Paddle Switch (AP disconnect)
-Added some ICP functions to NUMPAD keys in BMS Keyfile
-Moved one or two functions to different keyboard keys in BMS Keyfile
-Re-assigned TrackIR CENTER to: ALT + F7
-Re-assigned DWVAC TOGGLE to: L-CTRL + NUMPAD -Installation:
Download the updated package (.rar) here: http://bit.ly/scubyflying (Refresh the download page).
Replace the .pr0 file into your Saitek SST software.
Replace the .key file into BMS.
Don’t forget to update keys in TrackIR and DWVAC.Cheers,
Scub -
Scuby is there a chance(just saying maybe) you have a same profile for the X52?? Looks awsome in X52Pro by the way…
-
Scuby is there a chance(just saying maybe) you have a same profile for the X52?? Looks awsome in X52Pro by the way…
Hi!
I believe that the software and profile for X52 is different than the Pro, so I expect that profiles are not interchangeable. Maybe someone can recreate it? I do not own a X52.
Good luck!
Cheers
Scub -
I just got back thanks to BMS 4.33 and found your profile, aparently I can’t figure out how to get a Radar Lock.
I slew the cursor onto the target and what do I have to press then? Haven’t found the right key on the HOTAS to lock the target -
I just got back thanks to BMS 4.33 and found your profile, aparently I can’t figure out how to get a Radar Lock.
I slew the cursor onto the target and what do I have to press then? Haven’t found the right key on the HOTAS to lock the targetTMS up
TMS down = drop target, which would be your next question I guess
-
I dunno what I did wrong but now it works, thanks
I figured it would be TMS up as it’s the same in the A10C (DCS).
Anyway, works now! -
Update Nov/01/2015 for 4.33:
-Keyfile: Totally new keyfile based on the default “BMS - Basic.key” from 4.33;
-Profile: In Mode 2, the Throttle Slider has an auto-step VTOL-nozzle angle function for easier Harrier Operation;Installation:
Download the updated package (.rar) here: http://bit.ly/scubyflying (Refresh the download page).
Replace the .pr0 file into your Saitek SST software.
Replace the .key file into BMS.Cheers,
Scub -
Thank you Scuby!!
-
Thanks very much Scuby.
-
Hi and thanks for what you do for the community. Can you explain for a newbee like me how to install your profile. I own a x52 pro…. I tried to do by myself but when i put my 52 the green screen was off so i didnt insist.
Thanks again
Laurent -
Thanks Scuby!
-
Hi and thanks for what you do for the community. Can you explain for a newbee like me how to install your profile. I own a x52 pro…. I tried to do by myself but when i put my 52 the green screen was off so i didnt insist.
Thanks again
LaurentHi Laurent,
Loading a profile is simple. Start the Saitek Profiler software and find the menu where you can open/load the profile file from the download. After that make sure you click the button which activates the profile to your stick. You might want to test it too with the test button.
Hope that helps!
Cheers,
Scub -
Perfect combination, but it takes time to get used to it
-
Thanks for the profile, Scuby.
-
Scuby, I have a question about how you bound the VAC ARM to the POV hat 3 on the throttle. All I can see is that you added SimDoNothing -1 0 0X4A 2 0 1 0 “3RD: DWVAC Arm Voice Activation” which is ctrl num -. What I don’t understand is how you bound the POV hat 3 to ctrl num -. I looked in the pr0 file and didn’t see it mapped there.
It shows you are using shift POV HAT 3 for VAC ARM but I see it nowhere. The reason I am asking is because I want to add that to my X52 profile.
I’m beginning to wonder if my profile editor is not reading the X52 pro profile correctly because I have an X52 and you have the POV HAT 3 mapped to ctrl num -.
-
Scuby, I have a question about how you bound the VAC ARM to the POV hat 3 on the throttle. All I can see is that you added SimDoNothing -1 0 0X4A 2 0 1 0 “3RD: DWVAC Arm Voice Activation” which is ctrl num -. What I don’t understand is how you bound the POV hat 3 to ctrl num -. I looked in the pr0 file and didn’t see it mapped there.
It shows you are using shift POV HAT 3 for VAC ARM but I see it nowhere. The reason I am asking is because I want to add that to my X52 profile.
I’m beginning to wonder if my profile editor is not reading the X52 pro profile correctly because I have an X52 and you have the POV HAT 3 mapped to ctrl num -.
Hi Viking,
Sorry for my late reply, extremely busy in RL.
Regarding VAC, indeed I use the key combination “CTRL NUM -” for VAC ARM.
Regarding the BMS keyfile, where it says: "SimDoNothing -1 0 0X4A 2 0 1 0 “3RD: DWVAC Arm Voice Activation” and “CTRL NUM -” … this just for show! I did that, so that myself and others can see not to use that key combination in BMS.
Regarding the X52 Profile, the throttle POV should forward the “CTRL NUM -” key combination. Did you try to use the load button after opening the x52 profile? Sometimes it needs to be pressed before trying the HOTAS buttons…
Let me know!
Cheers,
Scub -
OK. Thanks. The problem I am having now is that when I map a button to VAC through the profile editor it over rides the dx callback, including the shifted dx callback. Am I doing something wrong or does mapping something with the profile editor block the shifted dx callback no matter what?
Thanks for the response.
-
Well, with my limited knowledge, I think that when you map a key to a x52 button in Saitek Profile Software, then the result will always be that key press instead of DX output.
DX in itself does not support shifting, our smart BMS coders have added this feature to BMS keyfile. Im sure you are using that. But it takes recognition of two DX buttons to work…now when the Saitek Software has mapped a key to one x52 button, and overrides it, BMS can never recognize one as DX and consequently both for shift DX.
Or I am indeed wrong about DX and it can be done but the above sounds kinda logical.
My profile is fully key based to not have this problem with 3rd party software like VAC, amongst other advantages.
-
That makes sense. What is done with DX “shifting” is that you put in the config file the value you want the shift button to add to the original button value. For instance, we use 256. So when we press button 5 it does that callback. When we press the shift button then button 5 it does the callback for button 261, and so on. So each hotas has like 32 DX buttons or something like that and then ?32? more are made available by adding 256 to each button when the pinky shift is pressed. The sim thinks we are pressing different buttons because the DX number is changed by 256 when we press the pinky shift, giving us twice the callbacks. The profile editor changes modes giving you many more buttons.