joystick not working in ah

[DarkHawk]

Had a system crash, did a complete install, plus all updates, in AH, unable
to setup the joystick, checking in windows each function works correctly, however in AH I get three setting on the x & y axis
either zero, 32xxx or 65xxx, no gradual change as it was before the system crash, down loaded a new copy of ah and installed.
dx to follow:
------------------
System Information
------------------
Time of this report: 8/14/2010, 14:57:07
       Machine name: YOUR-13E050B673
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100427-1636)
           Language: English (Regional Setting: English)
System Manufacturer: Sony Corporation
       System Model: VGC-RA825G(UC)
               BIOS: BIOS Date: 11/16/04 15:31:07 Ver: 08.00.10
          Processor: Intel(R) Pentium(R) 4 CPU 3.60GHz (2 CPUs)
             Memory: 2048MB RAM
          Page File: 828MB used, 3115MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.5512 32bit Unicode

------------
DxDiag Notes
------------
  DirectX Files Tab: No problems found.
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Music Tab: No problems found.
          Input Tab: No problems found.
        Network Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (n/a)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
        Card name: ATI Radeon HD 4550 
     Manufacturer: ATI Technologies Inc.
        Chip type: ATI Radeon Graphics Processor (0x9540)
         DAC type: Internal DAC(400MHz)
       Device Key: Enum\PCI\VEN_1002&DEV_9540&SUBSYS_22701545&REV_00
   Display Memory: 512.0 MB
     Current Mode: 1280 x 1024 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: ati2dvag.dll
   Driver Version: 6.14.0010.7101 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 7/6/2010 21:47:56, 299520 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: ati2mtag.sys
    Mini VDD Date: 7/6/2010 22:27:52, 5069312 bytes
Device Identifier: {D7B71EE2-D600-11CF-486D-7A02A1C2CB35}
        Vendor ID: 0x1002
        Device ID: 0x9540
        SubSys ID: 0x22701545
      Revision ID: 0x0000
      Revision ID: 0x0000
      Video Accel: ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
         Registry: OK
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled
DDraw Test Result: Not run
 D3D7 Test Result: Not run
 D3D8 Test Result: Not run
 D3D9 Test Result: Not run

-------------
Sound Devices
-------------
            Description: Logitech USB Headset
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: USB\Vid_046d&Pid_0a02&Rev_1013&MI_00
        Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
            Driver Name: usbaudio.sys
         Driver Version: 5.01.2600.5512 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 4/13/2008 14:45:12, 60032 bytes
            Other Files:
        Driver Provider: Microsoft
         HW Accel Level: Full
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run

            Description: Realtek HD Audio rear output
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0880&SUBSYS_08800000&REV_0905
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RtkHDAud.sys
         Driver Version: 5.10.0000.5028 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 7/29/2004 16:04:26, 2216128 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Full
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 100, 192000
Static/Strm HW Mix Bufs: 33, 32
 Static/Strm HW 3D Bufs: 33, 32
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: Yes, Yes
   I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run
      Device Name: Saitek X52 Flight Controller
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x0255
        FF Driver: n/a

      Device Name: Saitek Pro Flight Rudder Pedals
         Attached: 1
    Controller ID: 0x1
Vendor/Product ID: 0x06A3, 0x0763
        FF Driver: n/a

Poll w/ Interrupt: No
         Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x265B
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/13/2008 14:45:37, 59520 bytes
| Driver: usbd.sys, 8/10/2004 08:00:00, 4736 bytes
|
+-+ Saitek Pro Flight Rudder Pedals (USB)
| | Vendor/Product ID: 0x06A3, 0x0763
| | Location: Saitek Pro Flight Rudder Pedals
| | Matching Device ID: usb\vid_06a3&pid_0763
| | Service: HidUsb
| | OEMData: 00 00 00 00 00 00 00 00
| | Driver: hidusb.sys, 4/13/2008 14:45:28, 10368 bytes
| | Driver: hidclass.sys, 4/13/2008 14:45:26, 36864 bytes
| | Driver: hidparse.sys, 4/13/2008 14:45:22, 24960 bytes
| | Driver: hid.dll, 4/13/2008 20:11:54, 20992 bytes
| |
| +-+ Saitek Pro Flight Rudder Pedals (HID)
| | | Vendor/Product ID: 0x06A3, 0x0763
| | | Matching Device ID: hid\vid_06a3&pid_0763
| | | Service: SaiH0763
| | | OEMData: 00 00 00 00 00 00 00 00
| | | Driver: SaiH0763.sys, 2/15/2008 17:51:22, 136832 bytes
| | | Driver: SaiC0763.Dll, 2/15/2008 17:51:22, 831488 bytes
| | | Driver: SaiC0763_07.dll, 2/15/2008 17:51:22, 8192 bytes
| | | Driver: SaiC0763_09.dll, 2/15/2008 17:51:22, 7680 bytes
| | | Driver: SaiC0763_0A.dll, 2/15/2008 17:51:22, 8192 bytes
| | | Driver: SaiC0763_0C.dll, 2/15/2008 17:51:22, 8704 bytes
| | | Driver: SaiC0763_10.dll, 2/15/2008 17:51:22, 8192 bytes
| | | Driver: SaiC0763_11.dll, 2/15/2008 17:51:22, 5632 bytes
| | | Driver: SaiC0763_0402.dll, 2/15/2008 17:51:22, 7168 bytes

[The Fugitive]

