X52 in FC2 DRIVING ME NUTS!!!!

[jwputnam]

I have been working all day at setting up my Saitek X-52 in Flaming Cliffs 2 (updated).

 

I cannot get it to work. I have tried everything. I have tried an SST profile as well as "programming" the game inside.

 

Example: I attempt to set the "fire" button to change the color of the hud. I know that the command is "RCntrl + H", but when I load the game, the "fire" button seems not to recognize the modifier and simply gives me auto pilot altitude hold.

 

I have read the GUI manual and it looks like I may need to designate a "switch" versus a "modifier", but I am LOST!!!!!

 

I know that I am missing something that must be pretty simple, but after about eight hours of this....IT IS KILLING ME!

 

Can anybody explain what is happening to me? I NEVER had any trouble programming my X-52 in LOMAC.

 

Thanks!

[Kaiza]

Have you tried clearing all keybinds in the game and then using just your SST programming software exclusively?

[nomdeplume]

What version of the profile editor are you using? Older versions don't understand the difference between Left Ctrl and Right Ctrl, and so profiles won't work properly with games which care about the distinction. I'm using 6.6.6.9 and it works fine.

 

It may also be worth clearing the default joystick button bindings from the controls list for the plane you're setting up, just in case of a conflict. I don't think the game ever sees the joystick button presses if you have them mapped to something else with SST but it never hurts.

 

Also be aware that every plane has different controls and must be configured separately within FC2. This isn't such a problem if you're using SST as most of the keypresses are similar, but it has caused quite a few people some confusion.

[jwputnam]

I am using 6.6.6.9 as well and I have reloaded it as well as the 6.2.2.0 drivers several times now.

 

I prefer using SST as I like it a lot. I have cleared the X52 "category" inside the game, but I leave the keyboard commands (obviously) so that I can use the keyboard.

 

I complete my profile and load it. When I start the game, once again I press on the "fire" button in mode 1 (navigation...for me) and I get altitude hold ("h" versus "Rcntrl h")...and my flaps toggle instead on just go down because the modifier is not recognized it seems. This is true of ALL those commands that need a modifier.

 

I have reloaded the game and update twice now with no success. I run the game in "administrator", but I did not install it as "administrator". I am going to try that, but I don't expect much success.

 

I would suspect a software glitch in FC 2, but no one else seems to be reporting this problem.

 

Incidentally, I am running Windows 7, 64 bit on an AMD Dual Core with 4 gigs of ram.

 

Almost forgot....I note that I can get the "fire button" to work (changing the HUD color) IF I manually press the Rcntrl key on the keyboard, so it really makes me think that the problem is in the SST program not sending the instructions completely, but when I check the instruction using the test profile, it shows it as "HControlKey" (with blue repeaters after the H and ControlKey).

Edited June 27, 2010 by jwputnam
addendum

[EtherealN]

I would suspect a software glitch in FC 2, but no one else seems to be reporting this problem.

 

