Jump to content
The simFlight Network Forums

Recommended Posts

Pete, I would like to say 'thank you' for developing FSUIPC. I know you've worked hard on it and have used it since your first release. I was hesitant submitting to this forum, but I am now at a loss.

About 3 weeks ago in P3D v4, I noticed randomly, sometimes continuously for short spurts, my ailerons were spiking to the left. It did not matter the aircraft type nor condition. I turned on FSUIPC (version 5.122) logging and found this:

1488735 *** AXIS: Cntrl= 65695 (0x0001009f), Param= 16383 (0x00003fff) AILERON_SET

A normal aileron axis movement with my Saitek Pro Yoke shows this:
1487907 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 16383 (0xffffce91) AXIS_THROTTLE_SET

I ran many tests and cannot figure out what is sending this to the sim:
Disconnected ALL USB ports, including mouse/keyboard.
Deleted the FSUIPC INI file AND the P3D CFG file. 
Selected 'aileron' in 'Control Spike Elimination' in FSUIPC but spikes still occur.

Allowed FSUIPC to handle all axes (reverted back since this did nothing)
Checked all axes for assignments other than joystick

It happens at random times, without even touching the computer and will sometimes happen back to back (see log file attached). When at cruise it still happens but luckily the autopilot does not disconnect, though the aircraft almost rolls over. I cannot hand fly anymore worried about this spike. 

Anyone have any ideas where I can find the culprit? It seems like the 0x0001009f from the FSUIPC log file is the identifier, but I cannot figure out what that is. Or, perhaps there is a way to edit the FSUIPC file to ignore that axis?

Thanks in advance for your assistance.

fsuipc5.log

Edited by syndola

Share this post


Link to post
Share on other sites

Hi,

first thing to see in your log file snip is that you have a USB or controller problem, maybe a bad USB hub. Is power saving for USB switched off in Windows?

Quote

 6627109 ***** HID USB device reconnected: re-initialising FSUIPC connections
  6627109 ---------------------- Joystick Device Scan -----------------------
  6627109 -------------------------------------------------------------------
  6648156 ***** HID USB device reconnected: re-initialising FSUIPC connections
  6648156 ---------------------- Joystick Device Scan -----------------------
  6648156 Product= CH PRO PEDALS USB 
  6648156    Manufacturer= CH PRODUCTS
  6648156    Vendor=068E, Product=00F2 (Version 0.0)
  6648172    GUIDs returned for product: VID_068E&PID_00F2:
  6648172       GUID= {00000000-0000-0000-0000-000000000000}
  6648172       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
  6648172 -------------------------------------------------------------------
  6648172 Device acquired for use:
  6648172    Joystick ID = 0 (Registry okay)
  6648172    0=CH PRO PEDALS USB
  6648172    0.GUID={518B77E0-3626-11E5-8004-444553540000}
  6648172 -------------------------------------------------------------------
  6670281 ***** HID USB device reconnected: re-initialising FSUIPC connections
  6670281 ---------------------- Joystick Device Scan -----------------------
  6670281 Product= Saitek Pro Flight Yoke
  6670281    Manufacturer= Saitek
  6670281    Vendor=06A3, Product=0BAC (Version 3.4)
  6670297    GUIDs returned for product: VID_06A3&PID_0BAC:
  6670297       GUID= {518DE8E0-3626-11E5-8005-444553540000}
  6670297       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
  6670297 Product= CH PRO PEDALS USB 
  6670297    Manufacturer= CH PRODUCTS
  6670297    Vendor=068E, Product=00F2 (Version 0.0)
  6670297    GUIDs returned for product: VID_068E&PID_00F2:
  6670297       GUID= {00000000-0000-0000-0000-000000000000}
  6670297       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
  6670297 -------------------------------------------------------------------
  6670297 Device acquired for use:
  6670297    Joystick ID = 1 (Registry okay)
  6670297    1=Saitek Pro Flight Yoke
  6670297    1.GUID={518DE8E0-3626-11E5-8005-444553540000}
  6670297 Device acquired for use:
  6670297    Joystick ID = 0 (Registry okay)
  6670297    0=CH PRO PEDALS USB
  6670297    0.GUID={518B77E0-3626-11E5-8004-444553540000}
  6670297 -------------------------------------------------------------------
  6670531 ***** HID USB device reconnected: re-initialising FSUIPC connections
  6670531 ---------------------- Joystick Device Scan -----------------------
  6670531 Product= Saitek Pro Flight Yoke
  6670531    Manufacturer= Saitek
  6670531    Vendor=06A3, Product=0BAC (Version 3.4)
  6670531    GUIDs returned for product: VID_06A3&PID_0BAC:
  6670531       GUID= {518DE8E0-3626-11E5-8005-444553540000}
  6670531       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
  6670531 Product= CH PRO PEDALS USB 
  6670547    Manufacturer= CH PRODUCTS
  6670547    Vendor=068E, Product=00F2 (Version 0.0)
  6670547    GUIDs returned for product: VID_068E&PID_00F2:
  6670547       GUID= {00000000-0000-0000-0000-000000000000}
  6670547       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
  6670547 -------------------------------------------------------------------
  6670547 Device acquired for use:
  6670547    Joystick ID = 1 (Registry okay)
  6670547    1=Saitek Pro Flight Yoke
  6670547    1.GUID={518DE8E0-3626-11E5-8005-444553540000}
  6670547 Device acquired for use:
  6670547    Joystick ID = 0 (Registry okay)
  6670547    0=CH PRO PEDALS USB
  6670547    0.GUID={518B77E0-3626-11E5-8004-444553540000}
  6670547 -------------------------------------------------------------------

