X-52 Profile
-
Hello guys, I post my profile.
Rename the .doc files and remove the doc extension. Rename AAA.pro.doc to AAA.pro, and the AAA.key.doc to AAA.key in order to work.
I had to do that otherwise I couldn’t upload, the system only allows certain type of files.
I have modified the original and you will find the Saitek profile, the BMS profile and the photos with the assigned buttons.
I hope you like it.
The slider I use it for field of view, like zoom in/out and the wheel for increase/decrease range. -
I modified the profile and now is more combat efficient. Have a look and use if you like. The instructions are the same with me previous post.
I make those updates for people who dont want to bother making a profile. I want to help others.
Enjoy
-
Hi! Are you using pinky as a shift function?
And if so, how did you do it? Cuz I’m lost -
Hi! Are you using pinky as a shift function?
And if so, how did you do it? Cuz I’m lostFirst, you pick a button that the shift is going to be on.
Then, in your key file, you assign this command to that button SimHOTASPinkyShift.
You need to know what DX Button number that button is. Let’s say it’s DX button #5. Your keyfile command will look like this: SimHotasPinkyShift 5 -1 -2 0 0x0 -1
You then need to assign the same command with the shift offset (usually 256) …. in other words, you’re going to make button #5 ACT like a second button and it will be assigned a DX number of 5 + 256 --> it will be DX Button #261. You need the same command as before, but on button #261, SimHotasPinkyShift 261 -1 -2 0 0x0 -1.
Those are your shift commands. The numbering (shifted or unshifted) works like so (typically, there can be customized exceptions if I understand correctly):
Now, for each button/switch on your HOTAS PLUS your POV hat, you can assign one command on the unshifted layer and another command on the shifted layer. Each button will ‘pretend’ to be two buttons …. on shifted and one unshifted … and those two ‘pretend’ buttons will be 256 DX numbers apart. So button 0 ACTS like button 0 & button 256, button 1 acts like button 1 & button 257 … 2 & 258 … 3 & 259 … 4 & 260 … etc.
-
yes I did.I used the Excell in the folder doc. and the explanation is above.
-
Hi mlazos,
i tried you profile a bit Yesterday, but i noticed that moving that little stick on the throttle (near cursor button) makes radar cursor move in wrong way and/or stops.
Moreover, pinky + hat 3 up and down does nothing (no waypoint prev/next)I just loaded your .pr0 into saitek and .key into bms….what am I missing?
Thanks in advance!I modified the profile and now is more combat efficient. Have a look and use if you like. The instructions are the same with me previous post.
I make those updates for people who dont want to bother making a profile. I want to help others.
Enjoy
-
I downloaded both files, I run them and works for me. First change the extension. Remove the doc. Then load the file in the profile from falcon. you go to controllers and you load the AAA.key
You do the same for the X52 and make sure there is no previous profile, run the profiler in order to clear any previous profile.I tried all buttons, the previous and next waypoint buttons work as expected and the stick controls the radar cursor. Maybe you need to get used, Im not sure what you mean by wrong way.
It should work normally, they work for me. I dont see any reason not to work for you. It is the normal X52, not the pro. Can you try one more time please?You should also activate the command Enable clutch button from the controller settings. you can do that in the game controller properties.
In the profile for the X52, you can actually easily modify the mouse stick on the controller. It is not from the falcon key so you can adjust it the way you want it easily.
-
Thank you for your answer. I have the normal X52, not the pro version.
I’ll try tonight for sure. Actually I didn’t clear previous saitek profile, i only put the pr0 file in the saitek directory and chosen from the icon tray saitek icon…
About the mini stick, it happens that it works only in 2 directions. The other 2 directions does nothing or recenter my trackir.
I’ll let you know after my test tonight.I downloaded both files, I run them and works for me. First change the extension. Remove the doc. Then load the file in the profile from falcon. you go to controllers and you load the AAA.key
You do the same for the X52 and make sure there is no previous profile, run the profiler in order to clear any previous profile.I tried all buttons, the previous and next waypoint buttons work as expected and the stick controls the radar cursor. Maybe you need to get used, Im not sure what you mean by wrong way.
It should work normally, they work for me. I dont see any reason not to work for you. It is the normal X52, not the pro. Can you try one more time please?You should also activate the command Enable clutch button from the controller settings. you can do that in the game controller properties.
In the profile for the X52, you can actually easily modify the mouse stick on the controller. It is not from the falcon key so you can adjust it the way you want it easily.
-
Ok, i made some tests and clearing previous saitek Profiles solved many issues.
Now, the only thing that doesnt work as it should is the radar cursor slew. At first ,moving the mouse stick up caused trackir recenter, and i think i resolved changing in trackir software the shortcut for center (it was F12). Moving it down, radar cursor slews down, but never stops! I found no solution for this issue indeed
I have been trying with and without the enable clutch option but the result is the same.
Do you have any advise? -
just a general quick question about using an x-52 with this sim, is there a way to get a unassagned (joystick binds) keyfile so that NO buttons are mapped within BMS for my x-52 so that i can make my own profile with entirley my own bindings in the x-52s profile software thus avoiding conflicts? Would be very appreciative of any help you could give here. Best Regards
-
just a general quick question about using an x-52 with this sim, is there a way to get a unassagned (joystick binds) keyfile so that NO buttons are mapped within BMS for my x-52 so that i can make my own profile with entirley my own bindings in the x-52s profile software thus avoiding conflicts? Would be very appreciative of any help you could give here. Best Regards
I’m in the process of configuring the controls and have this same question… is anybody able to assist? I 'm having a difficult time in assigning the controls to my hotas
-
This post is deleted! -
I’m in the process of configuring the controls and have this same question… is anybody able to assist? I 'm having a difficult time in assigning the controls to my hotas
I wonder why you guys want to make a profile in the *&!#^%$ SST software and skip the ease and comfort of DirectX. All you have to do is put a DX number after the function call instead of extracting the key value from a function and emulate that with SST, which is known not to be God’s greatest gift to this Earth you now!
Ok…assuming you want it do it your own way then look at BMS Basic.key, open it, delete everything from ### DX button mapping and beyond.
Load this keyfile in BMS /controller UI.
Now you do not have DX assigments crossing your line of fire with SST anymore.Good luck.
btw … I would not try to invent the wheel myself but rather look for a descent X-52 keyfile on this forum and go from there.
-
-
I am using your profile but I can not get the mini stick to slew the radar cursor. It starts out centered in the radar screen but as soon as I attempt to slew it, it begins to move left and down without stopping. What could I be doing wrong? Perhaps the advanced avionics settings? Should Cursor X and Y be set to keyboard or mini stick X and Y? No matter what I do I can’t get control of the radar cursor for some reason. Also had to change the SST profile for the Cursor right to shift right arrow from F12. Was it supposed to be that way?
-
I modified the profile and now is more combat efficient. Have a look and use if you like. The instructions are the same with me previous post.
I make those updates for people who dont want to bother making a profile. I want to help others.
And I appreciated this a lot, mlazos.
Thanks for sharing and best regards,
-
This post is deleted! -
I wonder why you guys want to make a profile in the *&!#^%$ SST software and skip the ease and comfort of DirectX. All you have to do is put a DX number after the function call instead of extracting the key value from a function and emulate that with SST, which is known not to be God’s greatest gift to this Earth you now!
Ok…assuming you want it do it your own way then look at BMS Basic.key, open it, delete everything from ### DX button mapping and beyond.
Load this keyfile in BMS /controller UI.
Now you do not have DX assigments crossing your line of fire with SST anymore.Good luck.
btw … I would not try to invent the wheel myself but rather look for a descent X-52 keyfile on this forum and go from there.
Hi Snelle! The directX approach sounds interesting. Could you point me to a more complete discussion of how to do it?
Thanks! -
maybe you have other software binding the keys? it happened to me once when i was trying to run a program to record the screen.
Check what other software you run and what keys are binding. -
@16th:
I am using your profile but I can not get the mini stick to slew the radar cursor. It starts out centered in the radar screen but as soon as I attempt to slew it, it begins to move left and down without stopping. What could I be doing wrong? Perhaps the advanced avionics settings? Should Cursor X and Y be set to keyboard or mini stick X and Y? No matter what I do I can’t get control of the radar cursor for some reason.
one of the earlier driver versions seems to have that problem. it was a pain in the ass. installed latest drivers, problem seems to be fixed.