Jump to content
The simFlight Network Forums
Iain Williams

FSUPIC V5.22 not reading axis controls P3D V4.1

Recommended Posts

Hello Peter

I have just updated to WIN 10 and P3D V 4.1.   I also have purchased FSUPIC 5.

My yoke, rudder and throttle settings have been calibrated in WIN 10 in the game controller section (Leo Bodnar cards).  When I open P3D, the game will read these settings (not using FSUPIC).

I then installed FSUPIC5 (5.22) and attempted to calibrate using FSUPIC.  The axis controller tab will not read the WIN 10 settings - when I move the yoke, throttle, etc there are no numbers in the box..  Therefore, calibration cannot be done in FSUPIC.

However, if I open the game controller tab in WIN 10, click properties, OK, and close again, and then open FSUPIC, the settings in the axis controller tab are visible and can be read.  I have done many tests and the only way FSUPIC will read the initial settings is if I open the calibration section in WIN 10 and click OK prior to opening P3D

I attach the appropriate logs.

All the P3D settings have been removed.  Calibration is only by FSUPIC

Do you have any suggestions to rectify this  issue ?

Thank you.  Kind Regards,   Iain

 

FSUIPC5 Install.log

FSUIPC5_prev.log

FSUIPC5.ini

FSUIPC5.log

Share this post


Link to post
Share on other sites
2 hours ago, Iain Williams said:

I then installed FSUPIC5 (5.22) and attempted to calibrate using FSUPIC.  The axis controller tab will not read the WIN 10 settings

Two points here. First, there is not yet a "5.22" so I guess you mean 5.122.

Second, the Axes tab is for assigning axes, not calibrating. You can calibrate no matter where you assign, in FSUIPC or in P3D.

There are 5 devices recognised by FSUIPC:

      984 Device acquired for use:
      984    Joystick ID = 0 (Registry okay)
      984    0=BU0836A Interface
      984    0.GUID={54768E70-F318-11E7-8003-444553540000}

      984 Device acquired for use:
      984    Joystick ID = 1 (Registry okay)
      984    1=Po.Joystick id
      984    1.GUID={54768E70-F318-11E7-8006-444553540000}

      984 Device acquired for use:
      984    Joystick ID = 2 (Registry okay)
      984    2=BU0836 Interface
      984    2.GUID={54768E70-F318-11E7-8007-444553540000}

      984 Device acquired for use:
      984    Joystick ID = 3 (Registry okay)
      984    3=BU0836 Interface
      984    3.GUID={54768E70-F318-11E7-800B-444553540000}

      984 Device acquired for use:
      984    Joystick ID = 4 (Registry okay)
      984    4=Button Box Interface
      984    4.GUID={0835D8F0-F31C-11E7-8016-444553540000}

Where are the "yoke, throttle, etc" connected?  I can give you parameters to obtain more logging to see what is going on, but first please go into your Windows Device Manager, find every USB entry, and for those which have power management options in their "Properties" (right-click for that), disable power management.

BTW does P3D itself have this problem? Have you tried it? If you only wish to use FSUIPC for calibration, you can assign in P3D instead if you wish.

2 hours ago, Iain Williams said:

All the P3D settings have been removed.  Calibration is only by FSUPIC

You mean "assignment"! Calibration can only be done after assignment!

You never need to "remove" all P3D settings, merely disable the controllers -- one checkbox. Much cleaner and safer!

Pete

 

Share this post


Link to post
Share on other sites

Hello Peter

Thank you for your prompt reply.

Yes  5.122 (my apologies for not being precise)

I am using Leo Bodnar BU0836A, BU0836 cards to control yoke, throttle (thrust levers/speed brake/reverse thrust/flaps/various buttons on TQ), rudder and steering tiller.  These are connected directing to the USB of the motherboard.

Normally I register these cards and calibrate initially in the game controller of WIN 10.  This has been done and has been checked.

FSUPIC does not read these initial settings.  When I open the axis tab to assign the various items (for example elevators) FSUPIC does not 'see' or 'communicate' with the registered settings in WIN 10 for the device.  This is the same for all the cards.   However, if I either, prior to or after starting P3D, open the game controller in WIN 10 and select any of the attached cards, click properties and then press OK and close out of the game controller, FSUPIC will then 'see' the outputs and then allow the axis to be assigned and calibrated.

Interestingly, once I have the calibration correctly done in FSUPIC - everything is perfect.   But, if I close down the PC and start it up again and open P3D, the same issue occurs - the settings do not have any affect in the game.  They only become live' when I open the game controller as mentioned above.

