Settings/Questions for Saitek X52 Pro

[Ratneck]

I've got my X52 Pro mostly working with the flight in game, and it definitely makes the game more fun for me. I've run into a couple of issues and I was wondering if anyone else had found these and found a solution.

1) When I use the main hat for "ascend" and "Descend", it assigns buttons 128 and 130. These only rarely seem to work in game. When I load the profiler and break the hat into key presses and assign the "space" and "Left Control" to the up and down function on the hat, it works fine. Does anyone know why this is occurring, or has anyone else had a similar issue?

2) When I pull my throttle all the way back, after slowing down, I don't get a zero speed. I have the throttle set to Analog Throttle. It seems like I actually hit my lowest throttle point before the lower detent. I'm going to split that out into a key press (for brakes, if available), along with the upper detent (for afterburner). Either way, the ship always seems to be around 1 - 3 kph. The only way to get it to fully stop is to get out, and back in. I've checked my throttle in the saitek utility and it is giving a clean full on to full off. Has anyone else experienced this throttle "slop" at the bottom of the range?

3) The dual stage trigger. Does anyone have a sure fire way to assign the "second" stage of the trigger? I've found it detects the first stage and assumes that's what I want to program. I finally got it to work by assigning the first stage to what I want the trigger to hit, and then quickly doing it again and grabbing the trigger to make it sense the second stage, then I have to assign the first stage to another function and clear it. Is there a better way to do this?

4) Finally, does anyone have a set-up or profile for their stick they'd like to share? I'm still working on mine, and I'm new to the game so mine is still very much a work in progress....only two keys in the profile the rest is in the game....but I'll be changing that soon.

For now, I have the hat on the throttle set to my chat channels, I'm assuming they'll get the VoIP working better. The upper left stick hat I have for views, the lower hat only ascend and descend so far. And my buttons are randomly placed.

