How can I start MS FSX using 737NGX's anti-collision lights on at startup? Without doing a cold and dark setup, of course. I keep getting dinged on my flight critique from FS Flight Keeper for starting engines with beacon lights off.

I'm pretty sure that you can set up the cockpit the way that you want it, then save it as a user state and set that as the default state on the CDU.

 

 

Sent from my iPad using Tapatalk HD

You can set up the flight deck anyway you wish and load it and the other startup states anytime you wish, including when you first load the aircraft.

 

This is covered exceptionally well in the NGX Introduction.

 

Good luck!

Checklists man! Gotta use your checklists and make sure you are ready for push back and engine start. I would suggest that before suggesting you just have the beacon on at all times. That doesn't sound like a very appealing solution....

Thanks, gents. Got it squared away by saving panel state with beacon lights on. Then it shows in Flight Keeper beacon lights on before starting engines. It amazes me how even if I change liveries from day to day, it still remembers this setting.

Usually, since the APU gets started just prior to push, I turn my Beacon on right after I hit the APU start sequence.

Man, I guess I should just leave all the lights on any time I go flying.  Wouldn't want to have to follow those darned checklists, and have to go flipping switches!

 

While I'm at it, I guess I should leave my car's headlights on all the time, too...

Thanks, gents. Got it squared away by saving panel state with beacon lights on. Then it shows in Flight Keeper beacon lights on before starting engines. It amazes me how even if I change liveries from day to day, it still remembers this setting.

 

I don't understand why you don't select "NGX Short" for the load panel state in the NGX FMC (in PMDG Setup). Then when you load up you will be in the cockpit with the APU running but before engine start. Then you just switch on the anti-collision light, pushback and while being pushed go through the engine start procedure. :wacko:

 

Iain Smith

Man, I guess I should just leave all the lights on any time I go flying.  Wouldn't want to have to follow those darned checklists, and have to go flipping switches!

 

While I'm at it, I guess I should leave my car's headlights on all the time, too...

 

That's how we drive here in Denmark....you know the car is moving, or about to, when it's lights are on. So running lights on at all times.

 

Italy is worse...you do not have to have lights on doing the day time, except if you are in a tunnel. So you do mountinous driving with on hand on the light switch...

 

To the OP. Just select the Beacon on prior to pushback.

Johnny - I has the same problem with FSFK not recognizing the beacon. My solution to that (and this solved many many other issues) is to save my flight with the Cessna when I exit FSX.

It's been mentioned in many threads that opening/closing FSX with a complex aircraft causes many headaches in FSX - including a sequence of events issue in FSFK's log.

 

And yes - a custom panel state is easy. I have one for first flight of the day and quick / medium turn around times. But BEACON is never on until you're about to push back.

 

Bob