Jump to content
The simFlight Network Forums

Only 1 of 2 Throttle Quads Recognized


Recommended Posts

I just installed FSUIPC5  and when I try to assign axes only one of my two throttle quads is recognized.  The Options>Controls in P3Dv4 does see both quads and allows assignments to both. When I look at the FSUIPC5.ini file,my joystick, rudders, and one quad are listed:

[JoyNames]
AutoAssignLetters=No
0=Logitech Extreme 3D
0.GUID={8E3EB8A0-30F7-11E7-8003-444553540000}
2=Saitek Pro Flight Throttle Quadrant
2.GUID={8E498E10-30F7-11E7-8009-444553540000}
3=Saitek Pro Flight Rudder Pedals
3.GUID={8E498E10-30F7-11E7-800B-444553540000}

In my FSUIPC4.ini, all four devices are recognized:

AutoAssignLetters=No
0=Logitech Extreme 3D
0.GUID={8E3EB8A0-30F7-11E7-8003-444553540000}
1=Saitek Pro Flight Throttle Quadrant
1.GUID={8E496700-30F7-11E7-8008-444553540000}
2=Saitek Pro Flight Throttle Quadrant
2.GUID={8E498E10-30F7-11E7-8009-444553540000}
3=Saitek Pro Flight Rudder Pedals
3.GUID={8E498E10-30F7-11E7-800B-444553540000}

If I try to add the lines from my FSUIPC4.ini for device #1 into my FSUIPC5.ini it still does not work and the lines that I added are deleted. See attached Log file. Any ideas?

Charlie

 

********* FSUIPC5, Version 5.10 (1st June 2017) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
FSUIPC5.dll version = 5.1.0.0
Reading options from "X:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Running inside Prepar3D v4 on Windows 10
Module base=7FFE98590000
User Name="Charles Felix"
User Addr="cfelix@gte.net"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 03/06/2017 13:35:10
        0 FLT path = "C:\Users\Charlie\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 = "X:\Program Files\Lockheed Martin\Prepar3D v4\"
       78 ---------------------- Joystick Device Scan -----------------------
       94 Product= Logitech Extreme 3D
       94    Manufacturer= Logitech
       94    Vendor=046D, Product=C215 (Version 2.4)
       94    GUIDs returned for product: VID_046D&PID_C215:
       94       GUID= {8E3EB8A0-30F7-11E7-8003-444553540000}
       94       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X1023,Y1023,Z255
      109 Product= Saitek Pro Flight Quadrant
      109    Manufacturer= Saitek
      109    Vendor=06A3, Product=0C2D (Version 2.0)
      109    GUIDs returned for product: VID_06A3&PID_0C2D:
      109       GUID= {8E496700-30F7-11E7-8008-444553540000}
      109       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      109       GUID= {8E498E10-30F7-11E7-8009-444553540000}
      109       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      109 Product= Saitek Pro Flight Quadrant
      109    Manufacturer= Saitek
      109    Vendor=06A3, Product=0C2D (Version 2.0)
      109 Product= Saitek Pro Flight Rudder Pedals
      109    Manufacturer= Saitek
      109    Vendor=06A3, Product=0763 (Version 1.0)
      109    GUIDs returned for product: VID_06A3&PID_0763:
      109       GUID= {8E498E10-30F7-11E7-800B-444553540000}
      109       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      109 -------------------------------------------------------------------
      109 Device acquired for use:
      109    Joystick ID = 0 (Registry okay)
      109    0=Logitech Extreme 3D
      109    0.GUID={8E3EB8A0-30F7-11E7-8003-444553540000}
      109 Device acquired for use:
      109    Joystick ID = 2 (Registry okay)
      109    2=Saitek Pro Flight Throttle Quadrant
      109    2.GUID={8E498E10-30F7-11E7-8009-444553540000}
      109 Device acquired for use:
      109    Joystick ID = 3 (Registry okay)
      109    3=Saitek Pro Flight Rudder Pedals
      109    3.GUID={8E498E10-30F7-11E7-800B-444553540000}
      109 -------------------------------------------------------------------
      125 LogOptions=00000000 00000001
      125 -------------------------------------------------------------------
      125 SimConnect_Open succeeded: waiting to check version okay
      125 Opened separate AI Traffic client okay
     2390 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0)
     2390 Initialising SimConnect data requests now
     2390 FSUIPC Menu entry added
     2390 ... Using Prepar3D with Professional License
     2406 C:\Users\Charlie\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
     2406 X:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    35203 Aircraft loaded: running normally now ...
    35203 User Aircraft ID 2 supplied, now being used
    35609 System time = 03/06/2017 13:35:46, Simulator time = 13:35:14 (18:35Z)
    35609 Aircraft="F-22 Raptor - 525th Fighter Squadron"
    51640 Starting everything now ...
    52797 Advanced Weather Interface Enabled
    86312 Sim stopped: average frame rate for last 36 secs = 60.0 fps
    86312    Max AI traffic was 34 aircraft (Deleted 0)
   137453 === Closing session: waiting for DLLStop to be called ...
   146859 === DLLStop called ...
   146859 === Closing external processes we started ...
   147859 === About to kill any Lua plug-ins still running ...
   148000 === Closing global Lua thread
   149000 === About to kill my timers ...
   149203 === Restoring window procs ...
   149203 === Unloading libraries ...
   149203 === stopping other threads ...
   149203 === ... Button scanning ...
   149312 === ... Axis scanning ...
   149406 === Releasing joystick devices ...
   149406 === Freeing macro memory
   149406 === Removing any offset overrides
   149406 === Clearing any displays left
   149406 === Calling SimConnect_Close ...
   151515 === SimConnect_Close done!
   151515 === AI slots deleted!
   151515 === Freeing button memory ...
   151515 === Closing my Windows ...
   151515 === Freeing FS libraries ...
   152515 === Closing devices ...
   152515 === Closing the Log ... Bye Bye! ...
   152515 System time = 03/06/2017 13:37:43, Simulator time = 13:36:17 (18:36Z)
   152515 *** FSUIPC log file being closed