Thomas

Share this post


Link to post
Share on other sites

Thank you Thomas. I have turned off power saving for USB and will attempt to recreate the issue this evening with a new log file.

Edit: Unfortunately, that didn't work. I have created this log of about 10 minutes of my flight tonight, recording the axes (attached). This even happens when I disconnect all USBs from my computer. 

fsuipc5.log

Edited by syndola

Share this post


Link to post
Share on other sites
16 hours ago, syndola said:

Allowed FSUIPC to handle all axes (reverted back since this did nothing)

That has me concerned. Do you normally mix assignments in P3D and FSUIPC? You should choose one or the other, and if assigning in FSUIPC, disable controllers properly in P3D. Don't rely on delting assignments there.

The normal axis logging does not identify the actual source of the value being hanled. It could be from the axis itself, read by FSUIPC, or it could be from somewhere else. To check the values from the axis itself you would need to add more logging options: add these lines to the [General] section in the INI:

Debug=Please
LogExtras=x1008

Be aware, this will make the log mucvh larger.

Pete

 

 

Share this post


Link to post
Share on other sites

Pete, I only assigned all axes in FSUIPC to determine if P3D was somehow the cause, but rolled back all assignments to P3D after determining it did not matter if P3D OR FSUIPC had control over axes.

I was finally able to reproduce the spike with your suggestions. I edited the INI file to include your suggestions, then clicked on "Axis Controls," then "New Log."  I waited until the initial spike to start the logging, hoping the next one would happen quickly but it did not until later. I cannot upload one log file but two were created: fsuipc5.1.log and fsuipc5.log (attached). As soon as the ailerons went full left, I stopped the log. Please let me know if there is something else I should do. I copied the beginning 30 or so lines and then skipped to the bottom and copied the last 30 or so lines of fsuipc5.1.log:

Module base=7FF91A1B0000
Windows 10 Home 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
Prepar3D.exe version = 4.1.7.22841
Checking the Registrations now ...
User Name="Jonathan Vida"
User Addr="syndola@@hotmail.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
       47 System time = 09/01/2018 21:43:24
       47 FLT path = "C:\Users\syndola\Documents\Prepar3D v4 Files\"
       47 ------ Module Version Check ------
       47        acontain.dll: 4.1.7.22841
       47             api.dll: 4.1.7.22841
       47        controls.dll: 4.1.7.22841
       47      fs-traffic.dll: 4.1.7.22841
       63             G3D.dll: 4.1.7.22841
       63        language.dll: 4.1.7.22841
       63            sim1.dll: 4.1.7.22841
       63        visualfx.dll: 4.1.7.22841
       63         weather.dll: 4.1.7.22841
       63          window.dll: 4.1.7.22841
       63 ----------------------------------
      110 FS path = "D:\Prepar3D v4\"
      250 ---------------------- Joystick Device Scan -----------------------
      250 Product= Saitek Pro Flight Yoke
      250    Manufacturer= Saitek
      250    Vendor=06A3, Product=0BAC (Version 3.4)
      282    GUIDs returned for product: VID_06A3&PID_0BAC:
      282       GUID= {518DE8E0-3626-11E5-8005-444553540000}
      282       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      282 Product= CH PRO PEDALS USB 
      282    Manufacturer= CH PRODUCTS
      282    Vendor=068E, Product=00F2 (Version 0.0)
      282    GUIDs returned for product: VID_068E&PID_00F2:
      282       GUID= {518B77E0-3626-11E5-8004-444553540000}
      282       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      282 -------------------------------------------------------------------
      282 Device acquired for use:
      282    Joystick ID = 1 (Registry okay)
      282    1=Saitek Pro Flight Yoke
      282    1.GUID={518DE8E0-3626-11E5-8005-444553540000}
      282 Device acquired for use:
      282    Joystick ID = 0 (Registry okay)
      282    0=CH PRO PEDALS USB
      282    0.GUID={518B77E0-3626-11E5-8004-444553540000}
      282 -------------------------------------------------------------------
      329 LogOptions=00000000 00010091
      329 SimConnect_Open succeeded: waiting to check version okay
      329 Opened separate AI Traffic client okay

