Jump to content
The simFlight Network Forums

Recommended Posts

Posted (edited)

FSUIPC5 Install.logHello;

I have registered FSUIPC5 (5.102) and the latest 747 (1.17.21) from PMDG . My problem is that the engine seems to start correctly, but the oil temps stay in yellow range (22). When I attempt to move the throttles (mapped the FSUIPC) they move flawlessly but no increase in N1. If I just start with the default 747 state everything works fine. If I use any other state where the engines need to be started I get this problem.

I've contacted PMDG support who asked me to disable FSUIPC5 and then the engines started and performed normally.

Any help would be appreciated.

Win10 x64

P3dv4

 

FSUIPC5.log

FSUIPC5.ini

Edited by skewr
added log files
Posted
On 6/19/2017 at 3:45 AM, skewr said:

I've contacted PMDG support who asked me to disable FSUIPC5 and then the engines started and performed normally.

PMDG's implementation needs throttle axes assigned normally (whether in P3D or FSUIPC), to the normal Axis controls (Axis throttleN set in FSUIPC), and not calibrated. The problem is that they intercepts the axes at the same level as FSUIPC does, whereas calibrated values have to be fed into FS at a lower level to avoid an infinite loop.

Pete

 

Posted

Thank you for the quick reply.

I'm having the same issue after:

1) Checking the "profile specific" box in FSUIPC and unassigning the throttles

2) Deleting all default throttle related axis in P3d v4 Axis Assignments

3) Assigning the CH Throttle Quadrants to their respective P3D Events (For example Engine 1 throttle axis  in P3D assigned to the Y Axis which corresponds to the first throttle on the CH throttle quadrant)

I then tried

A) Setting throttles though FSUIPC (by checking "Send to FS as normal axis")

B) tried checking and unchecking "Exclude THROTTLEn_set"

 

Are there any other workarounds?

THanks for trying to assist.

Posted
1 hour ago, skewr said:

Deleting all default throttle related axis in P3d v4 Axis Assignments

Are you saying you had controllers enabled in P3D, yet were asdsigning in FSUIPC? That is a complete no-no and will likely give all sorts of problems. Either use FSUIPC for assignment OR P3D, do NOT mix them!

1 hour ago, skewr said:

Checking the "profile specific" box in FSUIPC and unassigning the throttles

Whay has "Profile Specific" got to do with it. dod you only have throttles assigned in a specific profile for the PMDG aircraft?

1 hour ago, skewr said:

Assigning the CH Throttle Quadrants to their respective P3D Events (For example Engine 1 throttle axis  in P3D assigned to the Y Axis which corresponds to the first throttle on the CH throttle quadrant)

Sorry, where are you talking about assigning now?

I'm confused altogether by your message i'm afraid. I don't know where you started from now where you are going to.

Just a clarification. Assigning in FSUIPC to "Axis ... Set" contorls, for ANY axis, with Controllers DISABLED in P3D, is exactly the same as not assigning anything in FSUIPC, enabling controllers in P3D, and assigning the same axes there.

Pete
 

Posted

Are you saying you had controllers enabled in P3D, yet were asdsigning in FSUIPC? That is a complete no-no and will likely give all sorts of problems. Either use FSUIPC for assignment OR P3D, do NOT mix them!

No sir. What I am saying is that I tried both conditions separately. I used P3D first THEN I deleted the assignments in P3D and used FSUIPC as normal axis.

Whay has "Profile Specific" got to do with it. dod you only have throttles assigned in a specific profile for the PMDG aircraft?

Because the 777 works perfectly through FSUIPC  and I would like to keep any changes I make exclusive to the 747, therefore I used Profile specific

10 hours ago, Pete Dowson said:

Sorry, where are you talking about assigning now?

I'm confused altogether by your message i'm afraid. I don't know where you started from now where you are going to.

Just a clarification. Assigning in FSUIPC to "Axis ... Set" contorls, for ANY axis, with Controllers DISABLED in P3D, is exactly the same as not assigning anything in FSUIPC, enabling controllers in P3D, and assigning the same axes there.

I suppose I wasn't clear enough? I was trying to inform you HOW I setup the CH Quadrant in P3D.

Where am I going to? I'd like to be flying with the 747 utilizing FSUIPC.

Posted
51 minutes ago, skewr said:

Because the 777 works perfectly through FSUIPC  and I would like to keep any changes I make exclusive to the 747, therefore I used Profile specific

The PMDG 777? My understanding is that all three PMDG Boeing products, 737, 747 and 777 use the same methods for their throttle axis control inputs, so the same methods in FSUIPC should apply and work with both.

53 minutes ago, skewr said:

Where am I going to? I'd like to be flying with the 747 utilizing FSUIPC.

Assign to Axis throttle1 set (etc) in FSUIPC, do NOT calibrate -- i.e. press "RESET" for each throttle in the 4 throttles page in the Calibration tab both with AND without your profile selected. Then, if it works with your P3D assignment, it works through FSUIPC because it will then be doing identical things.

That is the way it works in FSUIPC for every one else. It will work for you unless there's something wrong with your 777 installation.

Post your FSUIPC5.INI file when you've done, and I'll check it. In your previously posted one you had all your axes assigned Directly (not good for PMDG) AND all Calibrated (not good for PMDG) -- and all without any Profile specific selection at all.

In fact, if I now understand you correctly and you actually had problems with no assignments in FSUIPC but all in P3D, then it obviously is a 777 problem. Try uninstalling it and reinstalling.

Pete

 

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.