Saitek X-52 Profile
-
Check your documents library (or whatever it is in Win10 - I use Win7).
Cheers!
-
look there:
C:\Users\Public\Documents\SmartTechnology ProfilesSebi
-
Hello, Viking, how you?
I’m experiencing an issue never had before: after having reinstalled your last updated profile on my Win 10 Pro system, the ‘Rotary 2’ command doesn’t work, so I can’t get any TGP zoom any longer.
Do you have any suggestions to fix that?
Thanks a lot in advance for your help, with best regards.
-
Kesmonkey,
I just wanted to thank you for an awesome profile for the x52. I have been using your profile for almost a year, and I love it. Thanks for all your hard work. While I hope to upgrade to a cougar with force sensing soon, I have had a great ride with the x52, and it will be great to always have as a backup. Its just a great hotas to introduce people into the hobby, and your profile really made it easy for me to learn the game.
-
Hi, Jackal. Good. How is it?
Have you made sure you assigned the rotary in the settings? If so check to see if you have these line in your key file:
SimRangeKnobUp -1 0 0x3E 4 0 0 1 “TQS: MAN RANGE Knob - Up”
SimRangeKnobDown -1 0 0x3D 4 0 0 1 “TQS: MAN RANGE Knob - Down”Let me know more about your problem if you can’t get it going.
-
Hi, Viking, it’s fine here and I hope it will keeping the same for you.
Thanks a lot for your help and suggestions, mate.
I’ll check that out right away, but from what I remember I haven’t those lines embedded in my key.
I’ll let you know further in any case, please count on my feedback.Update: no joy, nothing works as before. I noticed that in the SST no command has been assigned to that rotary. Would it mean something or not, to you?
Oh, please wait: and which kind of settings are you referring to, those in the .cfg file or in BMS - controllers - advanced submenu instead?Solved! What a moron I was, I didn’t set the rotary as the range knob device, and all is working out fine now.
Thanks a lot, Viking, and if I can dare a suggestion, what do you think to add this - if not already done, of course - in that .cfg file you made for the updated profile you’ve made?With best regards,
-
Only use these files and follow these directions only. I doing this does not work let me know.
Noob question: Is there a link to a keyboard layout that corresponds to this profile? Or perhaps I should ask if there was any reassignment in the keyfile relative to the default “full” version? Apologies if this is in the documentation somewhere - going nuts with all the reading.
thx, -Ron
-
Hey,
It should match well with the current keyboard layout. Let me know what buttons you are having problems with.
-
Could u build for 4.33 ?
-
Hey,
It should match well with the current keyboard layout. Let me know what buttons you are having problems with.
Thx Viking for responding. I’m just on ramp training TE #1, so no experience with wide range of commands. I do have the full keyboard layout printed out. I did think there was an issue with the wheel brakes (k key), but later discovered it was the known bug in the UI where going into the advanced controllers pane, then back, deactivates the keyboard. (Simple work around is to click on one of the other main setup windows, then go back to controllers.)
However, I do seem to have a problem on the X-52 with the pinky shifted trigger (first detent) not activating the wheel brakes. I’ve seen various mentions of issues relating to this, but haven’t pieced them altogether into a solution yet. Here are all lines in your key file that contain the string “wheelbrake” or “pinky”:
SimWheelBrakes -1 0 0X25 0 0 0 1 "CKPIT: Wheel Brakes - Hold" SimWheelBrakes 256 8 -2 0 0x0 0 SimHotasPinkyShift 5 8 -2 0 0x0 0 SimHotasPinkyShift 261 8 -2 0 0x0 0
And here are relevant(?) lines from my config file:
set g_nHotasPinkyShiftMagnitude 256 // following two lines added per Saitek X52 config instructions on BMS X52 forum.// set g_nHotasPinkyShiftMagnitude 256 set g_nHotasShiftQuickPressTimeLimit 500
I followed advice (yours I think) to add those last two lines. Does it matter that one of them is a redundancy?
Would appreciate any advice on resolving the X-52 problem.
WAIT. I just checked again on the runway start, and the pinky/trigger works! It brakes! I guess I didn’t notice it before because I was practicing ramp start, and the jet started rolling in idle after I removed the blocks and was going too fast by the time I noticed it. (I’m still learning Track IR also LOL.) That was when the k key wasn’t working, and I concluded that neither was the X52. Doh, what a mixup. I’ll post this anyway in case it helps someone else.
I want to thank you Vandal, and KesMonkey for these files. I’m still learning how callbacks and DX assignments work, but I can see it was a lot of work. What a fantastic example of cooperative development this whole project is!
-Ron
-
i need non-track-ir profile please
-
This post is deleted! -
I am having a problem. I have tried both Keys and Vikings profile and my radar cursor continues scrolls to the left. Does anybody know how to fix? Thanks
-
can we use for x-52 pro non trackir profile ? i sold my old saitek x-52 non pro and buy x-52 pro and i want to use this profile .
help me :?
-
can we use for x-52 pro non trackir profile ? i sold my old saitek x-52 non pro and buy x-52 pro and i want to use this profile .
help me :?
No. Buttons and button numbers are different between X-52 and X-52 Pro. You need a keyfile specific to whichever device you’re using.
I posted a non-Track version of mine (X-52 Pro) here:
-
No. Buttons and button numbers are different between X-52 and X-52 Pro. You need a keyfile specific to whichever device you’re using.
I posted a non-Track version of mine (X-52 Pro) here:
i downloaded it but only throttle and stick work …
no buttons works.
-
i downloaded it but only throttle and stick work …
no buttons works.
You have other devices? MFD’s, Rudders, ICP, etc.?
If so, adjust the file x:\Falcon BMS 4.33 U1\User\Config\DeviceSorting.txt so that the X-52 Pro is first and other devices are after. If your keyfile uses DX assignments for those ‘other’ devices, this may cause an issue …. those DX commands may no longer work.
-
rudder work but joystick mfd come blank …
-
rudder work but joystick mfd come blank …
It’s the device order that is causing a problem with that profile. 99% sure.
DX depends on a specific device order (which the user/creator accounts for). In this profile the X-52 Pro ‘owns’ DX buttons 1 - 32, so it must be the first device, or you have to renumber the commands to reflect where in the device order list the X-52 Pro is.
Can you post the content (copy/paste) of your x:\Falcon BMS 4.33 U1\User\Config\DeviceSorting.txt file?
-
{075C06A3-0000-0000-0000-504944564944} “Saitek X52 Flight Control System”
{00060079-0000-0000-0000-504944564944} "USB Joystick "
{00060079-0000-0000-0000-504944564944} “Usb Lan Zheng Electronics Vibration Joystick”
{076206A3-0000-0000-0000-504944564944} “X52 Professional H.O.T.A.S.”Like this