Jump to content
The simFlight Network Forums
Sign in to follow this  
Craig Haskell

Dual Saitek Throttles

Recommended Posts

Hi everyone,

Recently purchased FSUIPC5 but 2 things no longer work since the upgrade.

1) It does not fully support dual Saitek throttles ( 2 quadrant the throttle lever and prop pitch lever is not detected correctly, it is either on full or off)

2) Since the new 5.112 release it no longer save any axis assignments or button controls

Can anyone say if this is being fixed?

 

FSUIPC5 Install.log

FSUIPC5.ini

FSUIPC5.JoyScan.csv

Share this post


Link to post
Share on other sites
10 hours ago, Craig Haskell said:

Can anyone say if this is being fixed?

First try the interim update 5.113, available for three weeks now.

Also the FSUIPC5.LOG file is required, not the install log.

Your JoyScan file shows:

Y, x1E, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 3, 3, 0, {8EE9DBB0-7BB4-11E7-8009-444553540000}, {8EE9DBB0-7BB4-11E7-8009-444553540000}, {8EE9DBB0-7BB4-11E7-8009-444553540000}, Y, Y
Y, x1E, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, 1, 1, 0, {8ED6A1D0-7BB4-11E7-8005-444553540000}, {8ED6A1D0-7BB4-11E7-8005-444553540000}, {8ED6A1D0-7BB4-11E7-8005-444553540000}, Y, Y
Y, x1E, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, 2, 2, 1, {8EE017B0-7BB4-11E7-8006-444553540000}, {8EE017B0-7BB4-11E7-8006-444553540000}, {8EE017B0-7BB4-11E7-8006-444553540000}, Y, Y
N, x01, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, -1, 4, 2, {NULL}, {E2A751A0-8E7A-11E7-8008-444553540000}, {NULL}, N, N
Y, x1E, x06A3, x0BAC, Saitek Pro Flight Yoke, 0, 0, 0, {8ED198C0-7BB4-11E7-8003-444553540000}, {8ED198C0-7BB4-11E7-8003-444553540000}, {8ED198C0-7BB4-11E7-8003-444553540000}, Y, Y

So, THREE Saitek throttles, one of which appears to be an invalid Registry entry. 

The INI file sohws these detected and entered correctly.

0=Saitek Pro Flight Yoke
0.GUID={8ED198C0-7BB4-11E7-8003-444553540000}
1=Saitek Pro Flight Throttle Quadrant
1.GUID={8ED6A1D0-7BB4-11E7-8005-444553540000}
2=Saitek Pro Flight Throttle Quadrant
2.GUID={8EE017B0-7BB4-11E7-8006-444553540000}
3=Saitek Pro Flight Rudder Pedals
3.GUID={8EE9DBB0-7BB4-11E7-8009-444553540000}

So what exactly do you mean by this?

Quote

1) It does not fully support dual Saitek throttles ( 2 quadrant the throttle lever and prop pitch lever is not detected correctly, it is either on full or off)

The two throttles are fine, which different assignable IDs 1 and 2.

What "prop piitch lever" do you have on your throttles?  Do you mean you assigned one? To an FS control or direct to FSUIPC calibration.  For it to be full on or off  it sould s like you've not bothered to calibrate correctly. Your INI file sohws no calibrations whatsoever, and only an Axis assignment to and uncalibrated Elevator assigned "direct to calibration".

Pete

 

 

 

 

Share this post


Link to post
Share on other sites

Sorry Pete, I should've explained myself better.

The axis that do not work correctly are 2X and 2Y. 2Z Works fine

With the levers, when they are set at half way they are showing in FSUIPC as 16384 just above half way and -16384 just below half way they do not show the whole range.

At first I thought it was the throttle than and got a replacement from Logitech (formerly Saitek), but this proved not to be it.

I can plug them in separately and both work fine, I have also tried on a friends computer and again they work fine.