hopefully you just trimmed the report a bit too soon, because under the USB heading it only shows the rudders....

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x265B
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/13/2008 14:45:37, 59520 bytes
| Driver: usbd.sys, 8/10/2004 08:00:00, 4736 bytes
|
+-+ Saitek Pro Flight Rudder Pedals (USB)
| | Vendor/Product ID: 0x06A3, 0x0763
| | Location: Saitek Pro Flight Rudder Pedals
| | Matching Device ID: usb\vid_06a3&pid_0763
| | Service: HidUsb
| | OEMData: 00 00 00 00 00 00 00 00
| | Driver: hidusb.sys, 4/13/2008 14:45:28, 10368 bytes
| | Driver: hidclass.sys, 4/13/2008 14:45:26, 36864 bytes
| | Driver: hidparse.sys, 4/13/2008 14:45:22, 24960 bytes
| | Driver: hid.dll, 4/13/2008 20:11:54, 20992 bytes
| |
| +-+ Saitek Pro Flight Rudder Pedals (HID)
| | | Vendor/Product ID: 0x06A3, 0x0763
| | | Matching Device ID: hid\vid_06a3&pid_0763
| | | Service: SaiH0763
| | | OEMData: 00 00 00 00 00 00 00 00
| | | Driver: SaiH0763.sys, 2/15/2008 17:51:22, 136832 bytes
| | | Driver: SaiC0763.Dll, 2/15/2008 17:51:22, 831488 bytes
| | | Driver: SaiC0763_07.dll, 2/15/2008 17:51:22, 8192 bytes
| | | Driver: SaiC0763_09.dll, 2/15/2008 17:51:22, 7680 bytes
| | | Driver: SaiC0763_0A.dll, 2/15/2008 17:51:22, 8192 bytes
| | | Driver: SaiC0763_0C.dll, 2/15/2008 17:51:22, 8704 bytes
| | | Driver: SaiC0763_10.dll, 2/15/2008 17:51:22, 8192 bytes
| | | Driver: SaiC0763_11.dll, 2/15/2008 17:51:22, 5632 bytes
| | | Driver: SaiC0763_0402.dll, 2/15/2008 17:51:22, 7168 bytes


Double check to make sure your seeing your stick in there. You should be seeing you said it works in windows. When in the game, go to Map Controllers. Use the dropdown box to find your stick and select it, then highlight each axis and point it toward the proper axis. Click the OK button to save. Then go back and calibrate each axis one at a time.

 Hope it works out for ya.

[Tigger29]

If you're trying a Saitek X52, make sure you turn the LED's all the way down in the control panel (or use a powered USB hub).  Also make sure the cord between the stick and the throttle is fully seated... it's very common for these to come slightly unplugged and cause issues.

And of course, make sure windows sees the stick just fine and that all functions work through the control panel.

If you don't use a Saitek X52, let us know what stick you are using..

[DarkHawk]

testing in the game port the stick works okay, all other function work, hat switches work, all buttons work on the x52, even the throttle work, only thing failing is the x and y axis. The x52 shows up in ah along with the
rudder pedals. 



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

      Device Name: Saitek Pro Flight Rudder Pedals
         Attached: 1
    Controller ID: 0x1
Vendor/Product ID: 0x06A3, 0x0763
        FF Driver: na. 

The stick did not show in the usb port, but it will test ok in windows, under the game port setting.

[Skuzzy]

Did you try using the "Calibrate Axis" button in the Options->Controls->Map Controllers panel to calibrate each individual axis you are having issues with.  Be sure to select the axis before hitting the button.

Did you happen to load the Saitek software?

[DarkHawk]

Download updated drivers from saitek, I have just completed a new install of all software, but did not update to the newest drivers only installed the ones on the install disk, I do not use the sst program at all, I still have a lot of updates of software to complete, may have a problem with a compatability issue, will not install the latest drivers from saitek. just ran some off line test and stick and rudder pedals are working correctly, will continue to test to see if any additional problems show up.
 on the dxdiag run if the joystick is plugged in after the rudder pedals you will see two entries for the x52 under the usb entry, if pedals are added after the stick you then see to sets of rudder pedals listed under the usb entry.

had other issues that had to be correct lost some hardware, new now installed.

Thanks Darkhawk

[Skuzzy]

People, please stop installing Saitek software, if you are not using SST.  It will cause long term problems.  No USB connected stick needs any software installed.

There is a bug in Saitek's software, that if you happen to get it, you cannot calibrate your stick without hacking into the registry.  This is per Saitek.

You just ask for problems with you install their software.

[ebfd11]

Skuzzy,

I had the same problem with my set up, ch fighterstick, x52 throttle and ch pro pedals, they would not hold calibration or mapping. The way I fixed it was to get a powered USB hub and walla the problem disappeared. OHH BTW DO NOT d/l the SST hardware, it will only make things worse for ya, trust me i know.

[Skuzzy]

Yes, CH Products really do need an external powered USB hub.

The problem with the Satiek software is when you get into the error condition which will not allow a proper calibration of the stick, you have to hack the registry.  Removing the software does not fix the problem.

[Ack-Ack]

Yes, CH Products really do need an external powered USB hub.

You know what's really funny and I believe also helps create confusion and more problems?  CH does not recommend using powered USB hubs with any of their products.  Despite the fact it was shown early on when I worked there that a USB powered hub resolved most CH issues and all of the testimony of customers that have resolved their issues with a USB powered hub, CH refuses to change their stance.  If you were to contact their tech support they will tell you not to use one.

ack-ack