X52 PRO Profile by 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.
-
Exactly. Viking did you find a solution to combine the key with your DX setup? Perhaps you can setup the entire POV en shift POV in Saitek to solve it.
-
I just mapped the mouse button on the throttle to VAC and lost the DX callbacks for that button. The way my HOTAS is set up is that the mode switching knob activates the callback for DF/MRM and so on, so unfortunately I cannot map to any other modes in the profile editor and use them with a pinky shift, which is what I think your profile does. I am happy with the setup but I just thought it would be great to be able to have the comms Hat POV work just like they are supposed to then just press the pinky shift and comms Hat when I used VAC. At this moment I don’t see being able to do that unless I am missing something. I would have to rewrite the entire key file and program a new profile which is too much work at the moment just for that tiny issue. Too bad I can’t use your profile because I have the X52 and not the pro. Thanks for getting back to me and helping me understand how you got it done in your setup. I have a pretty good idea how DX stuff works but I am still figuring out how it all fits together with the profile editor.
-
I hope you succeed. Just to be clear, my profile does not use DX at all. Everything is by keys, and only 1 mode. Maybe copy the same idea to your regular x52? If VAC on shift POV is your primary requirement.
-
Thanks. I need to learn more about the profile editor. I couldn’t view your profile because it doesn’t show up with an X52. So all of your shifted keys are programed into a shifted state within the profile editor? If VAC worked with DX then I could do it in the key file, but it looks like if I want it to work without overriding the shifted state I have to use the profiler software.
-
First off i want to Thank you for this great profile. Huge help in getting back into Falcon after 10 years.
Only problem i am having is the (D) button on the throttle doesn’t toggle air brakes. when testing in Profiler the Shift function (Deploy chute) functions but the non shift doesnt do anything even though i have confirmed it is assigned to press B key. Also confirmed BMS is still set to use B key to toggle airbrakes in .key.
Using Win10 Saitek drivers btw , in case that matters.Any help would be greatly appreciated , Thanks again Scuby
-
Maxavius,
Could you open Notepad or Word, and confirm you can type the “B” key when you press the throttle button? If yes, then I would take another look to the keyfile. If no, then I would take another look to the Saitek profile, or, maybe another 3rd party software is absorbing/conflicting the “B” key…
Good luck!
-
I downloaded your profile and playing around with it. I’m not new to BMS, but I just got my x52 pro. I’m not use to programming and DX is WAY new to me and I’m still learning the SST profiler. But I wanted to change a few things on your profile. Can I just use the SST profile and how does DX come into play? Where do I find it? Thanks for any info.
-
I downloaded your profile and playing around with it. I’m not new to BMS, but I just got my x52 pro. I’m not use to programming and DX is WAY new to me and I’m still learning the SST profiler. But I wanted to change a few things on your profile. Can I just use the SST profile and how does DX come into play? Where do I find it? Thanks for any info.
Hello redshirt78,
This x52 profile is based solely on key emulation, i.e. pressing a button results in pressing a keyboard key. Non of the x52 buttons are assigned as a DX callback.
Now, if a user wants to make changes to the x52 profile, this can be done with STT profiler by using new keyboard keys.
However, if a user wants to assign a DX callback to one of the x52 buttons, then the user must first go in the STT profiler and delete that key. Now the BMS keyfile will recognize a button press as a DX press (instead of recognizing a key).
For what it is worth, I wouldn’t recommend mixing key emulation with DX assignment. Rather choose - based on your preference - either a key based or DX based profile on this forum. Both have pro’s and con’s.
Have fun!
Scub -
Hello redshirt78,
This x52 profile is based solely on key emulation, i.e. pressing a button results in pressing a keyboard key. Non of the x52 buttons are assigned as a DX callback.
Now, if a user wants to make changes to the x52 profile, this can be done with STT profiler by using new keyboard keys.
However, if a user wants to assign a DX callback to one of the x52 buttons, then the user must first go in the STT profiler and delete that key. Now the BMS keyfile will recognize a button press as a DX press (instead of recognizing a key).
For what it is worth, I wouldn’t recommend mixing key emulation with DX assignment. Rather choose - based on your preference - either a key based or DX based profile on this forum. Both have pro’s and con’s.
Have fun!
ScubSince your profile isn’t DX, having the Mode switch do different things is not possible? I’m assuming that’s a DX thing. Plus, if I change a command, does BMS automatically recognize the change? Or do I need to do some file swapping that’s best left for professionals (people who know what they are doing). Thanks in advance.
EDIT: to clarify, I don’t want to mix DX stuff into your profile since yours is not DX.
-
Since your profile isn’t DX, having the Mode switch do different things is not possible? I’m assuming that’s a DX thing.
With STT, you can setup the mode switch as mode selector or 3way switch. In this profile it is a mode selector. To have it work as switch, you enter keys in the top row in STT.
Plus, if I change a command, does BMS automatically recognize the change? Or do I need to do some file swapping that’s best left for professionals (people who know what they are doing). Thanks in advance.
EDIT: to clarify, I don’t want to mix DX stuff into your profile since yours is not DX.
The keys you use in STT need to exist in the BMS keyfile. So have a look at the BMS keyfile and find the functions you wish to operate. Also research which keys or combos are free for use. Enter free keys for those functions in the BMS keyfile, enter the same keys in STT profile.