Personally, I would suspect a "software glitch" in the profiler and driver for the stick. Saitek drivers are just amazingly shoddy and prone to explosive behaviour. (I can cause BSOD's through naming commands certain ways in my profiler, for example - sets the MFD driver on fire. :P )

 

Do you have the magic mouse and magic keyboard drivers properly loaded? DxDiag would be nice.

[jwputnam]

The mouse and keyboard drivers are showing as working properly and drivers are 6.6.6.9.

 

I looked at DXDIAG and noticed that I have DX 11 loaded and the game requires DX 9, but I wouldn't think that to be a problem.

[EtherealN]

Dx11 and Dx9 co-exist.

 

I'd still like a DxDiag though, since it makes it a lot easier to look up hardware and drivers without waiting between each question. ;)

[mig29movt]

I used the SST software in a serious way (not just experimenting) for the 1st time today because I wasn't able to use the Ingame Settings in FC2...

 

I don't know if it helps but I learned this today:

 

You have to press exactly the same buttons in the same order in your profiler as you would do it on the keyboard.

In my case: Eject (Ctr[lleft] + E, 3 times) on the Button "POV Hat 2: UP"

 

In the empty cell I entered the following to get it working: CTRL and then E, releasing E and then releasing CTRL.

 

It looked like before inside the preview cell but this time it was also doing what I intended :glare:

 

I really hope it helps to you because I can understand how it is to mess around a full day just to assign the buttons in the F-15C :cry:

[jwputnam]

The log is too big to post here at 40,000 characters.

 

How about this:

 

 

-------------------

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: Saitek Magic Hotkey Device

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x06A3, 0x5081

FF Driver: n/a

Device Name: Microsoft Wireless Optical Desktop® 2.10

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x045E, 0x009D

FF Driver: n/a

Device Name: Microsoft Wireless Optical Desktop® 2.10

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x045E, 0x009D

FF Driver: n/a

Device Name: Microsoft Wireless Optical Desktop® 2.10

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x045E, 0x009D

FF Driver: n/a

Device Name: USB Receiver

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x046D, 0xC518

FF Driver: n/a

Device Name: USB Receiver

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x046D, 0xC518

FF Driver: n/a

Device Name: USB Receiver

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x046D, 0xC518

FF Driver: n/a

Device Name: Saitek X52 Flight Controller

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x06A3, 0x0255

FF Driver: n/a

Poll w/ Interrupt: No

-----------

USB Devices

-----------

+ USB Root Hub

| Vendor/Product ID: 0x10DE, 0x026D

| Matching Device ID: usb\root_hub

| Service: usbhub

| Driver: usbhub.sys, 10/23/2009 23:28:24, 343040 bytes

| Driver: usbd.sys, 7/13/2009 19:06:23, 7936 bytes

|

+-+ Saitek X52 Flight Controller (USB)

| | Vendor/Product ID: 0x06A3, 0x0255

| | Location: Port_#0006.Hub_#0001

| | Matching Device ID: usb\vid_06a3&pid_0255

| | Service: HidUsb

| | OEMData: 03 00 88 11 22 00 00 00

| | Driver: hidusb.sys, 7/13/2009 19:06:22, 30208 bytes

| | Driver: hidclass.sys, 7/13/2009 19:06:21, 76288 bytes

| | Driver: hidparse.sys, 7/13/2009 19:06:17, 32896 bytes

| |

| +-+ Saitek X52 Flight Controller (HID)

| | | Vendor/Product ID: 0x06A3, 0x0255

| | | Matching Device ID: hid\vid_06a3&pid_0255

| | | Service: SaiH0255

| | | OEMData: 03 00 88 11 22 00 00 00

| | | Driver: SaiH0255.sys, 2/15/2008 18:24:18, 178304 bytes

| | | Driver: SaiD0255.pr0, 2/15/2008 18:24:18, 8252 bytes

| | | Driver: SaiC0255.Dll, 2/15/2008 18:24:18, 1052160 bytes

| | | Driver: SaiC0255_07.dll, 2/15/2008 18:24:18, 8192 bytes

| | | Driver: SaiC0255_09.dll, 2/15/2008 18:24:18, 7680 bytes

| | | Driver: SaiC0255_0A.dll, 2/15/2008 18:24:18, 8192 bytes

| | | Driver: SaiC0255_0C.dll, 2/15/2008 18:24:18, 8704 bytes

| | | Driver: SaiC0255_10.dll, 2/15/2008 18:24:18, 8192 bytes

| | | Driver: SaiC0255_11.dll, 2/15/2008 18:24:18, 5632 bytes

| | | Driver: SaiC0255_0402.dll, 2/15/2008 18:24:18, 7168 bytes

----------------

Gameport Devices

----------------

------------

PS/2 Devices

------------

+ HID Keyboard Device

| Matching Device ID: hid_device_system_keyboard

| Service: kbdhid

| Driver: kbdhid.sys, 7/13/2009 19:00:20, 33280 bytes

| Driver: kbdclass.sys, 7/13/2009 20:48:04, 50768 bytes

|

+ Microsoft USB Dual Receiver Wireless Keyboard (IntelliType Pro)

| Vendor/Product ID: 0x045E, 0x009D

| Matching Device ID: hid\vid_045e&pid_009d&mi_00

| Service: kbdhid

| Driver: kbdhid.sys, 7/13/2009 19:00:20, 33280 bytes

| Driver: kbdclass.sys, 7/13/2009 20:48:04, 50768 bytes

|

+ Terminal Server Keyboard Driver

| Matching Device ID: root\rdp_kbd

| Upper Filters: kbdclass

| Service: TermDD

| Driver: i8042prt.sys, 7/13/2009 18:19:57, 105472 bytes

| Driver: kbdclass.sys, 7/13/2009 20:48:04, 50768 bytes

|

+ HID-compliant mouse

| Matching Device ID: hid_device_system_mouse

| Service: mouhid

| Driver: mouhid.sys, 7/13/2009 19:00:20, 31232 bytes

| Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes

|

+ HID-compliant mouse

| Vendor/Product ID: 0x045E, 0x009D

| Matching Device ID: hid_device_system_mouse

| Service: mouhid

| Driver: mouhid.sys, 7/13/2009 19:00:20, 31232 bytes

| Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes

|

+ Logitech HID-compliant Cordless Mouse

| Vendor/Product ID: 0x046D, 0xC518

| Matching Device ID: hid\vid_046d&pid_c518&mi_00

| Upper Filters: LMouFilt

| Lower Filters: LHidFilt

| Service: mouhid

| Driver: LHidFilt.Sys, 6/17/2009 11:54:22, 55312 bytes

| Driver: LMouFilt.Sys, 6/17/2009 11:54:30, 57872 bytes

| Driver: KHALMNPR.Exe, 6/17/2009 11:53:26, 130576 bytes

| Driver: mouhid.sys, 7/13/2009 19:00:20, 31232 bytes

| Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes

| Driver: WdfCoInstaller01005.dll, 6/1/2009 13:49:56, 1918856 bytes

|

+ Terminal Server Mouse Driver

| Matching Device ID: root\rdp_mou

| Upper Filters: mouclass

| Service: TermDD

| Driver: termdd.sys, 7/13/2009 20:45:55, 62544 bytes

| Driver: sermouse.sys, 7/13/2009 19:00:20, 26624 bytes

| Driver: mouclass.sys, 7/13/2009 20:48:27, 49216 bytes

Edited June 27, 2010 by jwputnam

[jwputnam]

I'll give this a try and let you know in an hour or so.

 

 

OH MY GOD!!!! OH MY GOD!!!! You are a f^%*&g GENIUS!!!!!!!

 

It works! It works!!!!!!

 

THANK YOU THANK YOU THANK YOU

Edited June 27, 2010 by jwputnam

[EtherealN]

How do I send you the DxDiag file? Screen shot? Is there a log that I can print out?

 

Yes. See screenshot.

 

Then reply using the "Go Advanced" button, then press the paperclip icon in the toolbar above the text field (but below the "title" field). Select and upload the DxDiag.txt using that.

Edited June 27, 2010 by EtherealN

[jwputnam]

Log is attached

 

Very kind of you to offer so much help!

DxDiag.txt

[jwputnam]

Problem is resolved.

 

How do we let others know?

[EtherealN]

People with similar problems can use the search function on the forum, or hopefully, I'll remember the thread and look it up for them. :)

[jwputnam]

Thank you so very much! Finally, I can play the damn game after two days of frustration!

[TWL]

same problem

 

So what fixed the problem? The DX stuff or the suggestion by mig29movt?

 

Thank You;

[jwputnam]

mig29movt

 

I have also spent a few hours developing a very logical (in my opinion) profile for the A-10. It is WAY best to make your own so that you understand WHY it works, but if you want it, I can post it.

Edited June 29, 2010 by jwputnam

[VRCRaptor]

mig29movt

 

I have also spent a few hours developing a very logical (in my opinion) profile for the A-10. It is WAY best to make your own so that you understand WHY it works, but if you want it, I can post it.

 

I would be interested in the X52 config you have...