SKeller

Is this particular view maybe zoomed out too far? I noticed that if I zoom out too far, I can't operate the panel with the mouse anymore.

+1 Bryan's customer service is really excellent. You have a problem? He will come up with a solution in no time.

I thought there was one for Win 7 and one for Vista and that's it. Unfortunately, I can't really remember where I downloaded it and what exact version it was. Have you looked at this one? http://www.chip.de/d...r_31709612.html Which of the various language packs you use, however, depends on your operating system. If you say you have Win 7 64bit including all updates, you should have SP1 as well. Right-click on "Computer", select "Eigenschaften" and see if you have SP1 or not.

I'm running the German version of Win 7, too. No problem. I simply installed Vistalizator, switched to English, "trained" the speech recognition, and then switched back to German Windows. FS2Crew Voice works like a treat.

I don't quite understand this discussion ;-) The NGX, as provided by PMDG, allows us to simulate tons of failures whenever we feel like, or randomly, or service-based. And now, for the first time ever, we have an F/O how supports us dealing with these by following the flows as laid out in the QRH. How great is this? Anyone who enjoys handling failures will sure love this add-on.

But how do I load the NGX without loading a panel state at the same time? I don't quite get how I could create a panel state "from scratch".

Hi Richard, Thanks for your input. The Panel State I normally use for startup is a custom save based on PMDG's 'NGX Long'. (I just switched to hPa and Radio Altimeters and then immediately saved again under a different name.) So, in total, I tried four different panel states: My custom one (fails), 'Long' and 'Short' as provided by PMDG (both fail) plus 'Cold & Dark' which is the only one that did not result in a Master Caution after engine start. Bryan: Would it help if I sent you the panel state files? I haven't found the time yet to test your fix. Will do tonight (I'm UTC+1). Thanks and best regards, Stefan

I'm using it and enjoying it big time :-) Awesome piece of software!

Hi Bryan, In the meantime I did a reinstall of FS2Crew (just in case), but I still get the same results. I was thinking again about the order in which the F/O reads these failures, and something seems to be a bit odd. This is the order in which the failures are reported when the right side fails: And here's the order for the left side: Does this maybe shed some light on the problem? Best, Stefan

Hi guys, I just ran a couple of tests again. Just to be sure that my custom Lufthansa livery downloaded from the AVSIM file library is not the problem, I used the PMDG House liveries for all these tests. And I disabled OpusFSX too. So, the only add-ons involved besides the NGX and FS2Crew Emergency were AES, Aerosoft's Mega Airport Frankfurt and Ground Environment X Europe. Here are the results: 737-600 Panel State 'NGX Short' -> same error 737-700 Panel State 'NGX Short' -> same error 737-800 Panel State 'NGX Short' -> same error (I didn't bother trying with the 900, I hope you don't mind) After that, I tried again with the 736, Panel State 'NGX Short', but this time I did the engine start flow myself (#2 then #1). After cutout of engine starter #1, I turned on both engine generators. Then I turned the Probe Heat switches ON (first left then right), and this time the "Master Caution Anti-Ice" was triggered when I turned on the left probe heat. Tried a fresh start again, did the engine start flow myself again, but this time turned on the right probe heat first. "Master Caution Anti-Ice" was triggered when I turned on the right probe heat. After saying "Checked" and "Identify", the F/O repoprted the following: "It looks like the Captain's Pitot Heat has failed." "It looks like the left Elevator Pitot Heat has failed." "It looks like the left Alpha Vane Heat has failed." "We got an auxiliary Probe Heat failure." So, this time the other side failed. (And besides: The warning light for the AUX Probe Heat is actually on the right but is announced when the left side fails, the TEMP Probe Heat is on the left but is announced when the right side fails.) I am wondering if FS2Crew might just query for the Probe Heat failures a bit too early... The thing is that if you flip one Probe Heat switch, the four amber lights for the other Probe Heat switch are still on, and so is the Master Caution light and the F/O's Anti-Ice annunciator on the main panel. This somehow looks to me as if FS2Crew was expecting a "No Lights" state after the first Probe Heat switch is turned ON and was not allowing enough time for the second switch to come ON as well. Then again, why am I the only one experiencing this and why does it work when running the full Preflight from Cold & Dark??? I said I'm lost, didn't I? ;-) Best regards, Stefan

Hi Glen, Thanks a lot for your continuing support. I do turn on the Window Heat switches myself, but for some reason I didn't include this step in my list above, sorry. The sequence should read: - Yaw Damper ON - Emergency Exit Lights Guard closed - Passenger Signs ON - Window Heat switches ON - Recirc Fans Auto - Pressurization Panel set I'm about to start FSX and try with the NGX Short panel state. I'll report back the results. Thanks again and best regards, Stefan

Have never tried the Short panel. Will do tonight.

The sound actually plays the very moment the lights go out. And it shouldn't play four times either, should it? A mystery, that is ;-)

Hi Glen, Thanks a lot for your time and your input. Much appreciated. Yes, I'm using ground electrical power. My startup panel state is "NGX Long", and I open FS2Crew as soon as the NGX has fully initialized. Then I check the CFG and BRF pages. Here's what the panels look like: You are right, I normally do not say "Are you ready for the departure brief". My understanding of the software was that it doesn't matter, as long as the BR page is set, and saying "Any questions" at some point during Preflight would do. I just tried the procedure above again, this time saying "Are you ready for the departure brief" prior to "Any questions", but the result was the same. Regarding pushback, I don't use FS2Crew's pushback. I use AES pushback at my add-on airports or the NGX pushback when at default airports without AES support. In both cases, after the APU is on the bus, I call the ground crew saying "Please disconnect external power". After that I use the "Prepare position for departure now" command by AES. I actually had the suspicion myself that pushback might be the culprit, but when I just tested again, I started my FSX session at the holding point of the runway, so no pushback involved at all, yet I get the same error. And when I use the pushback procedure described above from a "Cold & Dark" panel state, everything works fine... Anyway, I can live with this. It's a matter of 5 seconds that my F/O is speaking rubbish. Not a problem at all. Of course, it would be excellent to find out what exactly the problem is, but I guess you guys all have more important things to do ;-) Thanks a lot and best regards, Stefan

