Cras

I want to set up Radar Contact so that my First Officer speaks, but there is no voice for the captain (aka Me)I have been flying Radar Contact for over a year now with pilot wavs disabled, as I like to say my part rather than press a button and listen to a pre-canned recording.However, I would like to continue this practice, but when I hand over the comms to my FO, I hear him speak his part instead of silence. I figure that if I can create a new pilot set that essentially has all the wavs just blank, 5 seconds of silence, then I can have the pilot wavs active and then accomplish my objective.So I ask, is this possible? And how would I go about it, because I see these folders are not named, but numbered, and their structure is complex to say the least.

+1 for the push button for numbers version of the Xpndr to make its way into the NGX in a future SP.

That is messed up. Seriously messed up. I have never seen this with Shade myself, but this is a serious issue. Repair may be out of the question, but I can leave that to better informed people to decide that. I would guess that the only viable solution would be total fresh re-install of the NGX, but I would first recommend you get in contact with PMDG directly with a support ticket.

Oh man this mix is soooo good. Nice work.

The one thing that really got my attention from the Xplane 10 preview videos released way back when was the Space Shuttle. If X-plane can seriously and accurately simulate super sonic flight and upper atmospheric flight, than I will certainly give it a look.

I myself and still looking forward to PMDG's effort on a Boeing house livery myself.

The Space Shuttle was able to fly soley on autopilot. And the Russian Buran (their Shuttle knockoff), flew its sole flight unmanned. Auto launch, auto orbit, auto de-orbit, auto land.If the Space Shuttle can do it, a 737 can do it.

very sad when I read this. Signed the petition, and I do hope this gets stopped.

I personally set the A/P disconnect button in the PMDG settings on the CDU. Then I map that key to my fire button on the X52 Pro via FSUIPC. That way when I hit it the second time, it kills the aural warning.Prior to that, I had my fire button mapped to Z, the FSX a/p button, but which is actually a toggle, so my pressing it a second time, it would re-activate CMD A, which is not what I wanted.I also have A/T disconnect button mapped to my joystick as well. During the final approach, I really don't like taking my view away from the HUD.

Do you actually fly RNAV GPS approaches in an NG or do you fly RNAV RNPs. I admit I tend to only fly an RNAV approach is I have the chart and it is RNP. I just never saw any indicators that dictate that I can fly GPS approaches in an NG, I thought those are WAAS.

On the Innsbruck case, my guess would be this information would be in the navdata in real life, so the real life FMS would know there is a G/S there and display the toggle appropriately.But in FSX, we do the best we can.

I see what you are seeing, no G/S on/off for non-precision approaches, but I assumed that it was done on purpose. No point in a toggle for a glideslope on an approach where g/s is n/a.

This thread has turned to sh!#.Thanks Cory for that. The internet doesn't have enough sh#!, we need as much of it as we can.

I have had Service base failiures on since day one and have yet to see one. I went for broke and set up the random failures for three in two hours just to get some use out of the QRH.

HIGHMEMFIX tweak in the fsx.cfg will fix this.And ditch ENB mod if you are using it.

+1 on the Avsim AFCAD library. Great stuff being done by people. AFCAD addresses the navaids and runway usage as well. -1 to Ronny <last name>, what the hell are you doing with your signiture?

You can go into the failiures section of the pmdg options in the CDU and see if any failiures are active.

If it is indeed the FSX internal frame limiter, then that would explain it. I myself, having never had a CTD or sim freeze caused by the EFB, use the java fps limiter and have the FSX internal one set to unlimited. May be on to something here.

Ok then. I just can't imagine why a pilot would arm the autopilot on purpose whilst on the ground. And I can't imagine why any plane would allow the CMD to arm in the first place with the wheels still on the ground. There is no reason for that.And thanks for the information by the way.

Why would you ever want to arm CMD when on the ground? Or was the deal with the B777 an inadvertant arming of the CMD?I don't even flip the A/T switch to on until I am line up on the runway.

alright then. Thanks to Fred.

third, saw the same thing the other day.

Are the PMDG guys still planning on doing the Boeing House Colours?

Flying with CWS is actually a lot of fun, I use it all the time. I use it sometimes when given clearence to intercept the localizer, as I can drop the roll mode into RWS, arm VOR/LOC, turn the plane on the intercept heading myself, and when the autoflight system is ready to take over, it will automatically take the plane out of CWS and back into full CMD roll mode. Same goes for intercepting altitude set on the MPC. It will not intercept a heading, but if you lower the bank to something like under 5 degrees, CWS will automatically level the wings. It is great to use for departures and arrivals I think, since you are flying the bird all by yourself, but want to still do a bit of hand flying, CWS lets you do that but still have the ability to do the other things you need to do, like man the radios, set up the FMS, things like that.Give CWS a try.

EFB is expensive, but you do get a month to try it out to see if it is worth it to you. The minimums not being exact as the real world charts is something one has to keep in mind, but it beats flying with no chart at all.I run it on my laptop so it is always up for me. But if running it on the same machine as FSX, as long as you got HIGHMEMFIX=1 in your fsx.cfg and are not using ENB series or the D3D9 hook frame limiter, alt+tab should work fine for you with not problem. It is only when using D3D9 hooks that alt+tab can cause black screen of death in FSX.