Sorry Al, but I sure don't. In fact I've never even tried to undock the 'message bar...'

What I don't understand is why makers of complex add-ons simply don't add a gauge that sets the FSX-internal controls to a certain state during aircraft initialization.

Well, I don't understand this either. In fact, I actually have the parameter initialization embedded in the model itself, so there no chance that anyone can screw things up by messing with the panel.cfg file or gauge system. :He He:

  <!-- KA 350 VISIBILITY SCRIPTS -->
  <PartInfo>
    <Name>KA_350_LOGIC_NODE</Name>
    <Visibility>
      <Parameter>
        <Code>
          (L:MilViz_init,bool) 0 ==
          if{
          (* add all checks and set parameters here *) 
          1 (>L:MilViz_init,bool)
          }
       </Code>
      </Parameter>
    </Visibility>
  </PartInfo>

 

 

so there no chance that anyone can screw things up by messing with the panel.cfg file or gauge system

 

Aw c'mon Bill, half the fun of flight simming is screwing up other people's work.

Well, I don't understand this either. In fact, I actually have the parameter initialization embedded in the model itself, so there no chance that anyone can screw things up by messing with the panel.cfg file or gauge system. :He He:

 

I think I've even learned this trick from you. :Whistle:

 

 

 

Aw c'mon Bill, half the fun of flight simming is screwing up other people's work.

 

You forgot the most important part: "...and then complain about it like it was the end of the world."

 

 

What I don't understand is why makers of complex add-ons simply don't add a gauge that sets the FSX-internal controls to a certain state during aircraft initialization.

This is one of the easiest tricks in the book and doesn't require a team of NASA-scientists. Just wait till initialization is complete and then set mixture or the avionics switch or whatdoIknow to whatever the add-on requires prior to startup.

 

I've never understood it either.  I brought that up somewhere once, quite awhile ago, when there was a discussion about a certain developers aircraft requiring a default aircraft in order to have the fuel and mixture set up properly.  It was taken as criticism, unfortunately.  I've always contended that I could make a simple external program that you could set up with a configurable range of values, run once and exit while the sim is active, and have essentially a range of 'default startup states' that would satisfy the most stringent requirements of any complex addon.

Fr. Bill, thanks for the clarification. It makes more sense to me now. Also I've enjoyed your many contributions to the forums over the years.

 

GW