Great stuff! Thanks!!! :smile:

When starting from Cold & Dark and doing the Preflight, everything is fine. When starting from the "NGX Long" panel state and doing as described above, I get the quadruple Master Caution alert. Yet, I don't see I'm doing anything wrong...

I skip FS2Crew's Preflight procedure and perform the following myself: - Enter Fuel and Payload in CDU - IRS switches to NAV - CDU preflight - Set Trim for takeoff - Yaw Damper ON - Emergency Exit Lights Guard closed - Passenger Signs ON - Recirc Fans Auto - Pressurization Panel set - Flight Directors both ON - Auto Brake RTO - Left FWD Fuel Pump ON - APU Start - Auto Throttle Arm - IAS Set V2 - HDG set runway heading - Altitude set initial climb - APU generators both ON - Ground Connections remove - Parking Brake Set - Elec Hyd Pumps both ON - Isolation Valve Open - Bleeds On - Fuel pumps ON - Anti Collision Lights ON - I say "Any questions", F/O replies "No questions" - I say "Before Start Procedure" - I say "Before Start Checklist", and we're running the checklist fine - I say "Cabin Crew arm slides" - I say "Start sequence is 2 then 1", F/O replies "Check" - I start pushback - I say "Start engine two" - F/O "Starter cutout" - I say "Start engine one" - F/O "Starter cutout" - F/O turns on generators, turns off the APU, turns on left Probe Heat, then right Probe Heat, and here comes the alert.

Nope. Both switches are in the Off position when I load the aircraft, and the first (and only) one to touch them is the F/O after starting Engine #1 (sequence 2 then 1).

Hi Bryan, Thanks for your response. One more thing that I probably should have mentioned in the first place: All of the above applies to the 737-600. I haven't used Emergency NGX with the 7/8/900 yet. Maybe that helps? Best regards, Stefan

Okay, I did three more tests with pen an paper ready, and here's what happened every time: As soon as the F/O turns on the right Pitot Heat switch after engine start, off he goes: F/O: "Uh, Master Caution Anti-Ice. Uh, Master Caution Anti-Ice. Uh, Master Caution Anti-Ice. Uh, Master Caution Anti-Ice." However: No Master Caution lights, no annunciators, no amber lights whatsoever anywhere in the cockpit. The Probe Heat warning lights extinguish at the same time the F/O flips the switch... I say: "Checked", then "Identify". F/O: "Uh, we got a Temp Probe Heat failure." F/O: "Uh, it looks like the F/O Pitot Heat has failed." F/O: "Uh, it looks like the right Elevator Pitot Heat has failed." F/O: "Captain, it looks like the right Alpha Vane Heat has failed." I'm really lost here. I perform the Captain's flows to the letter, and I'm sure the F/O does the same with his flows :wink:. Something seems to make him think though that the right Probe Heat has failed. Of course, I can simply ignore it, no big deal. But I guess that's not the way it should be, is it? Best regards, Stefan

I'd say the answer is OpusFSX, as Stéphane suggested. You get everything that EZdok has, PLUS a great weather engine. Or in fact, it's primarily a weather add-on with a great camera tool included for free :wink:. Either way, I'm enjoying Opus big time and wouldn't want to miss it. Had REX plus EZdok before, now I dumped them both for Opus.

Window heat is switched on during preflight, yes - either by myself (if I skip FS2Crew's Preflight) or by the F/O. Either way, it is on at the time the F/O alerts me. And there are no amber lights anywhere on any panel... I wil doublecheck on my next flight.

Doesn't the F/O switch on the probe heat after engine start? Anyway, I'm sure probe heat was on, the Before Taxi Checklist was fine. There were no failures, no lights, nothing unusual really. Strange... It seems to have started after having updated to 2.1E

Hi Bryan, I must admit I didn't check the F/O's side. But shouldn't both Master Caution "buttons" light up in any case? I thought that only the annunciators were different on the Captain's and F/O's side, but the Master Caution lights were in sync...

Hi guys, I'm enjoying Emergency NGX big time. What a great add-on! However, with FAIL enabled on the FS2Crew main panel, I always get a strange alert after pushback and engine start. My Aussie F/O says "Uh, Master Caution Anti-Ice" four times in a row. The thing is that the Master Caution light does not even light up, and I have selected NOT REQ for anti-ice on the Briefing page. Not a big deal, I just ignore the warning, but anyway, it would be great to know whether I'm doing something wrong. Does anyone else get this alert or knows how to avoid it? Thanks a lot in advance.