Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I've used FSUIPC in various iterations for years with FS2002 onwards.

This is a new install of P3DV4.5 in Windows 10.

The GF quadrant is not properly recognised. Of the 6 axes, only 5, 6 going left to right are seen at all. I can assign these to Mixture set and Flaps set, but the assignment is quickly 'forgotten'.

Axes 1-4 are not recognised at all.

The Ch Eclipse Yoke and Saitek rudder pedals are recognised and can be assigned in the usual way.

I have attached the Joyscan.csv and the log file follows. 

I'd be grateful for advice.

********* FSUIPC5, Version 5.155 (27th March 2020) by Pete & John Dowson *********
Running inside Prepar3D v4
Module base=7FFCE3910000
Windows 10 Home 64 Bit reported as Build 18362, Release ID: 1903 (OS 10.0)
Prepar3D.exe version = 4.5.13.32097
Reading options from "D:\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="John Fee"
User Addr="gooneybird@yankeedodge.com"
FSUIPC5 Key is provided
WideFS7 Key is provided
       78 System time = 28/03/2020 10:07:59
      110 FLT UNC path = "\\RUDOLF\Users\howar\Documents\Prepar3D v4 Files\"
      110 Using DialogMode
      157 FS UNC path = "\\RUDOLF\D\Prepar3D v4\"
      235 ---------------------- Joystick Device Scan -----------------------
      235 Product= CH ECLIPSE YOKE
      235    Manufacturer= S
      235    Vendor=068E, Product=0051 (Version 0.0)
      250    GUIDs returned for product: VID_068E&PID_0051:
      250       GUID= {DAA25190-EC02-11E7-8006-444553540000}
      250       Details: Btns=26, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1006,Y1023,Z1023
      250 Product= Saitek Pro Flight Rudder Pedals
      266    Manufacturer= Saitek
      266    Vendor=06A3, Product=0763 (Version 1.1)
      266    GUIDs returned for product: VID_06A3&PID_0763:
      266       GUID= {DAA2C6C0-EC02-11E7-8008-444553540000}
      266       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      266 Product= GF-TQ6 Throttle System
      282    Manufacturer= GoFlight
      282    Vendor=09F3, Product=0200 (Version 1.0)
      282    GUIDs returned for product: VID_09F3&PID_0200:
      282       GUID= {DAA29FB0-EC02-11E7-8007-444553540000}
      282       Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R223,U77,V221,X41,Y42,Z227
      282 -------------------------------------------------------------------
      297 Device acquired for use:
      297    Joystick ID = 1 (Registry okay)
      297    1=CH ECLIPSE YOKE
      297    1.GUID={DAA25190-EC02-11E7-8006-444553540000}
      297 Device acquired for use:
      297    Joystick ID = 2 (Registry okay)
      297    2=Saitek Pro Flight Rudder Pedals
      297    2.GUID={DAA2C6C0-EC02-11E7-8008-444553540000}
      297 Device acquired for use:
      297    Joystick ID = 0 (Registry okay)
      297    0=GF-TQ6 Throttle System
      297    0.GUID={DAA29FB0-EC02-11E7-8007-444553540000}
      297 -------------------------------------------------------------------
      328 ### Checking Prepar3D.cfg
      328     Controllers are set to ON, using RawInput within P3D
      328 -------------------------------------------------------------------
      328 LogOptions=00000000 00000001
      328 -------------------------------------------------------------------
      328 SimConnect_Open succeeded: waiting to check version okay
      328 Opened separate AI Traffic client okay
    19328 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.13.32097 (SimConnect: 4.5.0.0)
    19328 Initialising SimConnect data requests now
    19328 FSUIPC Menu entry added
    19344 ... Using Prepar3D with Academic License
    19375 \\RUDOLF\Users\howar\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    19375 \\RUDOLF\D\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    37860 \\RUDOLF\D\Prepar3D v4\SimObjects\Airplanes\Maule_M7_260C\Maule_M7_260C.air
    37891 ### The user object is 'Maule M7 260C'
    37891 ### Mode is NORMAL
    38203 ### Mode: PAUSE on
   111547 Loading Complete ...
   111563 ### Mode is NORMAL
   112375 User Aircraft ID 2 supplied, now being used
   112391 Aircraft loaded: running normally now ...
   112641 System time = 28/03/2020 10:09:51, Simulator time = 14:00:01 (19:00Z)
   112641 Aircraft="Maule M7 260C"
   149891 ### Mode: PAUSE on
   151407 -------------------- Starting everything now ----------------------
   151407 Starting WideServer now ...
   152469 Advanced Weather Interface Enabled
   181157 Sim stopped: average frame rate for last 31 secs = 111.1 fps
   181157    Max AI traffic was 25 aircraft
   181157 -------------------------------------------------------------------
   260610 Sim stopped: average frame rate for last 63 secs = 112.4 fps
   260610    Max AI traffic was 0 aircraft
   260610 -------------------------------------------------------------------
  1152391 Sim stopped: average frame rate for last 882 secs = 113.0 fps
  1152391    Max AI traffic was 0 aircraft
  1152391 -------------------------------------------------------------------
  1154375 === Closing session: waiting for DLLStop to be called ...
  1162250 === DLLStop called ...
  1162250 === Closing external processes we started ...
  1163250 === About to kill any Lua plug-ins still running ...
  1163407 === Closing global Lua thread

John

 

FSUIPC5.JoyScan.csv

Posted
43 minutes ago, John Fee said:

The GF quadrant is not properly recognised. Of the 6 axes, only 5, 6 going left to right are seen at all. I can assign these to Mixture set and Flaps set, but the assignment is quickly 'forgotten'.

FSUIPC doesn't "forget" assignments. They are stored in your FSUIPC5.INI file as soon as you press OK.  So perhaps you need to explain what you mean by "forgotten" -- the assignments disappear? Get deleted? Or simply that you stop getting a response?

Have you made sure that Windows power management is turned off for all the USB devices listed in Device Manager which have such an option? (By default they are on).

45 minutes ago, John Fee said:

Axes 1-4 are not recognised at all.

Are they seen by Windows? Are they calibrated there? And are they seen by P3D?

Are you also running an GoFlight software? If so, are you sure they are not pre-empted by assignments there?

47 minutes ago, John Fee said:

I have attached the Joyscan.csv and the log file follows.

They look fine, but the FSUIPC5.INI file is important -- it shows how and what you've assigned.

For the log you could enable axis logging (in the Logging options tab) to see if the assignment is simply to something you didn't intend.

Pete

 

  • Like 1
Posted

Thanks.

Problem was Windows calibration. Wonky. Not sure how it became wonky as I checked it along the way.  I changed USB power management to off as advised.

Now, I am mostly sorted.

Not sure how to calibrate 5 flap detentes in the Maule with the non-detented axis lever. As it stands the flaps do a full up or down cycle using only half the available lever run.

Thanks again for your help, Pete.

John

Posted
1 hour ago, John Fee said:

Not sure how to calibrate 5 flap detentes in the Maule with the non-detented axis lever. As it stands the flaps do a full up or down cycle using only half the available lever run.

Well, you don't need detentes really. Just pretend where they'd be, or stick little markers on. If you make the markers of stiff card you might even be able to have a pointed part sticking slightly into the lever travel slot, so you can feel it.

As Thomas says, it is covered in the user guide. Calibrate each position with some leeway either side, so the precise positioning isn't critical. I've been using the FSUIPC flap calibration method like this for years with never a miss.

Pete

 

  • Like 1

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.