Registered Controller Detected in P3DV3.4 But Not in FSUIPC v4.966c

[gkamilar]

Hello Pete, 
I have been using my registered version of FSUIPC4 (v4.955) very successfully with Win 7/64, FSX-SP2, PMDG-737NGX and the following hardware:

• CH Eclipse Yoke
• Thrustmaster Rudder Pedals
• FSXThrottle Pro Tek 737 Quadrant

I recently created a fresh install of Win 7/64 on a second SDD with Prepar3D (v3.4.22), PMDG 737NGX (new license for P3D) and the same hardware.  This install features FSUIPC (v4.966c).

After "disabling controllers" and deleting all axis assignments in P3D I have successfully assigned the yoke and rudder pedals in FSUIPC.  However, I get no response when I try to assign the  throttle quadrant.  The same is true for buttons & switches; I get no data when I scan and move the quadrant axes / buttons.  All three devices are registered in the FSUIPC.ini file (attached) and all three can be assigned and calibrated within P3D if I enable the controllers for troubleshooting purposes only.  I have used the JoyId utility to swap all of the axes to different ID's and back again without effect.  I have run the HID Scanner (log attached) but it looks okay to me.  I have spent several days over the past 2 weeks poring through the forum for a solution without success so I hope you can tell me what is wrong.  

I have attached a log coverering the following actions:

Start Prepar3D > start a scenario > Open FSUIPC > assign ailerons > assign elevator > assign rudder > assign left brake > assign right brake > close FSUIPC & save assignments > move all of the assigned axes > open FSUIPC > try to assign quadrant axes without seeing any input > close FSUIPC > move quadrant axes > move aileron axis again > close Prepar3D.

Many thanks in advance,
Gregg 

FSUIPC Files.zip

[Pete Dowson]

23 minutes ago, gkamilar said:

However, I get no response when I try to assign the  throttle quadrant.  The same is true for buttons & switches; I get no data when I scan and move the quadrant axes / buttons.  All three devices are registered in the FSUIPC.ini file (attached) and all three can be assigned and calibrated within P3D if I enable the controllers for troubleshooting purposes only.

Sounds like the ProTek Throttle has a non-standard Registry setting for its GUID.  Please od two things:

1. Download this test version of FSUIPC: FSUIPC 4.966j. Save a copy of your FSUIPC4.DLL and FSUIPC4.INI from the Modules folder, and copy this later version in, overwriting the 4.966c version.

2. Edit the FSUIPC4.INI file, adding these lines to the [General] section:
Debug=Please
LogExtras=x200000

3. Run P3D, just get to the fully ready-to-fly stage, then close it. Save both the INI and LOG files to ZIP up with some more data:

4. Now please get me some stuff from your Registry, as follows:

Export the contents of these sections of the Registry:

HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\MediaProperties\PrivateProperties

 

Do this by running RegEdit from the Windows start menu, going down the Explorer style layers to those and with that layer selected do File-Export give them each a name (it’ll save as a .reg file -- please do not give it a different filetype in that dialogue).

 

Then rename them from .reg to .txt so the mail system or my anti-virus doesn’t reject them (.reg files, when run, change the registry), and send those to me at petedowson@btconnect.com.

 

Okay? thanks.

 

I have similar problems with a couple of Saitek X-55s, unsolved yet, but from the above data I should be able to provide work-arounds, as I did for the X-55s. I am currently trying to get hold of an X-55 set so I can sort it out properly.

 

Pete

 

[gkamilar]

Requested files on the way via email

[gkamilar]

Pete,

Looks like there was a problem when the controller was installed by Windows.  I disabled and then re-enabled the controller in Device Manager and the problem disappeared.  Thanks for your help!!