FSUIPC V 5.101k Saitek Throttles Not Working

[Travis1992]

Hello. My Saitek Throttles work fine in P3Dv4 controls, however, when removing all controls from P3D, then attempting to put them on FSUIPC, It will not find any axis or buttons when trying to set up.

[Thomas Richter]

Hi,

you will need to send, after a short session, your FSUIPC5.ini / FSUIPC5.log and FSUIPC5.JoyScan.csv files. They are all located in your ...\P3Dv4_Installation_Folder\Modules\

Thomas

[Travis1992]

Here they are. I also have a CH Yoke and Rudder peddles. They both seem to be working fine. I think the rudder peddles are still being ran through P3D at the moment.

FSUIPC5.JoyScan.csv

FSUIPC5.log

FSUIPC5.ini

[Thomas Richter]

Hi,

the log and csv files show that the throttle and paddles have the same GUID assigned, very strange. Can you try connect the throttle to a different USB port, so it should get reassigned to that port.

Thomas

[Travis1992]

U had shut down the computer for about 30 min or so. I then removed my two usb's for my two saitek throttle quad's from my usb hub directly into my computers motherboard usb slots. I loaded up P3Dv4 and started a flight. Once loaded in, I had no control on my yoke that was previously working. I went into FSUIPC, and now have no response from yoke and 2 throttles.

The forums is only letting me upload 1 item for some reason, The .ini and .log files follows.