5) speaking of buttons, I have a button set to pull up the map, but is it possible to set a key to center on myself (is there a hotkey that doesn't involve clicking the little "man" in the center of the map panning tool?)?

[MalakithSkadi]

I would be very interested to hear how you are managing to bind the Joystick and Rudder Axis, the only way I can currently get it to detect anything ingame is to use Key binds in the profiler which are obviously horrible digital inputs (all or nothing).

I can get it to detect XBox controller sticks fine, but then can't work out how to have the X52 emulate them but if I just try with the default Stick axis it refuses to bind anything in game.

[Ratneck]

The best I can tell you is that it works fine for me. I go into settings, -> Keybinding -> (Select Tab). Then I click on the space on the grid that corresponds with "Joystick" and the Function I want. When the box pops up to program the key, I do the action on the joystick I want to assign.

I attached screen shots so you can see how it shows up. Based on the fact that the game considers the X52 Pro to be a Gamepad, it must be getting this information from windows. If you look at the screenshot of my "Devices", you'll see that the X52 Pro is categorized as a gamepad by Windows 7.

This makes me think it's using DirectX input for the joystick, so I've cut the relevant section of my DXdiag file for you:

-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Programmable Hotkeys
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x5081
        FF Driver: n/a

      Device Name: Saitek X52 Pro Flight Controller
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x0762
        FF Driver: n/a

      Device Name: Asus Wireless Audio Device
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x170D, 0x0001
        FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x1E26
| Matching Device ID: usb\root_hub20
| Service: usbhub
| Driver: usbhub.sys, 3/24/2011 22:29:26, 343040 bytes
| Driver: usbd.sys, 3/24/2011 22:28:59, 7936 bytes
| 
+-+ Generic USB Hub
| | Vendor/Product ID: 0x8087, 0x0024
| | Location: Port_#0001.Hub_#0002
| | Matching Device ID: usb\class_09
| | Service: usbhub
| | Driver: usbhub.sys, 3/24/2011 22:29:26, 343040 bytes
| | 
| +-+ Saitek X52 Pro Flight Controller (USB)
| | | Vendor/Product ID: 0x06A3, 0x0762
| | | Location: Port_#0005.Hub_#0004
| | | Matching Device ID: usb\vid_06a3&pid_0762
| | | Service: HidUsb
| | | OEMData: 03 00 88 11 27 00 00 00
| | | Driver: hidusb.sys, 11/20/2010 05:43:49, 30208 bytes
| | | Driver: hidclass.sys, 11/20/2010 05:43:49, 76800 bytes
| | | Driver: hidparse.sys, 7/13/2009 19:06:17, 32896 bytes
| | | 
| | +-+ Saitek X52 Pro Flight Controller (HID)
| | | | Vendor/Product ID: 0x06A3, 0x0762
| | | | Matching Device ID: hid\vid_06a3&pid_0762
| | | | Service: SaiH0762
| | | | OEMData: 03 00 88 11 27 00 00 00
| | | | Driver: SaiH0762.sys, 4/4/2008 17:10:34, 178560 bytes
| | | | Driver: SaiD0762.pr0, 2/15/2008 18:27:30, 8438 bytes
| | | | Driver: SaiC0762.Dll, 4/4/2008 17:10:34, 1060352 bytes
| | | | Driver: SaiC0762_07.dll, 4/4/2008 17:10:34, 8192 bytes
| | | | Driver: SaiC0762_09.dll, 4/4/2008 17:10:34, 7680 bytes
| | | | Driver: SaiC0762_0A.dll, 4/4/2008 17:10:34, 8192 bytes
| | | | Driver: SaiC0762_0C.dll, 4/4/2008 17:10:34, 8704 bytes
| | | | Driver: SaiC0762_10.dll, 4/4/2008 17:10:34, 8192 bytes
| | | | Driver: SaiC0762_11.dll, 4/4/2008 17:10:34, 5632 bytes
| | | | Driver: SaiC0762_0402.dll, 4/4/2008 17:10:34, 7168 bytes

When I go into Device Manager, I find the X52 listed under "Human Interface Devices":
Human Interface Devices
Saitek X52 Pro Flight Controller (HID) 6.2.2.4 (4/4/2008)
Saitek X52 Pro Flight Controller (USB) 6.2.2.4 (4/4/2008)

My programming/config software is Software version 7.0.2.7

Have you tried shutting off your profile in the programming software? Right clicking on the icon in the task bar and going to "Clear"? This way the stick is sending it's commands and not keyboard commands, as I'd guess a keyboard command can't go under the "Joystick" column....that I don't know for sure.

I downloaded the drivers/software directly from Saitek, I didn't let windows use anything built in for it. Have you tried uninstalling the two entries for the Joystick, restarting the machine, and re installing the driver?

Finally, since the stick appears to be a hand-off from windows, you have to have it plugged in and fully recognized before you start the software. If you plug it in afterwards, it will work with keypresses through the profiling software, since that emulates a keyboard....but the game doesn't see it as a device.

Hope that was helpful....Work calls, I'll take a look later.
Will

[MalakithSkadi]

Yep had to update the drivers mine were a few months older.

Still not really happy with their implementation though, problems I am encountering are:

1. Even with the Deadzone slider as low as possible there is a noticeable deadzone (not the X52s settings, checked those).

2. It seems to "accelerate" part way through the axis, once you go past about half way the movement gained is significantly higher for the input given.

3. Rudder axis never achieves "maximum speed", I had to set them up as a Band axis then bind in A and D to get anything like decent speed out of the rudder.

4. Throttle, similar problem to you. Its temperamental as to whether it decides Full back is hover or not. I found pushing it forward and then back again usually kicks it in but its not ideal.



It is number 2 that is really the deal breaker in dogfights though, you move that fraction that should make you pull only slightly further back, it kicks into its "acceleration zone" and wham massive overshoot on the target.


Thanks for the help in getting me this far though, at least I can justify jumping in the Fighter now instead of just sticking to Galaxy and Liberators.



On the note of some of your issues. I bound the Hat on the Throttle Up and Down to be Ascend and Descend directly in game (no programmer settings), it seems to respond fine every time so can't help there.

With regard to Binding the 2 stage trigger. Hold the trigger at Stage 1, click the thing in the menu you want to bind. It wont detect you holding an existing button, then click it into Stage 2. It should pick up the transition and bind it. I just set both of mine to Primary Fire.