

Here's the flight on the MP tracker too- very nice, went from KSFO 28L to Santa Maria.

@Armchair Ace: where did you get this EICAS display?

nickyivyca wrote:And also implement the autostart to start up the engines, though I'm not sure about that. I'll take a look soon.
startup = func
{
# activate glass cockpit instruments
setprop("systems/electrical/outputs/efis", 16);
# turn on starter
setprop("controls/engines/engine[0]/starter", "true");
setprop("controls/engines/engine[1]/starter", "true");
# turn on fuel pump
setprop("controls/engines/engine[0]/fuel-pump", "true");
setprop("controls/engines/engine[1]/fuel-pump", "true");
# toggle engine cutoff after 1 second
settimer(func {
setprop("controls/engines/engine[0]/cutoff", "false");
setprop("controls/engines/engine[1]/cutoff", "false");
}, 1);
}
Armchair Ace wrote:The EICAS display came from the 772ER. As far as I could tell, it doesn't work too well on aircraft other than the 772ER.
Armchair Ace wrote:Say, do you mind if I add the A320 Engine Fire system to the Fokker 100? I tried implementing engine fires on it, but I can't find a property in the Internal Property Browser.
skyop wrote:Guys, slight problem: the new 777 instruments are visible through the model!
Any fixes?
<animation>
<type>select</type>
<object-name>EICAS</object-name>
<object-name>Intstrument1</object-name>
<condition>
<equals>
<property>sim/current-view/view-number</property>
<value>0</value>
</equals>
</condition>
</animation>
Nasal error: could not read script file: G:/Flightgear191/data/Aircraft/A320/Nasal/dialogs.nas into module dialogs
nickyivyca wrote:Also, the YASim autostart isn't working for me. When I press autostart, nothing happens. I think it has sometime to do with the console error that I'm getting whenever I start up.
nickyivyca wrote:There is no "dialogs.nas" file...
Users browsing this forum: aglunt, YandexBot [Bot] and 2 guests