SKeller

You bet I do! Just posted a line in the German IVAO forum

Thank you so much, Bryan! You're a star! :smile:

No frequency dialing necessary. You only need to enable the correct button in the NGX's audio panel. See the Main Ops manual, page 38: Note: To communicate with the Ground Crew, press the FLT button on the Captain’s audio panel [...] The screenshot on page 39 shows the button(s) to press. Hope this helps, Stefan

I can only speak for the IVAO client, but it works perfectly fine. You only need to make sure that the "Enable IvAp <-> FSUIPC SDK" option is enabled in the IvAp Configuration tool. (This option is located under "3rd Party Tools" in the Configurator)

Great stuff, Bryan! Thanks a lot!

It will work, don't worry. The installer simply does not recognize SP1D and throws this message, but if your WX Radar is working, you have the latest build, and FS2Crew will run fine.

Thank you so much for your kind response. I'm not high, there's no need to shout at me, I didn't "comment", but asked a question, and I'm terribly sorry for having gotten you wrong regarding the panel sounds. However, from reading your "Panel buttons sound the same (place the panel near any PMDG button and click them one after another).", I wasn't able to figure out what you were aiming at. There you go, seems I AM high, or stupid. Please accept my sincere apologies. And you are right, of course: I didn't pay $$ for it. I paid €€ for it. So who am I...

What is wrong with the F/O's voice on the right speaker, considering he is sitting to the right of you? And are you really expecting the click sounds of the FS2Crew panel to move in space depending on where you place the panel? Wow! :smile:

Simply ignore the error message. FS2Crew will work fine.

That would be SOP1, I think. From reading throught the flows in the manuals, I notcied that SOP1 required the fewest changes compared to my legacy flows.

I also like SOP1 the best. What a great joy flying with Reboot!

Ah, NOW I'm with you I've been flying the NGX since it's release, and I never observed this problem. Could this be a problem specific to FSX Steam? I'm on FSX Boxed. Maybe the Steam pilots have an idea. But what you're saying is that pressing B will return different results depending on whether you're in the PMDGs or a default aircraft? This is very strange indeed... Last try: Do you happen to have two weather engines active and running at the same time? E.g., you use ASN and forgot to uncheck the IVAO weather in IvAp Configurator?

Maybe I have completely misunderstood your problem? Are you saying that the altimeter reading at the bottom right corner of the PFD does not match the reported QNH, but you think it should always match without any input by you? Is this what you're asking for? If so: It doesn't. And by the way, since you played the experience card: I've been an IVAO member for 14.5 years now.

Please trust me: There is no difference whatsoever between online and offline in this respect. And YES, you need to calibrate your altimeter manually. Always. That's also true for real life by the way. Your wheather in FSX will change automatically, yes. But your altimeter setting will NOT. And as said above, it's normally only three times you need to calibrate your altimeter during each flight: 1. On ground at your Departure airport prior to takeoff 2. When passing TA in climb 3. When passing TL in descent And each time, you need to do so manually.

It seems there's some kind of misunderstanding how altimeter calibration works ;-) Pressing B will set the altimeter to the local QNH at your current position. It will not re-calibrate automatically when the QNH changes later. Remember that you probably pass through different weather conditions with different pressure in cruise. Basically what you do is the following: 1. Set local QNH at your Departure Airport. 2. After takeoff, when passing Transition Altitude, set standard pressure (1013/29.92) and leave it there during climb, cruise and most of your descent, regardless of what the actual ambient pressure is. The idea is that all aircraft above TA use the same reference point for their altimeters. 3. When passing Transition Level during approach, set local QNH again (hit 'B'). That's it

I can help only with 1): The altimeter will *NOT* automatically calibrate! The barometric pressure is not read by the aircraft at startup. The altimeter setting of the NGX/777 will always be the value that was saved with the panel state you use as your startup state. So, once the aircraft and live weather has finished loading, you need to manually calibrate the altimeter to local QNH (simply pressing B on the keyboard will be the quickest way).

If you have the boxed version of the NGX, then the key on the DVD sticker is the one you need to enter at the Aerosoft site. If this does not work, you should contact Aerosoft rather than PMDG. Good luck!

Because when flying online on IVAO, you are normally assigned an individual squawk code. This makes sure that your callsign is displayed in the aircraft label on the radar screens (even when the transponder is in Standby), which is really handy (from the ATC point of view, that is). Setting transponder codes of 1200, 2000 and 7000, however, will make your callsign disappear from the label. Instead, the transponder code will be displayed. I know that by the time FS2Crew sets the transponder, you are parked at the gate. But being a TWR/GND controller on IVAO myself, I can really say that it would help a lot on busy aprons, if arriving aircraft kept their callsign in the label until they disconnect from IVAO. Not a big deal, of course. I was just thinking you might consider it now that you're recoding tons of stuff anyway... :Big Grin: Oh, and thanks for the news on ground crew handling. Sounds excellent. Best regards, Stefan

Hi Bryan, While you're being at it ... Would it be possible to prevent FS2Crew Reboot from resetting both the transponder code and the CFG settings for PWR/AIR SRC once you arrive at the gate? In the current version, as soon as you shut down both engines and answer the call by the ground crew, the transponder resets to 2000 and the PWR/AIR SRC resets to APU, regardless what was selected before. So, in order to have the ground crew connect the GPU, you need to open the CFG panel and select EXT/AC first, before you can issue the "Please connect the GPU now" command. It would be really great if these two settings were kept as they are during the entire "stay on board" I'm looking forward to Reboot!!! Thanks and best regards, Stefan

Will the panel states we created with the previous SP1d work in the latest version or do we have to re create them? Thanks

see here: http://forum.avsim.net/topic/464558-13mar15-aerosoft-dvd-and-download-customers-and-fsx-se-compatibility/#entry3199102

Hi Richard, Yes, it is. Edit: Plus, I *think* that "Aircraft casts shadow on itself" (or whatever the option is called in English - I have a German version of FSX) must be enabled in the FSX settings as well.

Regular FSX + NGX SP1d + FS2Crew Emergency NGX 2.3 Voice Edition works fine! Did a full flight from Before Start Procedure to Shutdown Checklist, and no problem whatsoever. (Did the Preflight myself, though, because I always do so). What I did before was a full uninstall in this order: 1. FS2Crew 2. NGX 600/700 SP1c 3. NGX 800/900 SP1c 4. Deleting all NGX folders as per the instructions in the PMDG forum Then reinstalled: 1. NGX 800/900 SP1d 2. NGX 600/700 SP1d 3. FS2Crew NGX 4. FS2Crew Emergency NGX When opening FS2Crew Configurator, I received the warning about SP1c not being present, but I just ignored it and enabled Emergency Voice Edition. And everything is fine

Did you delete the entire [sIM]\PMDG folder after uninstalling? Because I removed only the PMDG 737 NGX subfolder and left my NAVDATA folder untouched. After installing SP1d, my current AIRAC was still there.

THANK YOU PMDG :im Not Worthy: