SKeller

Do you respond with "Brakes released"? This should be the trigger for the Ground Crew to go on. Not only releasing the brakes, but actually telling the Crew that you have done so. Regards, Stefan

Hi Bryan, Thanks for clarifying. I was mainly trying to find out whether this behaviour is intentional. I'm not saying it's an issue. From the IVAO ATC perspective, though, setting xponder to 2000 makes your callsign disappear from the radar screen. Instead, "2000" will be shown in the a/c label on the map. On very busy aprons, this might lead to some confusion at the ATC's end. Thanks a lot and best regards, Stefan

Hi Bryan, When I arrive at the gate, the transponder code automatically resets to 2000 during the ground crew dialogue as follows: Ground Crew: "Cockpit from ground" Me: "Go ahead" <transponder code resets to 2000> Ground Crew: "The chocks are in now and you can release the parking brakes" Not a big deal, but slightly inconvenient when flying online on IVAO ;-) I'm using 2.3E Voice Control. In fact, I only found out recently, after having used Emergency NGX since the very day you released it. I just couldn't figure out why my squawk was always "2000" when looking at the IVAO tracker after I had completed a flight. That's why I took a closer look now ;-) Do you happen to know a workaround for this? I have set "Gate Arr" and "Gate Dep" to NO on the Config panel (because those jetway bells scare the pants off of me). Would this be the problem? Best regards, Stefan P.S. Hope you're doing great sales with your Dash-8 version.

Hi math341c, What exactly is your problem? Don't you a - find the time to dial in the ILS frequency and approach course, or do you b - have problems to figure out what the correct frequencies and courses are? If a: It's a matter of seconds with the mousewheel. And when using FS2Crew voice control, you can have your F/O set them for you by saying "Set course on my side 247" and "Set course on your side 247" (meaning the left and right course knobs). Same for the NAV radios: "Set 109.1 on NAV 1" and "Set 109.1 on NAV 2". Of course, you need to know the correct frequency and course before. If b: Approach charts are the way to go (same for threshold elevation and decision height) Edit: Kyle beat me :-)

Same here. I won't fly anything without FS2Crew any more :-) Haven't got the Dash yet, but will purchase it the day FS2Crew will be released. Looking forward to it!!! Bryan, you really should receive commission by aircraft developers for boosting their sales ;-)

I'm also running a 560Ti (Gainward) with 1 GB of memory, an i7-2600K @ 3.4 GHz, OpusFSX for views (comparable to Ezdok) as well as for weather (using FEX cloud & sky textures) plus lots of add-on sceneries, and have no issues whatsoever with the T7.

True, there aren't any cloud textures included with Opus. The freeware clouds you refer to might be HDE v2? They are actually pretty nice. Personally, I got myself FEX. If you already have a weather addon, buying Opus "just" for the cameras might not seem worthwhile. Then again, Ezdok has its price as well, and TrackIR ... say no more ;-)

I'd say that OpusFSX is the new must-have. It does everything that Ezdok does (including everything you mentioned above) PLUS it is an excellent (I dare say the best available) weather engine. So it's something like a "buy one, get one free".

I don't know where all these problems come from... I run Windows 7 Pro, German version. And everything works fine! 1. Run Vistalizator and to set your OS language to English 2. Set Speech Recognition to English - US 3. Do the speech training 4. Run Vistalizator again and set your OS language back to your preferred language After that, FS2Crew voice works as it should no matter what the OS language is. Maybe those having problems did not read the following very important sentence in the manual: "Make Sure 'Run Speech Recognition at start-up' is UNCHECKED!" (on page 7) The Windows speech recognition will not work, but FS2Crew will.

Hi Bryan, Once again, you created a brilliant piece of art! Thank you so much for lifting us up to this truly unique level of immersion!!! :Applause: Wow!

Yup, but to initiate the push, you need to press a key. That's what I meant ;-)

No, I don't think so. You need to use the keys to control the GSX push. I don't actually "control" the pushback crew via voice, I just talk to the FS2Crew ground crew for the fun of it (and for the Airbus with the added benefit that I don't need to click with the mouse in order to advance FS2Crew to the next phase because I speak the trigger phrase).

I use this method because it gives you the best of both worlds :-) AES/GSX does perfect pushbacks without the hassle of entering distances and angles, and on the other hand it's SO MUCH FUN talking to the ground crew of your wonderful FS2Crew.

Hi Bryan, Thanks a lot for these tips. I added all the "Flaps" commands to the speech dictionary as described above. Works perfect now! Whoohoo! :biggrin:

And btw, in the FS2C Config panel, I set AES to OFF and "PB required" to NO.

Simply assign the same key for (VATSIM) push-to-talk and for Soft Mute (FS2Crew). That's how I do it on IVAO. Whenever you hold the PTT key to talk to ATC, FS2Crew doesn't "listen" then. BTW, I'm using AES/GSX as well and I don't need to manually advance FS2Crew to the next mode. - I select "prepare for departure" in AES - wait for the AES crew to tell me to release the brakes - Call the FS2Crew crew "We're ready for pushback" - release the brake, say "Brake released" - wait till the pushback is complete - set brakes, say "Brake set" - say "You are cleared to disconnect and go to hand signals" So you can use AES for pushback without any need of clicking buttons. Works like a charm. Hope this helps, Stefan

Same here. I would love to use the ol' "Flaps Up" command again. I just don't get the F/O to fully retract the flaps. "Flaps Zero" somehow doesn't get recognized correctly.

Wheel chocks set? Tow truck connected?

In the FMC, go to PMDG SETUP>AIRCRAFT>DISPLAYS. Make sure that FUEL TOTAL DISPLAY on page 9/9 is set to NO.

Hi Christian, Have you tried starting FS2Crew only AFTER you saved/loaded your situation? I don't use VoxATC, but I remember having had the SDK error myself when loading a situation with FS2Crew already running.

They are all in <...>\Microsoft Flight Simulator X\PMDG\PMDG 737 NGX\PanelState For the panel states created by PMDG you'll find two files per panel state: NGX*.fmc and NGX*.sav. If you delete them, they shouldn't show up in the FMC any longer. Your custom states might include a third file *.rte.

Any PDF reader installed? The manuals are in PDF format. So either you don't have any PDF reader or the file associations in Windows are messed up. What happens if you double-click a PDF file?

No, it's actually the propeller that's moving. I've had the graphics error you're describing only once, and this was gone after restarting FSX. However, my initial issue is reproducable each end every time I start the left engine.

Thanks. So Opus is not the problem then ...

Do you happen to use OpusFSX as your camera control, like I do?