Let's put it this way. IF you install a 3rd party plane and you are experiencing problems you should try using a default plane before you do further troubleshooting.E.g. if you load the brilliant Flight Replicas Super Cub and your loaded situation was a plane with the generator switched OFF, you will loose all electrics in your Super Cub soon, as it's draining the battery.As the Super Cub doesn't have a generator switch you simply NEED a default plane to switch the generator ON before selecting the Super Cub.And that's by far not the only problem you can experience when you directly start with an add-on plane.

False statement. If you want aircraft to behave correctly, especially complex aircraft.... you must always ensure the default aircraft and default flight are showing when FS loads. There are many reasons for it, mostly due to the fact that saved flights are not reliably accurate and cause problems.

WRONG. I've tested all of my payware add-ons such as the RealAir Spitfire and I've had no problems so far. Dave.

WRONG. I've tested all of my payware add-ons such as the RealAir Spitfire and I've had no problems so far.

hate to point out that you are incorrect dave. the 'load a default FS aircraft' instruction solves multiple issues with addon aircraft having panel faults and incorrect behaviors.--

I always start-up FSX with the default 172 in 2D mode cold and dark. There are still many third party aircrfat that work best by doing so. Starting FSX 'sets' everything using the default aircraft, particularly in 2D mode, which I've always been told is still recommended to be on the safe side.It really isn't a problem. As soon as FS boots to my start-up, I switch to VC mode, then load my aircrfat. With everything else that must be done before taxi, this really isn't a major issue, and good 'insurance' for a flight without glitches by not doing so.

hate to point out that you are incorrect dave. the 'load a default FS aircraft' instruction solves multiple issues with addon aircraft having panel faults and incorrect behaviors.--

I believe you were pointing out with the VC buttons NOT being clickable in the FSX 737PIC? I also encountered a problem with the airspeed indicator always going overspeed even after only going within 180-195KIAS. Does loading the default 737-800 have any effect with those issues? Dave.

Both FS9 and FSX require proper initialization by loading default flights at startup. There are approximately 28 different features which iniatilaize properly when this is observed.The fact that you are not experiencing issues when loading a complex aircraft as your "default flight" is likely a matter of luck or having previously loaded a "default flight" then loading/saving the complex flight.

I believe you were pointing out with the VC buttons NOT being clickable in the FSX 737PIC?

are you running VATSIM's FSinn?

I also encountered a problem with the airspeed indicator always going overspeed even after only going within 180-195KIAS.

possible ... as you should not have a overspeed warning that slow unless you are very high, or low with flaps extended.

Does loading the default 737-800 have any effect with those issues?

possible to yes.support forum -http://forum.iemit.com--

WRONG. I've tested all of my payware add-ons such as the RealAir Spitfire and I've had no problems so far. Dave.

Dave, you are misunderstanding what was stated. Ed did not say one has to LOAD the default a/c, only that it should be visible in the Preview Window before choosing the a/c you actually want. Just the presence of the default in the Preview Window will load all of the extra state data from the "default flight" that isn't saved in a normal saved flight file...

Dave, you are misunderstanding what was stated. Ed did not say one has to LOAD the default a/c, only that it should be visible in the Preview Window before choosing the a/c you actually want. Just the presence of the default in the Preview Window will load all of the extra state data from the "default flight" that isn't saved in a normal saved flight file...

That's great news. I have the Cessna 172 come up on the preview screen always. I'll just select my "start aircraft" from there then. This is really starting to make a lot of sense to me.Thanks.Stan

Just the presence of the default in the Preview Window will load all of the extra state data from the "default flight" that isn't saved in a normal saved flight file...

THIS part of the post should be a sticky, Bill, as I - and a few others I suspect - didn't know this, and have always loaded then saved the darned thing prior to running a "serious" aircraft. Many thanks.

THIS part of the post should be a sticky, Bill, as I - and a few others I suspect - didn't know this, and have always loaded then saved the darned thing prior to running a "serious" aircraft. Many thanks.

Agreed, this is the first time I have ever heard Bill, or Ron, or any other developer explain it in this way.

Likewise... good to know thank you.

I guess I didn't say it very clearly. :( For those who think it doesn't matter... I'll give a perfect example of why it does:Say you're flying an aircraft in FS... encounter icing... it slowly builds up on your airframe. You land, it's not melted yet... and do a saved flight and set it as your default flight.Next time FS loads, that aircraft 'state' is how FS is initialized. Complete with ice buildup... even if you pick a different aircraft that doesn't have de-icing capability... say the ultralight. :wink:It can cause problems, and that's just one thing of many I know of that can go wrong because the default FS flight wasn't the first thing loaded by FS.

.. and if you're going to fly the Leonardo Maddog you will hear Nagging Nellie as the black line moves across the white rectangle as she's loading: you may open with the engines running - even though you selected Cold n Dark: you will hear engine noise in the cockpit - even though she's not running... and so on. This one absolutely needs the proper default flight preset and saved, followed by the Maddog substituted at the flight location - and then saved - and then you quit fsx and start the Maddog's load Manager: THEN you will guarantee a clean Cold n Dark problem-free start.