I have taken your advice and reset all keystrokes and axis to default in P3D with only the 'controller' tab deselected (controllers turned off).  I am coming from FSX so am still learning P3D.

I also have disabled any power management associated with USBs.

I also tried P3D (calibrating within the game), however the same thing occurs as discussed above.

Do you have any suggestions on how I can resolve this issue ?  

On another note, everything mentioned above was working perfecting in WIN 7 with FSX (not that this helps...)

Thank you,    Iain

Share this post


Link to post
Share on other sites
3 minutes ago, Iain Williams said:

FSUPIC does not read these initial settings.  When I open the axis tab to assign the various items (for example elevators) FSUPIC does not 'see' or 'communicate' with the registered settings in WIN 10 for the device.  This is the same for all the cards. 

Well, the log does show it gets data about those devices, as shown RED below:

      906 Product= Button Box Interface
      906    Manufacturer= Leo Bodnar
      906    Serial Number= B28218
      906    Vendor=1DD2, Product=1140 (Version 1.4)
      922    GUIDs returned for product: VID_1DD2&PID_1140:
      922       GUID= {0835D8F0-F31C-11E7-8016-444553540000}
      922       Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      922 Product= BU0836 Interface
      922    Manufacturer= Leo Bodnar
      922    Serial Number= B19406
      922    Vendor=16C0, Product=05B5 (Version 1.34)
      922    GUIDs returned for product: VID_16C0&PID_05B5:
      922       GUID= {54768E70-F318-11E7-8007-444553540000}
      922       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X638,Y1023,Z488
      922       GUID= {54768E70-F318-11E7-800B-444553540000}
      922       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V1023,X908,Y889,Z621
      922 Product= BU0836A Interface
      922    Manufacturer= Leo Bodnar
      922    Serial Number= B31477
      922    Vendor=16C0, Product=05BA (Version 1.34)
      922    GUIDs returned for product: VID_16C0&PID_05BA:
      922       GUID= {54768E70-F318-11E7-8003-444553540000}
      922       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4093,Y0,Z0
      922 Product= BU0836 Interface
      922    Manufacturer= Leo Bodnar
      922    Serial Number= B17614
      922    Vendor=16C0, Product=05B5 (Version 1.34)

      922 Product= Po.Joystick id 
      922    Manufacturer= PoLabs 
      922    Serial Number= 2.11582
      922    Vendor=1DC3, Product=1001 (Version 16.0)
      922    GUIDs returned for product: VID_1DC3&PID_1001:
      922       GUID= {54768E70-F318-11E7-8005-444553540000}
      922       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      922 -------------------------------------------------------------------

Some of the rest of your last message seems to be a duplication of what you said before.

23 minutes ago, Iain Williams said:

I have taken your advice and reset all keystrokes and axis to default in P3D with only the 'controller' tab deselected (controllers turned off). 

Where do you see such advice?

I certainly wouldn't deselect any keystrokes in P3D!  They are needed for all sorts of things. there is NEVER any need to do so. If you assign a keystroke in FSUIPc it overrides the one in P3D, if that one is used. The manual is clear on this.

And I actually said you don't need to do anything with buttons or axes in P3D, just disable controllers.

26 minutes ago, Iain Williams said:

I am coming from FSX so am still learning P3D.

None of this is any different at all in P3D compared to FSX! True, the sim's menus are re-arranged. FSUIPC is exactly the same in all this area, just a 64-bit version of the same logic.

27 minutes ago, Iain Williams said:

I also tried P3D (calibrating within the game), however the same thing occurs as discussed above.

It realy cannot be the same in the Calibration sections. THAT's where you calibrate, and THATuses the FS controls, it doesn't read axes at all. it merely intercepts the controls themselves. I think you are looking it the wrong place.

29 minutes ago, Iain Williams said:

On another note, everything mentioned above was working perfecting in WIN 7 with FSX

It is more likely the difference between Win7 and Win10, though what on Earth is wrong with your Win10 I've no idea I'm afraid.

Did you try selecting RAW mode in any of the Axis assignments, to see if using the raw values gives anything? That bypasses Windows calibration.

Another way to check the values from the axes you could add more logging options: add these lines to the [General] section in the INI:

Debug=Please
LogExtras=x1008

Be aware, this will (or should!) make the log much larger.

Pete

 

Share this post


Link to post
Share on other sites

Thanks for the note Peter.

Yes P3D is similar to FSX.  At the time of writing I had only about 45 minutes into P3D of which most was looking the FSUPIC issue.

Thank you for the logging files.  I will add the line to the .ini and see what they report.

I did try the RAW values, however, they were no values.

Kind Regards,   Iain

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.