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.

not configured to start the engines ?

Featured Replies

Hi,I bought the voice+button edition today. I read the help file and all that but I must be making a mistake becase the FO won't start the engines because it is telling me w'ere not properly configured to do that.No idea what it is that I'm doing wrong.Any help appreciated.Vic

  • Commercial Member
Hi,I bought the voice+button edition today. I read the help file and all that but I must be making a mistake becase the FO won't start the engines because it is telling me w'ere not properly configured to do that.No idea what it is that I'm doing wrong.Any help appreciated.Vic
Hi Vic,Did you read the manual?Did you run the "Before Start Procedure"?Do the engines have an 'air' source? APU or External Air?Cheers,
  • Author
Did you read the manual?
Yes, I read the help/manual.
Did you run the "Before Start Procedure"?
Yes.
Do the engines have an 'air' source? APU or External Air?
Yes.APU.
  • Author

Yes it is but the *:* is stuck, repeating "we're not properly configured for engine start" over and over and no way to shut him up. It's getting annoying. I had to kill fsx.exe form task manager to stop him.P.S. I forgot to add that fs2crew seems to also cause crashes.I don't usually get ntdll.dll much but ever since fs2crew was installed they do happen fairly often.

  • Commercial Member
Yes it is but the *:* is stuck, repeating "we're not properly configured for engine start" over and over and no way to shut him up. It's getting annoying. I had to kill fsx.exe form task manager to stop him.P.S. I forgot to add that fs2crew seems to also cause crashes.I don't usually get ntdll.dll much but ever since fs2crew was installed they do happen fairly often.
How much PSI (air pressure) is shown in the duct?Can you start the engines manually?Regarding NTDLL.DLL, please see this thread for good some tips and advice.Cheers,
  • Author
How much PSI (air pressure) is shown in the duct?
About 25 ?
Can you start the engines manually?
If i dont use fs2crew at all i can start the engines manually ok but if I use fs2crew, that is follow the procedures till I'm stuck, there's always something wrong and then the answer would be no i cannot start them.I must be doing something wrong along the way. Is there any fool proof step by step guide that i could use to make fs2crew work for me ? i have to say that the manual included does not help me much. I need something that tells what to do fromt he beginning to end like i had for the other fs2crew products..Once you do it once or 2ce then it should be ok.I must be one of the chosen few who's too slow to figure things out. lolThanks
Regarding NTDLL.DLL, please see this thread for good some tips and advice.
I had those ntdll.dll problems awhile back because of them drivers.I updated them and all was fine till I installed fs2crew.
  • Author
Hi,Please email me at admin * fs2crew * .comI'll help you via a Remote Desktop. It's much easier if I can "see" what you're doing.Cheers,
problem solved. ThanksEDIT: Solution in case anyone else is interested is that you as Captain need to set the Fuel Levers to "Idle"... the FO does not do that part. It's your responsibility.

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.