Minimum frame rate was 59.7 fps, Maximum was 61.2 fps
Average frame rate for running time of 63 secs = 59.9 fps
Maximum AI traffic for session was 34 aircraft
Memory managed: 34 Allocs, 33 Freed
********* FSUIPC Log file closed ***********
 

 

 

Edited by CharlieF
Link to comment
Share on other sites

Same here: only one quadrant is recognized, in FSUIP5.ini this is te section related the Joystick:

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Rudder Pedals
0.GUID={28EBBAA0-829A-11E5-800C-444553540000}
A=Saitek Pro Flight Rudder Pedals
A.GUID={28EBBAA0-829A-11E5-800C-444553540000}
E=usb pad << MISSING JOYSTICK >>
E.GUID={28EBBAA0-829A-11E5-8002-444553540000}
F=usb pad << MISSING JOYSTICK >>
F.GUID={28EBBAA0-829A-11E5-8003-444553540000}
G=usb pad << MISSING JOYSTICK >>
G.GUID={28EBBAA0-829A-11E5-8004-444553540000}
4=usb pad
4.GUID={28EBBAA0-829A-11E5-8001-444553540000}
H=usb pad
H.GUID={28EBBAA0-829A-11E5-8001-444553540000}
5=Saitek Pro Flight Yoke
5.GUID={28EBBAA0-829A-11E5-800D-444553540000}
C=Saitek Pro Flight Yoke
C.GUID={28EBBAA0-829A-11E5-800D-444553540000}
B=Saitek Pro Flight Quadrant << MISSING JOYSTICK >>
B.GUID={28EBBAA0-829A-11E5-800E-444553540000}
7=Saitek Pro Flight Quadrant
7.GUID={28EBBAA0-829A-11E5-800F-444553540000}
D=Saitek Pro Flight Quadrant
D.GUID={28EBBAA0-829A-11E5-800F-444553540000}
8=Pro Flight Cessna Trim Wheel
8.GUID={4F45C0A0-7B6A-11E6-8001-444553540000}
L=Pro Flight Cessna Trim Wheel
L.GUID={4F45C0A0-7B6A-11E6-8001-444553540000}
K=<< MISSING JOYSTICK >>

