Nevian

Being a creature of habit I naturally enter the 777 cockpit with an NGX mindset. Regarding the MCP, I'm used to being able to deactivate different aspects of the autopilot as needed. For instance, wanting to control the roll manually how do I deactivate the HDG SEL mode? Same thing with pitch, how do I take manual control of this aspect without disconnect the A/P all together? In the NGX you could deactivate, say heading select, by pressing the HDG SEL-button. Doesn't seem to work here. Also, if you forced the yoke in one direction you would get manual control of pitch or roll. In the 777 it seems the A/P simply disconnects all together. Or did I miss something completely?

Thanks And this is the way it was intended...?

So flying around with the 777, and so far the things I've had trouble with are all with the MCP. Aren't the buttons supposed to be on/off? I'm not at all able to disconnect things as A/P, LNAV, VNAV, HOLD buttons etc. For instance, pressing Z to disconnect the A/P does nothing. The button is physically pressed, but nothing happens. The only way is to right click the hot spot beside the A/T button. Obviously that's not how it's supposed to be. Any ideas?

I noticed during a VOR/DME approach that once I dipped below a thousand feet or so ALT ACQ (Altitude Acquire) appeared on my PFD. What exactly does it mean, and what does it do?

Just a quick question - with most types of games I'm used to them getting the best FPS in full screen mode. However, with FSX it's the opposite. Much better in windowed mode. Even with a brand new high end system my full screen FPS goes down to around ten, whilst hovering around 25-30 in windowed mode. Is this how it is for most people? Or is it something I should look into?

The dashed segment has a couple of waypoints on it with the prefix MATF - which I have now found to mean Missed Approach Turning Fix, proving that it actually is a missed approach segment. I suppose that means that the remaining part is to be flown visually. Still I don't get why the missed approach point is so far away...

I'm attempting the RNAV approach to 08 at LOWI, Innsbruck beginning at ELMEM as the IAF. When looking at the chart I'm confused about a few things. First of all, the missed approach point is 12,7 nm from the runway. Also, after this point the route is dashed without any clear indication on why, except that the slope changes slightly. When feeding this into the FMC it also presents descent issues. Can someone explain? Thx :smile:

I'm currently playing around with the REX Essential Plus package. I like it, but have one question. The weather options in it seem to have all kinds of settings - except the ability to set a specific type of weather! Let's say I want a thunder storm. There is no such setting in REX - is this because I should do this in FSX itself? If so, will the textures, clouds etc. still be courtesy of REX?

I'm having great fun with the NGX package, but I can't seem to understand some of the aspects of the different approaches. Reading the FCOM didn't give me any eureka moments either, and so I'm here. A few questions: In a VOR approach, if your route is already programed into the FMC, what good does it do to dial in the VOR-frequency when the FMC is going to line you up with the runway anyway? And if I do use the LOC/VOR button, does the VOR course preside the FMC's programed waypoints? I've found that LAND 3 only appears in ILS approaches. What about LAND 2? I don't think I've ever seen it. And if we have Land 2 and 3, what ever happened to 1? How exactly does an NDB approach work? I know how to work the ADF itself, but how does the APP-button come into play? I'm getting the SINGLE CH message - sometimes in amber, sometimes in green. What's the difference here? Thanks

I wonder about one thing. Supposedly V1 is the speed at which you are dedicated to taking off. In order to know where this point accurs, one needs to know the length of the runway. I guess this lies within the FMC database as it's not fed to the system in any other way. For fun I just attempted to reject a number of takeoffs above V1 speed with wet runways and in all occasions I stop with quite some runway to spare. Don't know how well this part is modeled by PMDG. Or maybe this is the way it should be?

I too am able to type in KW99 into the REF NAV DATA page, but all it does is display the airports coordinates and runway info. This proves that the airport is indeed in the data base already - so why can it not be entered as a destination in the RTE page?

Hi all! My first post I was fooling around with the 737 NGX, and came across a problem when trying to program the FMC as I planned to land at an airport that didn't have an ICAO code. In FS Commander it is designated as W99, but I'm not able to put this in as my dest. in the FMC. The FMC manual states that you should the able to input a temporary dest. for just such cases by inputing it's location etc. in the REF NAV DATA page. However, I have not been able to. Is it at all possible?