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.

Engine start bug!

Featured Replies

Hello,

 

When i started to use the T7 i didn't get any problems for weeks. Now I get more and more problems to start the engines. I follow the engine start procedure like in the tutorial, but often, the oil temperature stucks around the outside air temperature, while the engine thrust remains around 21.4%. Then I can move the Thrust Levers full forward, but the engine doesn't react. I can load a new panel state, restart FSX but i always get the problem. Sometime one engine is affected, sometime both are. I can't fix the problem and the use of the 777 is more luck as plan these days...

Vincent Schmoeckel

  • Commercial Member

 

 


I can't fix the problem and the use of the 777 is more luck as plan these days...

 

I've never seen this issue and it didn't come up in testing.

 

Have you changed anything with your hardware, FSUIPC, or other settings?  Additionally, did you set the 777 as your default aircraft in Flight Sim?

Kyle Rodgers

  • Author

Hi,

 

thanks for your help until now. I've fixed the problem so far, i think. Normally, the standart flight with the Cessna 172 is with running engines. I had configured the standart flight with the PMDG747 in C&D Mode. After i changed this to the standart Cessna with running engines, my T7 works.

 

VIncent Schmoeckel

The default flight in FSX is the Ultralight, not the Cessna.

I'm pretty sure it says in the introduction manual that came with the 777 (you read that, right?) to NOT mess with the default flight settings as it can produce unfavorable results.

 

If it doesn't say that then...don't mess with the default flight.

AJ Pongress

Boeing777_Banner_BetaTeam.jpg

It does.

 

Never change the default flight, other than position. It WILL break all sorts of things.

--Peter Fabian 
RTFM.jpg

  • Commercial Member

For what it's worth, I used the default Cessna for years and it was fine.  I haven't bothered changing it after I reformatted last, though.

 

As far as your engine issues, I can't think of anything that could be causing it.

Kyle Rodgers

I had this issue on a saved flight . the #2 just wouldn't go . Deleted the saved situation and rebooted the PC and haven't seen it since.

 

Eric W

The default flight in FSX is the Ultralight, not the Cessna.

I'm pretty sure it says in the introduction manual that came with the 777 (you read that, right?) to NOT mess with the default flight settings as it can produce unfavorable results.

 

If it doesn't say that then...don't mess with the default flight.

Any default FSX aircraft will be OK, it's all about initialising internal FSX variables properly. I don't use the ultralight as it reminds me of the "gamey" side of FSX. So I prefer the C172 as default. Works perfectly for me.

 

You certainly should "mess" with the default flight by making the location the same time zone as yours if you want to minimise local time problems in FSX.  Some other complex addons (not PMDG) need you to "mess" with it to get them to initialise properly. So leaving it untouched is not really an option.

 

The main thing principle to stick to is never use a complex addon as your default aircraft.

ki9cAAb.jpg

  • Commercial Member

 

 


The main thing principle to stick to is never use a complex addon as your default aircraft.

 

That's what I always thought it was, but I was starting to have doubts based on things I'd seen recently.  Thanks for the confirmation.

Kyle Rodgers

Create an account or sign in to comment

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.