On of the Quadrants is in teh list, but with the << MISSING JOYSTICK >>

the others not recognized are VRInsight switchwes (I have opened another topic for that

KR

Joe

 

Link to comment
Share on other sites

8 hours ago, CharlieF said:

Here is the file you requested.

Thank you. It does show that FSUIPC is making a mistake here. One I don't understand at present. The csv file shows it has everything correct for both quadrants, yet it marks one down as bad for no apparent reason. I might have to add some extra logging in that area to work out why!

Were you using FSUIPC4 beforehand? If so, which version, and did that see both okay? If so, and is was a recent version, can you show me the FSUIPC4.Joyscan.csv from that, please?

Either way, can you please add these lines to the [General] section of the FSUIPC5.INI file, then just run P3D4 again please and show me both the LOG and the FSUIPC5.Joyscan.csv file again?

Debug=Please
LogExtras=x200000

Pete

 

Link to comment
Share on other sites

Please download version 5.101. I don't think it will fix it but it will give me more information.  Before running it add

Debug=Please
LogExtras=x200000

to the [General] section of FSUIPC5.INI. And please show me the Log, the INI and the CSV file resulting.

Pete

 

Link to comment
Share on other sites

4 hours ago, vlooi said:

FSUIPC5 sees only 2 of the 3 quadrants, the P3DV4 sees all. No problems in P3DV3.

What version of FSUIPC are you using in P3Dv3?The current one is 4.967 and should have identical results to FSUIPC5.01. If not, please show me the same logging and CSV file from FSUIPC4.

Pete

 

Link to comment
Share on other sites

Hi Pete,

I just upgraded my P3Dv3 FSUIPC4 from 4.966c to 4.967 and as you expected I now have the same problem in P3Dv3.  Here are the csv and log files from P3Dv3 after the upgrade to 4.967.  Also attached is the log file from FSUIPC5 after upgrading to 5.01 and adding the 2 lines to the ini file.  I could not include the CSV file due to size limitations.  If you need it I can send it under a separate post.

 

Charllie

Edited by CharlieF
Link to comment
Share on other sites

2 hours ago, CharlieF said:

Here are the csv and log files from P3Dv3 after the upgrade to 4.967.  Also attached is the log file from FSUIPC5 after upgrading to 5.01 and adding the 2 lines to the ini file.  I could not include the CSV file due to size limitations.

The CSV is most important and should be the smallest file of the lot! Everyone else manages to attach it fine.

Anyway, there were no other files with your post at all!

Pete

 

 

Link to comment
Share on other sites

I edited my previous post to let you know that upgrading to 4.97 in FSUIPC4 did cause the same problem as you expected (that post now includes the csv and log files from FSUIPC4) .  Glad to head you have a solution.  Thanks again for all your work.  

 

Charlie Felix

 

Link to comment
Share on other sites

3 minutes ago, CharlieF said:

that post now includes the csv and log files from FSUIPC4

No, there are no files in that post. 

4 minutes ago, CharlieF said:

Glad to head you have a solution.

I haven't solved it yet. The files help me narrow it down, that's all.

Pete

 

Link to comment
Share on other sites

Just now, vlooi said:

I'm not allowed more than 20kb upload?

I don't know, but each file should be less than that in any case, and you can always insert the text from the files into the message using the <> buton above the edit area.

Or even ZIP them. As they are all text files they ZIP down really small!

Pete

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.