Nevian

I know about the setting to change the rate at which weather changes, but weather also has its own dialog box where you chose weather themes, real weather etc. To have weather change on its own, which of these settings should be used?

I mean that you can't press them a second time to turn them off. They can only be turned off by choosing another mode. So say I want to control lateral movement manually - then I'd want to disengage LNAV - only you can't :(

Many thanks I believe I finally got it What I still don't get is why they chose to remove the feature. Along with things like LNAV / VNAV no longer being on / off buttons. Annoys me still...

I value your input greatly 777simmer, just so that's said Correct me if I'm wrong; Your described way of flying a VOR approach doesn't really utilize the VOR signal at all. The approach chosen from the database simply includes waypoints placed along the VOR-course to sort of "emulate" the true signal - and then LNAV just follows those. Does the 777 even have the ability to track the true signal? Or can it only be "faked" in the above described manner?

I was actually playing around with runway 04 at JFK (your previous post), and turns out I fell for the assumption that the VOR course would exactly match the runway heading so I put in 040 as the course in the FMC. Finding that the VOR course is actually 28° something seemed wrong... I have though seen cases where the chart and the database course deviate from each other by a few degrees. Not sure how much is "allowed" in such cases. As for my second question, I figure the other waypoints can only serve as vertical guidance as they have altitudes assigned to them. Am I way off?

No reason. Just checking that I'm not going through unnecessary steps. Ok, so I'm now able to intercept the course itself. But new basic wonderings arise; Many waypoints in VOR approaches are often offset somewhat from the actual VOR course. As you're obligated to follow that course (aren't you?), wouldn't that make these waypoints redundant? If the above isn't correct, and I'm actually to follow these waypoints - even though they deviate from the VOR course. Then I would need to remove the VOR from the legs page after intercepting it, otherwise the aircraft wants to go directly to the VOR (at the airport) and then back for the waypoints afterwards?

Thx. Is it at all possible to add anything to the RTE page without first having entered the departure and arrival ICAO codes? If so, how do I accomplish this?

So the LOC button is no longer used to intercept a VOR course. Apparently LNAV is used for this now, only I can't make it work. I see two scenarios; The FMC has a programed route, and as I approach the VOR course - assuming the NAV/RAD page has the correct tuning - LNAV is supposed to "catch" and track the VOR course? Hasn't happened to me as of yet... The FMC does not have a programed route. If I try to arm LNAV to intercept the VOR at this point the FMC responds with "No active route". How do I intercept the VOR in such a situation?

Of course you have - that's what you do. What I'm asking is simply how to achive in the 777 what was done in the 737. What exactly does "more integrated" imply? I guess these changes are intended as a step up, I just need to know how to see it as exactly that - and not a step down as is the initial impression when coming from the 737.

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...