Note:......most of the items between these two lines are identical to the following lines...

   765719 ###JOY### Event seen, ID=66504 (0x000103C8), Joy=32, value=-519 
   765719 Axis calibration: Control=66504, Original=-519, Calibrated=-519
   765719 ###JOY### Event seen, ID=66503 (0x000103C7), Joy=33, value=5646 
   765719 Axis calibration: Control=66503, Original=5646, Calibrated=5646
   765766 ###JOY### Event seen, ID=66504 (0x000103C8), Joy=32, value=-521 
   765766 Axis calibration: Control=66504, Original=-521, Calibrated=-521
   765766 ###JOY### Event seen, ID=66503 (0x000103C7), Joy=33, value=5641 
   765766 Axis calibration: Control=66503, Original=5641, Calibrated=5641
   765813 ###JOY### Event seen, ID=66504 (0x000103C8), Joy=32, value=-523 
   765813 Axis calibration: Control=66504, Original=-523, Calibrated=-523
   765813 ###JOY### Event seen, ID=66503 (0x000103C7), Joy=33, value=5637 
   765813 Axis calibration: Control=66503, Original=5637, Calibrated=5637
   765860 ###JOY### Event seen, ID=66504 (0x000103C8), Joy=32, value=-524 
   765860 Axis calibration: Control=66504, Original=-524, Calibrated=-524
   765860 ###JOY### Event seen, ID=66503 (0x000103C7), Joy=33, value=5634 
   765860 Axis calibration: Control=66503, Original=5634, Calibrated=5634
   765907 ###JOY### Event seen, ID=66504 (0x000103C8), Joy=32, value=-525 
   765907 Axis calibration: Control=66504, Original=-525, Calibrated=-525
   765907 ###JOY### Event seen, ID=66503 (0x000103C7), Joy=33, value=5632 
   765907 Axis calibration: Control=66503, Original=5632, Calibrated=5632
   768000 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   768000 Sim stopped: average frame rate for last 375 secs = 22.4 fps
   768000    Max AI traffic was 184 aircraft (Deleted 0)
[Log closed by user request, and continued in new file]
   772985 System time = 09/01/2018 21:56:17, Simulator time = 14:06:13 (18:06Z)
   772985 *** FSUIPC log file being closed
Minimum frame rate was 8.3 fps, Maximum was 29.5 fps
Average frame rate for running time of 375 secs = 22.4 fps
Maximum AI traffic for session was 184 aircraft
Memory managed: 151 Allocs, 149 Freed

Thank you again!

fsuipc5.log

Edited by syndola

Share this post


Link to post
Share on other sites
5 hours ago, syndola said:

I edited the INI file to include your suggestions, then clicked on "Axis Controls," then "New Log."  I waited until the initial spike to start the logging

That's not a good way. Best to have logging running then simply stop it soon after it occurs. Simply extract the last portion illustration the "spike".

5 hours ago, syndola said:

Note:......most of the items between these two lines are identical to the following lines...

And which line shows a "spike" ? It all looks good to me, except that you've turned off Axis logging, which is also needed to see what P3D received. You need Axis logging enabled as well!

5 hours ago, syndola said:

I cannot upload one log file but two were created: fsuipc5.1.log and fsuipc5.log (attached).

When you click on "new log" the previous is renamed with the .1

5 hours ago, syndola said:

As soon as the ailerons went full left, I stopped the log.

Well, as you must have seen if you looked at it at all, there's no sign of that in the log, so either it isn't covered by this section of log, or it isn't anything FSUIPC which read from the axis, and is nothing else FSUIPC is doing with axes. Because of the omission of Axis logging I can't tell what P3D is receiving though.

BTW, you cannot "stop" the log except by terminating P3D. So I'm not really sure what you meant there. You can de-select the logging options. but there's really no need to do either. If there's a spike recoded in the log it will stand out as a line with much larger numbers (16383 or -16383) occurring on the axis than those shown in your fragments.

Anyway, assuming you have "captured" the time of the spike, the only other thing I can think of, apart from a serious and unlikely bug in P3D itself, is aileron trim axis spiking. Do you have anything assigned to that? Check your P3D assignments -- it isn't in FSUIPC at least, according to the log (as far as it goes).

BTW large log files ZIP up real small for attachment.

Pete

 

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

×

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.