I have now calibrated all the levers (6) but they still show a positive and negative figure at the half way point.

Have added another set of files if you wouldn't mind taking a look.

Thank you

Craig

 

 

********* FSUIPC5, Version 5.113 (21st August 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFE713D0000
Windows 10 Enterprise 64 Bit reported as Build 10586, Release ID: 1511 (OS 10.0)
Prepar3D.exe version = 4.0.28.21686
Checking the Registrations now ...
User Name="Craig Haskell"
User Addr="craighaskell@outlook.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 12/09/2017 23:31:22
        0 FLT path = "C:\Users\Craig Haskell\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.28.21686
        0             api.dll: 4.0.28.21686
        0        controls.dll: 4.0.28.21686
        0      fs-traffic.dll: 4.0.28.21686
        0             G3D.dll: 4.0.28.21686
        0        language.dll: 4.0.28.21686
        0            sim1.dll: 4.0.28.21686
        0        visualfx.dll: 4.0.28.21686
        0         weather.dll: 4.0.28.21686
        0          window.dll: 4.0.28.21686
        0 ----------------------------------
       16 FS path = "G:\Prepar3D v4\"
      125 ---------------------- Joystick Device Scan -----------------------
      125 Product= Saitek Pro Flight Rudder Pedals
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0763 (Version 1.0)
      141    GUIDs returned for product: VID_06A3&PID_0763:
      141       GUID= {8EE9DBB0-7BB4-11E7-8009-444553540000}
      141       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      141 Product= Saitek Pro Flight Yoke
      141    Manufacturer= Saitek
      141    Vendor=06A3, Product=0BAC (Version 3.2)
      141    GUIDs returned for product: VID_06A3&PID_0BAC:
      141       GUID= {8ED198C0-7BB4-11E7-8003-444553540000}
      141       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      141 Product= Saitek Pro Flight Quadrant
      141    Manufacturer= Saitek
      141    Vendor=06A3, Product=0C2D (Version 2.2)
      141    GUIDs returned for product: VID_06A3&PID_0C2D:
      141       GUID= {8ED6A1D0-7BB4-11E7-8005-444553540000}
      141       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      141       GUID= {8EE017B0-7BB4-11E7-8006-444553540000}
      141       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X127,Y127,Z255
      156 Product= Saitek Pro Flight Quadrant
      156    Manufacturer= Saitek
      156    Vendor=06A3, Product=0C2D (Version 2.2)
      156 -------------------------------------------------------------------
      187 Device acquired for use:
      187    Joystick ID = 3 (Registry okay)
      187    3=Saitek Pro Flight Rudder Pedals
      187    3.GUID={8EE9DBB0-7BB4-11E7-8009-444553540000}
      187 Device acquired for use:
      187    Joystick ID = 0 (Registry okay)
      187    0=Saitek Pro Flight Yoke
      187    0.GUID={8ED198C0-7BB4-11E7-8003-444553540000}
      187 Device acquired for use:
      187    Joystick ID = 1 (Registry okay)
      187    1=Saitek Pro Flight Throttle Quadrant
      187    1.GUID={8ED6A1D0-7BB4-11E7-8005-444553540000}
      187 Device acquired for use:
      187    Joystick ID = 2 (Registry okay)
      187    2=Saitek Pro Flight Throttle Quadrant
      187    2.GUID={8EE017B0-7BB4-11E7-8006-444553540000}
      187 -------------------------------------------------------------------
      234 LogOptions=00000000 00000001
      250 SimConnect_Open succeeded: waiting to check version okay
      250 Opened separate AI Traffic client okay
     1984 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.28.21686 (SimConnect: 4.0.0.0)
     1984 Initialising SimConnect data requests now
     1984 FSUIPC Menu entry added
     1984 ... Using Prepar3D with Academic License
     2000 C:\Users\Craig Haskell\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
     2000 G:\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
   172047 G:\Prepar3D v4\SimObjects\Airplanes\JF_PA28_Warrior\JF_PA28_Warrior.air
   213484 User Aircraft ID 1 supplied, now being used
   213516 Aircraft loaded: running normally now ...
   213562 System time = 12/09/2017 23:34:56, Simulator time = 14:00:01 (19:00Z)
   213578 Aircraft="JF PA28 Warrior II G-SIXT"
   219594 Starting everything now ...
   219687 ASN active function link set
   219687 Ready for ActiveSky WX radar with additional data
   220922 Advanced Weather Interface Enabled
   749844 Sim stopped: average frame rate for last 536 secs = 22.5 fps
   749844    Max AI traffic was 0 aircraft
   985250 Sim stopped: average frame rate for last 130 secs = 26.4 fps
   985250    Max AI traffic was 0 aircraft
  1043219 Sim stopped: average frame rate for last 34 secs = 30.3 fps
  1043219    Max AI traffic was 0 aircraft
  1434828 Sim stopped: average frame rate for last 112 secs = 29.8 fps
  1434828    Max AI traffic was 0 aircraft
  1438000 === Closing session: waiting for DLLStop to be called ...
  1447250 === DLLStop called ...
  1447250 === Closing external processes we started ...
  1448250 === About to kill any Lua plug-ins still running ...
  1448391 === Closing global Lua thread
  1449406 === About to kill my timers ...
  1449594 === Restoring window procs ...
  1449594 === Unloading libraries ...
  1449594 === stopping other threads ...
  1449594 === ... Button scanning ...
  1449703 === ... Axis scanning ...
  1449797 === Releasing joystick devices ...
  1449797 === Freeing macro memory
  1449797 === Removing any offset overrides
  1449797 === Clearing any displays left
  1449797 === Calling SimConnect_Close ...
  1450500 === SimConnect_Close done!
  1450500 === AI slots deleted!
  1450500 === Freeing button memory ...
  1450500 === Closing my Windows ...
  1450500 === Freeing FS libraries ...
  1451500 === Closing devices ...
  1451500 === Closing the Log ... Bye Bye! ...
  1451500 System time = 12/09/2017 23:55:34, Simulator time = 14:13:34 (19:13Z)
  1451500 *** FSUIPC log file being closed
Minimum frame rate was 21.2 fps, Maximum was 39.9 fps
Average frame rate for running time of 812 secs = 24.4 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 381 Allocs, 381 Freed
********* FSUIPC Log file closed ***********
 

FSUIPC5.ini

FSUIPC5.JoyScan.csv

Share this post


Link to post
Share on other sites
1 hour ago, Craig Haskell said:

With the levers, when they are set at half way they are showing in FSUIPC as 16384 just above half way and -16384 just below half way they do not show the whole range.

Assuming it isn't just that you've not calibrated properly, or have assigned in the Sim, not in FSUIPC, and have some silly slider values there, then that's usually a Saitek installation bug. It is fixable in the Registry. I'm really surprisded they've not fixed that yet.  Take a look at the FAQ subforum. There are entries about that.

1 hour ago, Craig Haskell said:

I can plug them in separately and both work fine,

Sorry, that doesn't make sense. Where are you observing this "showing in FSUIPC as 16384 just above half way and -16384 just below half way"?

And what exactly do you mean by "they do not show the whole range."?

This from the LOG shows it is actually a Registry or installation problem. the two quadrands show totally different ranges for the two of them on the X and Y axes:

Max=R0,U0,V0,X255,Y255,Z255
Max=R0,U0,V0,X127,Y127,Z255

And the INI file shows you've not even calibrated any axis. They are all default values. You should ALWAYS calibrate when assigning direct to calibration, as you have.

Pete

 

Share this post


Link to post
Share on other sites

Pete,

Thank you so much for all your help.

I completely missed the right FAQ.  All is now working.

Your help has been very much appreciated.

Kind regards

Craig

Share this post


Link to post
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

Sign in to follow this  

×