Jump to content
The simFlight Network Forums

FSUIPC hiccup


Recommended Posts

Hello Gents,

Purchase and install fine and fine.

Have  COCKPIT FOR YOU  737 Throttle Quadrant working together with PMDG 737.

I assigned throttle, parking brake, speed break and flaps through P3D and wanted to use

reverse thrust axis and fuel cut off axis through FSUIPC.

All went well . Deleted all default assignments I was no longer using and seems okay.

I only use FSUIPC for those few functions alone and nothing else.

However there are some oddities with the top menu bar not wanting to stay up when I want it to.

Also outside of P3D finding myself zooming in and out whilst using the mouse scroll wheel to navigate EXPLORER. (when I should be scrolling up and down)

(As if the CTRL key is pressed down)

As soon as I remove FSUIPC all goes back to normal.

Not a big deal , just curious . Any advise welcome as I'm a novice with FSUIPC

Cheers, Rick Melcher

Link to comment
Share on other sites

Do these things happen with other aircraft? Is it only with PMDG? PMDG aircraft are continually sending controls to FS, all the time, and very fast. I wonder if there's something caused by that?

Quote

 

Also outside of P3D finding myself zooming in and out whilst using the mouse scroll wheel to navigate EXPLORER. (when I should be scrolling up and down)
(As if the CTRL key is pressed down)

 

There is no way anything in FSUIPC affects keyboard use outside of the simulator. It isn't possible, because when the sim hasn't got the focus it doesn't see any of the keyboard inputs.

Press the control key and release it. If the Control was pressed and not seen to be released, the system may just be waiting for a "keyup". But unless you've been making assignments to keypresses, nothing will be doing this in the first place.

9 hours ago, Richy said:

assigned throttle, parking brake, speed break and flaps through P3D and wanted to use reverse thrust axis and fuel cut off axis through FSUIPC.

Having axis assignments in both places, even if they do not (currently) seem to conflict, is NOT a good idea. You can still assign everything in FSUIPC -- for exactly the same effect as assigning in P3D.  Just assign to the regular Axis .... controls and don't calibrate in FSUIPC. What FS and the 737 sees then is indistinguishable from what they'd see with P3D assignment.

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.