Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Fun from defining the fuel controls in P3D4 and FSUIPC5

Featured Replies

Maybe this can save someone some pain in the future.  Or, at least, give someone a good laugh at my expense.   When I installed P3D4 and had no add-on aircraft and no FSUIPC5 I defined all of the controls from the P3D Controls menu, obviously.  When I installed the 777 and FSUIPC5 I removed all of the P3D4 control definitions, but forgot the fuel control switches.  That resulted in a journey covering about four hours over two days trying to figure out why the engines sometimes weren't responding to the throttles.

I could start the engines normally but, when I advanced the throttles, they moved on the screen and the throttle position indication moved on the EICAS, but the engines wouldn't spool up.  I also saw that the engine bleed air valves weren't opening.  When I loaded the Default panel, sometimes everything worked fine but usually the engines shut off after initialization with ENG FAIL L and ENG FAIL R displayed.  

To isolate the problem I disabled FSUIPC and defined the throttles in P3D4 again.  The engines worked correctly.  I then re-enabled FSUIPC5 but only enabled the axis controls.  The engines still worked.  I added the button section and the engines didn't work.  So I began adding the button definitions to FSUIPC one set at a time until I found that the fuel controls (EVT_CONTROL_STAND_ENG1_START_LEVER 70152 & EVT_CONTROL_STAND_ENG2_START_LEVER 70153) caused the  odd behavior.   At that point dawn broke over the rocks and I realized that the fuel controls in P3D4 were still active (I'm not at my sim PC and I don't remember the exact control name).  I deleted the P3D4 definitions and Bob's your uncle (or voila) (or firm palm slap to the forehead) the engines worked properly.  

On the plus side, I spent a lot of time watching the Air synoptic screen during engine startup, and it was interesting and informative to see the isolation valves opening and closing to route the APU bleed air to the engine start valve, and then switching the flow for the other engine start, finally opening the engine bleeds after APU shutdown.  I'm also glad that I didn't open a ticket for this.

Larry

[email protected] HT, Maximus XI Code, 16GB TridentZ @ 4000, 2080Ti FTW3 Ultra Hydro, ekwb EK-KIT P360 water, 4K@30, W10 Pro, P3D v5.0

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.