[General]
UpdatedByVersion=5101k
History=ETX3XJGPSOGBZWBJ06ZKO
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
FixControlAccel=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.0.23.21468
SimConnectUsed=4.0.0.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Throttle Quadrant
0.GUID={9825F3D0-47BB-11E7-8001-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=3X,256,F,65763,0,0,0    -{ TO SIM: AXIS_AILERONS_SET }-
1=3Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-
2=3Z,256
3=3Z,B,6016,16383,66079,0    -{ Entering=GEAR_UP }-
4=3Z,B,-5852,5888,65700,0    -{ Entering=GEAR_SET }-
5=3Z,B,-16384,-6112,66080,0    -{ Entering=GEAR_DOWN }-
6=3U,256,F,66534,0,0,0    -{ TO SIM: AXIS_FLAPS_SET }-
7=3V,256,F,66382,0,0,0    -{ TO SIM: AXIS_SPOILER_SET }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=R3,6,C65607,0     -{ELEV_TRIM_DN}-
2=R3,7,C65615,0     -{ELEV_TRIM_UP}-
3=P3,5,C65752,0     -{PARKING_BRAKES}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=C:\Prepar3D v4\Sound\
Device1=Primary Sound Driver
Device2=Digital Audio (S/PDIF) (High Definition Audio Device)
Device3=SAMSUNG-4 (NVIDIA High Definition Audio)
Device4=Speakers (USB Audio Device)

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Flaps=0,16380/16

LOG FILE:

 

********* FSUIPC5, Version 5.101k (9th June 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFFB8B80000
Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
Prepar3D.exe version = 4.0.23.21468
Checking the Registrations now ...
User Name="Travis Albrecht"
User Addr="travis1992@live.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 09/06/2017 19:06:14
        0 FLT path = "F:\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.23.21468
        0             api.dll: 4.0.23.21468
        0        controls.dll: 4.0.23.21468
        0      fs-traffic.dll: 4.0.23.21468
        0             G3D.dll: 4.0.23.21468
        0        language.dll: 4.0.23.21468
        0            sim1.dll: 4.0.23.21468
        0        visualfx.dll: 4.0.23.21468
        0         weather.dll: 4.0.23.21468
        0          window.dll: 4.0.23.21468
        0 ----------------------------------
       15 FS path = "C:\Prepar3D v4\"
      125 ---------------------- Joystick Device Scan -----------------------
      125 Product= CH PRO PEDALS USB
      125    Manufacturer= CH PRODUCTS
      125    Vendor=068E, Product=00F2 (Version 0.0)
      187    GUIDs returned for product: VID_068E&PID_00F2:
      187       GUID= {9825F3D0-47BB-11E7-8001-444553540000}
      187       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      187 Product= CH FLIGHT SIM YOKE USB
      187    Manufacturer= CH PRODUCTS
      187    Vendor=068E, Product=00FF (Version 0.0)
      187    GUIDs returned for product: VID_068E&PID_00FF:
      187       GUID= {982641F0-47BB-11E7-8008-444553540000}
      187       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X255,Y255,Z255
      187 Product= Saitek Pro Flight Quadrant
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0C2D (Version 2.1)
      203 Product= Saitek Pro Flight Quadrant
      203    Manufacturer= Saitek
      203    Vendor=06A3, Product=0C2D (Version 2.1)
      203 -------------------------------------------------------------------
      219 Device acquired for use :
      219    Joystick ID = 0 (Registry okay)
      219    0=CH PRO PEDALS USB
      219    0.GUID={9825F3D0-47BB-11E7-8001-444553540000}
      219 Device acquired for use :
      219    Joystick ID = 0 (Registry okay)
      219    0=Saitek Pro Flight Throttle Quadrant
      219    0.GUID={9825F3D0-47BB-11E7-8001-444553540000}
      219 -------------------------------------------------------------------
      219 LogOptions=00000000 00000001
      219 SimConnect_Open succeeded: waiting to check version okay
      219 Opened separate AI Traffic client okay
     2500 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0)
     2500 Initialising SimConnect data requests now
     2500 FSUIPC Menu entry added
     2515 ... Using Prepar3D with Professional License
     2515 F:\Documents\Prepar3D v4 Files\KMLB.fxml
     2515 C:\Prepar3D v4\SimObjects\Airplanes\RealAir Duke B60 V2\RealAir_Duke.air
    39594 Aircraft loaded: running normally now ...
    39594 User Aircraft ID 2 supplied, now being used
    40390 System time = 09/06/2017 19:06:55, Simulator time = 14:00:02 (18:00Z)
    40390 Aircraft="RealAir Beech Duke V2 N820MH"
    47328 Weather Mode now = Theme
    47359 Starting everything now ...
    47390 ASN active function link set
    47390 Ready for ASN WX radar
    48547 Advanced Weather Interface Enabled
    74547 Sim stopped: average frame rate for last 35 secs = 29.7 fps
    74547    Max AI traffic was 0 aircraft
   107594 === Closing session: waiting for DLLStop to be called ...
   116703 === DLLStop called ...
   116703 === Closing external processes we started ...
   117703 === About to kill any Lua plug-ins still running ...
   117844 === Closing global Lua thread
   118844 === About to kill my timers ...
   119047 === Restoring window procs ...
   119047 === Unloading libraries ...
   119047 === stopping other threads ...
   119047 === ... Button scanning ...
   119156 === ... Axis scanning ...
   119250 === Releasing joystick devices ...
   119250 === Freeing macro memory
   119250 === Removing any offset overrides
   119250 === Clearing any displays left
   119250 === Calling SimConnect_Close ...
   119953 === SimConnect_Close done!
   119953 === AI slots deleted!
   119953 === Freeing button memory ...
   119953 === Closing my Windows ...
   119953 === Freeing FS libraries ...
   120953 === Closing devices ...
   120953 === Closing the Log ... Bye Bye! ...
   120953 System time = 09/06/2017 19:08:15, Simulator time = 14:00:42 (18:00Z)
   120953 *** FSUIPC log file being closed
Minimum frame rate was 29.7 fps, Maximum was 29.9 fps
Average frame rate for running time of 40 secs = 29.7 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 20 Allocs, 19 Freed
********* FSUIPC Log file closed ***********

 

FSUIPC5.JoyScan.csv

[Pete Dowson]

3 hours ago, Travis1992 said:

Hello. My Saitek Throttles work fine in P3Dv4 controls, however, when removing all controls from P3D, then attempting to put them on FSUIPC, It will not find any axis or buttons when trying to set up.

From the JoyScan results it looks like your registry is rather severely corrputed in its registration of your devices. It have 6 entries for the Quadrant -- on 3 different GUIDs with one which looks as if it should work except that it has the same exact GUID as your Pedals (!!), another with 2 identical GUIDs (which is really wrong) and another with 3 identical GUIDs! (Even worse).

How all this happened I don't know. GUIDs are supposed to be guaranteed to be unique. It looks like something has really trashed that area.

Although I agree with Thomas that reconnecting the Quadrant to a different USB port might help, I think more needs to be done. 

First I'd like to see what is going on in the Registry in more detail. To that end, please re-run the test with FSUIPC, but first of all edit the FSUIPC5.INI file (in the P3D Modules folder) by adding these two lines to the [General] section:

Debug=Please
LogExtras=x200000

Then you could try uninstalling both the Quadrnt AND the pedals from Windows. Do that in the Windows Device Manager, and include the drivers too if it asks. Then just re-boot the system. Windows should find them and reinstall them, hopefully cleanly.

If things still need tidying up after that I can fix the Registry for you. I'f need to give you instructions on using the Windows RegEdit program to extract the section to be fixed so you can send it to me. I'd tidy it up and send it back, or alternatively give you instructions on how to do that.

[LATER]

I've just seen you newer post, after the one from Thomas.

The JoyScan shows that all moving them around has done is given the Pdals and one of the 6 listed Quadrants the same GUID. In fact now there are no unique GUIDs.

I think it really will need manual intervention in the Registry. But first try uninstlling all three items in the Device Manager and re-booting. Don't worry about where they are plugged in.

I'm off to bed now, but I'll catch up in the morning.

Pete

 

 

[Travis1992]

I added the lines into my .ini file. Something similar happened to me before. I did what was listed here while I was waiting:

I remember something similar to this helping in the past. It seems to have only brought back my yoke again. Doing the uninstalling devices and rebooting now.

[Pete Dowson]

2 minutes ago, Travis1992 said:

I added the lines into my .ini file.

And .. where is the log please? Those lnes were so that it would log more about what it saw in the Registry! That was the point. Sorry if I wasn't clear.

4 minutes ago, Travis1992 said:

Something similar happened to me before. I did what was listed here while I was waiting:

Which part of "what was listed" there?  Some of that is specific to a particular device makers, ones with VID_06A3 or VID_0738.  The 06A3 is Saitek. (your 6 listed Quadrants are all VID_06A3).

Your CH devices have VID_068E.

Pete

 

[Travis1992]

Sorry, I was planning on posting another post very shortly after that one. I uninstalled all the drivers in the HID section. While doing so, it uninstalled my wireless keyboard and mouse. Now my keyboard doesn't type and only does the additional things like changing volume hotkeys. Keyboard works perfectly in the BIOS. I have tried uninstalling the drivers again to fix it, and about anything else I could think of and nothing.

On the other hand, FSUIPC and my controllers all work perfectly now. Thanks for that bit. If you have anything in mind with the keyboard situation, please share. If not, this can be closed. Thank you Pete and Thomas.

(Using an entirely different wireless keyboard and mouse to type this)

 

[General]
UpdatedByVersion=5101k
History=159UAVS1J088C9OWDJCXN
InitDelayDevicesToo=No
Annotate=Yes
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
FixControlAccel=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
Console=No
Debug=Please
LogExtras=x200000
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.0.23.21468
SimConnectUsed=4.0.0.0

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
0=CH PRO PEDALS USB
0.GUID={9825F3D0-47BB-11E7-8001-444553540000}
3=CH FLIGHT SIM YOKE USB
3.GUID={982641F0-47BB-11E7-8008-444553540000}
1=Saitek Pro Flight Throttle Quadrant
1.GUID={E08B6580-4D4A-11E7-8001-444553540000}
2=Saitek Pro Flight Throttle Quadrant
2.GUID={FEFF7550-4D4B-11E7-8003-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=3X,256,F,65763,0,0,0    -{ TO SIM: AXIS_AILERONS_SET }-
1=3Y,256,F,65762,0,0,0    -{ TO SIM: AXIS_ELEVATOR_SET }-
2=3Z,256
3=3Z,B,6016,16383,66079,0    -{ Entering=GEAR_UP }-
4=3Z,B,-5852,5888,65700,0    -{ Entering=GEAR_SET }-
5=3Z,B,-16384,-6112,66080,0    -{ Entering=GEAR_DOWN }-
6=3U,256,F,66534,0,0,0    -{ TO SIM: AXIS_FLAPS_SET }-
7=3V,256,F,66382,0,0,0    -{ TO SIM: AXIS_SPOILER_SET }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=R3,6,C65607,0     -{ELEV_TRIM_DN}-
2=R3,7,C65615,0     -{ELEV_TRIM_UP}-
3=P3,5,C65752,0     -{PARKING_BRAKES}-

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=C:\Prepar3D v4\Sound\
Device1=Primary Sound Driver
Device2=Digital Audio (S/PDIF) (High Definition Audio Device)
Device3=SAMSUNG-4 (NVIDIA High Definition Audio)
Device4=Speakers (USB Audio Device)

[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=No
FlapsSetControl=0
FlapDetents=No
ReverserControl=66292
Reverser1Control=66422
Reverser2Control=66425
Reverser3Control=66428
Reverser4Control=66431
MaxThrottleForReverser=256
AileronTrimControl=66731
RudderTrimControl=66732
CowlFlaps1Control=66162
CowlFlaps2Control=66163
CowlFlaps3Control=66164
CowlFlaps4Control=66165
SteeringTillerControl=0
MaxSteerSpeed=60
Flaps=0,16380/16

 

********* FSUIPC5, Version 5.101k (9th June 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFCC8BC0000
Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
Prepar3D.exe version = 4.0.23.21468
Checking the Registrations now ...
User Name="Travis Albrecht"
User Addr="travis1992@live.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 09/06/2017 21:36:44
        0 FLT path = "F:\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.23.21468
        0             api.dll: 4.0.23.21468
        0        controls.dll: 4.0.23.21468
        0      fs-traffic.dll: 4.0.23.21468
        0             G3D.dll: 4.0.23.21468
        0        language.dll: 4.0.23.21468
        0            sim1.dll: 4.0.23.21468
        0        visualfx.dll: 4.0.23.21468
        0         weather.dll: 4.0.23.21468
        0          window.dll: 4.0.23.21468
        0 ----------------------------------
        0 FS path = "C:\Prepar3D v4\"
      109 #### Initialising Dlrectinput Axis Scanning ...
      109    (Entry from GetRegisteredOptions)
      109 ---------------------- Joystick Device Scan -----------------------
      109 Checking: \\?\hid#vid_068e&pid_00f2#8&982a2f7&3&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      109    Usage=4, UsagePage=1, =Game Controller
      109 Product= CH PRO PEDALS USB
      109    Manufacturer= CH PRODUCTS
      109    Vendor=068E, Product=00F2 (Version 0.0)
      125    GUIDs returned for product: VID_068E&PID_00F2:
      125       GUID= {9825F3D0-47BB-11E7-8001-444553540000}
      125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      125 Checking: \\?\hid#vid_06a3&pid_0c2d#8&1ec2068f&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      125    Usage=4, UsagePage=1, =Game Controller
      125 Product= Saitek Pro Flight Quadrant
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0C2D (Version 2.1)
      125    GUIDs returned for product: VID_06A3&PID_0C2D:
      125       GUID= {E08B6580-4D4A-11E7-8001-444553540000}
      125       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      125       GUID= {FEFF7550-4D4B-11E7-8003-444553540000}
      125       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      125 Checking: \\?\hid#vid_06a3&pid_0c2d#8&c0855ea&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      125    Usage=4, UsagePage=1, =Game Controller
      125 Product= Saitek Pro Flight Quadrant
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0C2D (Version 2.1)
      125 Checking: \\?\hid#vid_068e&pid_00ff#8&ec0e1e0&4&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      125    Usage=4, UsagePage=1, =Game Controller
      125 Product= CH FLIGHT SIM YOKE USB
      141    Manufacturer= CH PRODUCTS
      141    Vendor=068E, Product=00FF (Version 0.0)
      141    GUIDs returned for product: VID_068E&PID_00FF:
      141       GUID= {982641F0-47BB-11E7-8008-444553540000}
      141       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X255,Y255,Z255
      141 -------------------------------------------------------------------
      141 ****** Registry scanning: VID=068E, PID=00F2 ******
      141 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00F2\Calibration\0"
      141    ... and a "GUID" value
      141    GUID= {9825F3D0-47BB-11E7-8001-444553540000}
      141    1st registry entry has Joystick ID=0
      141    Attempting to acquire this device for checking ...
      141    Acquired device, GetDeviceState to check values
      141    ... Okay so far
      141    Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_068E&PID_00F2"
      141    Joy Name = "CH PRO PEDALS USB"
      141 ****** Registry scanning: VID=06A3, PID=0C2D ******
      141 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\0"
      141    ... and a "GUID" value
      141    GUID= {E08B6580-4D4A-11E7-8001-444553540000}
      141    1st registry entry has Joystick ID=1
      141    Attempting to acquire this device for checking ...
      141    Acquired device, GetDeviceState to check values
      141    ... Okay so far
      141 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_06A3&PID_0C2D\Calibration\1"
      141    ... and a "GUID" value
      141    GUID= {FEFF7550-4D4B-11E7-8003-444553540000}
      141    2nd registry entry has Joystick ID=2
      141    Attempting to acquire this device for checking ...
      141    Acquired device, GetDeviceState to check values
      141    ... Okay so far
      141    Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0C2D"
      141    Joy Name = "Saitek Pro Flight Throttle Quadrant"
      141 ****** Registry scanning: VID=068E, PID=00FF ******
      141 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_068E&PID_00FF\Calibration\0"
      141    ... and a "GUID" value
      141    GUID= {982641F0-47BB-11E7-8008-444553540000}
      141    1st registry entry has Joystick ID=3
      141    Attempting to acquire this device for checking ...
      141    Acquired device, GetDeviceState to check values
      141    ... Okay so far
      141    Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_068E&PID_00FF"
      141    Joy Name = "CH FLIGHT SIM YOKE USB"
      141 -------------------------------------------------------------------
      141 UserDevices: 0.GUID={9825F3D0-47BB-11E7-8001-444553540000}
      141 UserDevices: 1.GUID={E08B6580-4D4A-11E7-8001-444553540000}
      141 UserDevices: 2.GUID={FEFF7550-4D4B-11E7-8003-444553540000}
      141 UserDevices: 3.GUID={982641F0-47BB-11E7-8008-444553540000}
      141    Acquired device, GetDeviceState to check values
      141 Device acquired for use :
      141    Joystick ID = 0 (Registry okay)
      141    0=CH PRO PEDALS USB
      141    0.GUID={9825F3D0-47BB-11E7-8001-444553540000}
      141    Acquired device, GetDeviceState to check values
      141 Device acquired for use :
      141    Joystick ID = 1 (Registry okay)
      141    1=Saitek Pro Flight Throttle Quadrant
      141    1.GUID={E08B6580-4D4A-11E7-8001-444553540000}
      141    Acquired device, GetDeviceState to check values
      141 Device acquired for use :
      141    Joystick ID = 2 (Registry okay)
      141    2=Saitek Pro Flight Throttle Quadrant
      141    2.GUID={FEFF7550-4D4B-11E7-8003-444553540000}
      141    Acquired device, GetDeviceState to check values
      141 Device acquired for use :
      141    Joystick ID = 3 (Registry okay)
      141    3=CH FLIGHT SIM YOKE USB
      141    3.GUID={982641F0-47BB-11E7-8008-444553540000}
      141 -------------------------------------------------------------------
      141 ---------- Making INI JoyNames Section ----------
      141     wJoyIDsUsed=000F
      141    Joy#0: Name = CH PRO PEDALS USB
      141    Joy#0: GUID = {9825F3D0-47BB-11E7-8001-444553540000}
      141    Joy#1: Name = Saitek Pro Flight Throttle Quadrant
      141    Joy#1: GUID = {E08B6580-4D4A-11E7-8001-444553540000}
      141    Joy#2: Name = Saitek Pro Flight Throttle Quadrant
      141    Joy#2: GUID = {FEFF7550-4D4B-11E7-8003-444553540000}
      141    Joy#3: Name = CH FLIGHT SIM YOKE USB
      141    Joy#3: GUID = {982641F0-47BB-11E7-8008-444553540000}
      141 -------------------------------------------------
      141   Checking and assigning Joy Letters as needed
      141 #### Completed Dlrectinput Axis Scanning
      141 LogOptions=00000000 02000011
      156 SimConnect_Open succeeded: waiting to check version okay
      156 Opened separate AI Traffic client okay
     2797 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0)
     2797 Initialising SimConnect data requests now
     2797 FSUIPC Menu entry added
     2797 ... Using Prepar3D with Professional License
     2813 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
     2813 F:\Documents\Prepar3D v4 Files\KMLB.fxml
     2813 C:\Prepar3D v4\SimObjects\Airplanes\RealAir Duke B60 V2\RealAir_Duke.air
    37875 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    37906 Aircraft loaded: running normally now ...
    37906 User Aircraft ID 2 supplied, now being used
    38672 System time = 09/06/2017 21:37:22, Simulator time = 14:00:02 (18:00Z)
    38672 Aircraft="RealAir Beech Duke V2 N820MH"
    45375 Weather Mode now = Theme
    45656 Starting everything now ...
    45656 Note: "C:\Prepar3D v4\Modules\PFCcom64.DLL", Error 126 (The specified module could not be found. )
    45656 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    45688 ASN active function link set
    45688 Ready for ASN WX radar
    45688 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
    60313 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    61359 Advanced Weather Interface Enabled
   153078 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   153078 Sim stopped: average frame rate for last 93 secs = 29.8 fps
   153078    Max AI traffic was 0 aircraft
   154141 === Closing session: waiting for DLLStop to be called ...
   188625 === DLLStop called ...
   188625 === Closing external processes we started ...
   189625 === About to kill any Lua plug-ins still running ...
   189766 === Closing global Lua thread
   190766 === About to kill my timers ...
   190969 === Restoring window procs ...
   190969 === Unloading libraries ...
   190969 === stopping other threads ...
   190969 === ... Button scanning ...
   191078 === ... Axis scanning ...
   191172 === Releasing joystick devices ...
   191172 === Freeing macro memory
   191172 === Removing any offset overrides
   191172 === Clearing any displays left
   191172 === Calling SimConnect_Close ...
   191875 === SimConnect_Close done!
   191875 === AI slots deleted!
   191875 === Freeing button memory ...
   191875 === Closing my Windows ...
   191875 === Freeing FS libraries ...
   192875 === Closing devices ...
   192875 === Closing the Log ... Bye Bye! ...
   192875 System time = 09/06/2017 21:39:57, Simulator time = 14:01:42 (18:01Z)
   192875 *** FSUIPC log file being closed
Minimum frame rate was 29.7 fps, Maximum was 29.9 fps
Average frame rate for running time of 100 secs = 29.8 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 49 Allocs, 48 Freed
********* FSUIPC Log file closed ***********

 

 

[Pete Dowson]

5 hours ago, Travis1992 said:

I uninstalled all the drivers in the HID section.

That wasn't a good idea. Should have only uninstalled the joystick devices.

5 hours ago, Travis1992 said:

it uninstalled my wireless keyboard and mouse. Now my keyboard doesn't type and only does the additional things like changing volume hotkeys. Keyboard works perfectly in the BIOS. I have tried uninstalling the drivers again to fix it, and about anything else I could think of and nothing.

Some wireless devices work fine with later versions of Windows out of the box, some need their own drivers installed. You'd probably need to find those (the pair would have come with a disk) or go to their website.

5 hours ago, Travis1992 said:

On the other hand, FSUIPC and my controllers all work perfectly now.

Good.

Pete

 

[Travis1992]

Okay, so I got my keyboard back... At the price of having to do some sort of weird half reinstall thing. Keep in mind, this was a clean machine not long ago with a fresh install of windows 10. And I have always had some problem with Saitek TQ and windows 10. Anyway I have started over and started the files over fresh. New files attached below. I did delete the saitek registry like before, and also attempted to uninstall drivers for both CH and Saitek in device manager, then reset. after 8+ hours of fighting with this stupid keyboard thing(between yesterday and today), I will wait patiently for your response. That registry cleanup may be a good idea. Thanks Pete.

FSUIPC5.JoyScan.csv

FSUIPC5.log

FSUIPC5.ini

[Pete Dowson]

9 minutes ago, Travis1992 said:

I will wait patiently for your response.

What do you want me to say? You seem to have 3 good devices each with their own unique GUIDs:

[JoyNames]
AutoAssignLetters=No
0=CH PRO PEDALS USB  
0.GUID={9825F3D0-47BB-11E7-8001-444553540000}
2=Mad Catz Pro Flight Throttle Quadrant
2.GUID={98261AE0-47BB-11E7-8003-444553540000}
3=CH FLIGHT SIM YOKE USB  
3.GUID={982641F0-47BB-11E7-8008-444553540000}

Isn't that what you wanted?

Pete

 

[Travis1992]

I have 2 Mad Catz Pro Flight Throttle Quadrant's connected, Only one is working(in FSUIPC). Everything else is working.

[Thomas Richter]

Hi,

as your latest log file shows you are back to FSUIPC5.10, why that? Please install first latest interim version FSUIPC5101m_TEST.zip

********* FSUIPC5, Version 5.10 (1st June 2017) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
FSUIPC5.dll version = 5.1.0.0
...    
16 System time = 10/06/2017 19:02:24

Thomas

[Pete Dowson]

Oh dear. As Thomas noticed, you are using the original version of FSUIPC5. Problems with joystick scanning were fixed by 5.101j and the scan is certainly working well now.

Pete

 

[Travis1992]

Thank you Thomas. You are correct, I just updated to the latest 5101m. This must have happened when I did an OS recovery when I was dealing with my keyboard problem. It probably brought it back to 5.10. Sorry for the extra trouble guys, and I thank you again for the excellent and timely support. Everything is working fine again (knocks on wood). If this happens to anyone else, I would suggest them to go into Device Manager and then click View, then Show Hidden Devices. This could show something that is conflicting.

[Travis1992]

I hate to be posting yet another problem : / This is not an FSUIPC problem, however, I was hoping someone could point me in the right direction. It seems that my 2 throttle ID's may have flip flopped on each other and now P3D also thinks it is a new controller, adding default controls again. This is very annoying and I think it is very possible it will happen again. Now all my controls I just put into FSUIPC are on the opposite quadrants... Has anyone had this problem? Any solution? Thanks.

FSUIPC5.log

FSUIPC5.ini

FSUIPC5.JoyScan.csv

[Thomas Richter]

Hi,

1/ when assigning the functions in FSUIPC it is best to assign everything in FSUIPC instead of having it mixed, some in FSUIPC and others in FS/P3D. So you should disable Controllers in FS/P3D (in P3D in controls menu bottom)

2/ Best is to change this in FSUIPC5.ini file to Yes
AutoAssignLetters=No
change to
AutoAssignLetters=Yes
This will assign letters to each controller. Your assignments will then be related to the letter instead of the number. When it then happens that identical controller changed their number because of i.e. a USB port swap by mistake, then you can easily swap the assigned letter of the controller and the defined functions stays with the 'letter'

When Controllers are disabled in FS/P3D then any change of controller doesn't has any effect in FS/P3D.

Thomas

[Travis1992]

I will try this. Thank you Thomas. All controls are set up through FSUIPC currently. However, the disable controllers option is not checked. I will do this as well. If I have any more concerns, I will reply again.