Lek767

1. Did you press the EXEC button after entering the PERF INIT data, as the knowledge base article suggests? 2. Are *both* F/D switches turned on?

Check the PMDG Knowledge Base: http://support.precisionmanuals.com/KB/a99/v-speeds-dont-show-on-pfd-speed-tape-vnav-wont-arm-engage.aspx

The PMDG support site appeared to be down as well just a moment ago, but seems to be back up again. My guess is it's just a temporary back-end systems glitch. You could send them a support ticket via http://support.precisionmanuals.com/.

Why are you resurrecting a two-year-old thread?

Yes. http://forum.avsim.net/topic/401172-hole-in-the-vc/?hl=hole

What seems to be the problem?

Not in an MD-11, that's for sure...

Great idea, but before proceeding any further, you might want to skim through a couple of nearly identical posts made in the past few months. Here's a somewhat random, not even remotely comprehensive sample to get you started: http://forum.avsim.net/topic/401022-767-400/?hl=767 http://forum.avsim.net/topic/400606-757767-pmdg-next-project/?hl=767 http://forum.avsim.net/topic/398951-pmdg-b764/?hl=767 http://forum.avsim.net/topic/396487-dear-pmdguser-poll/?hl=767 http://forum.avsim.net/topic/391200-boeing-767/?hl=767

Unless someone else has a better idea, you should probably take FSUIPC out of the equation first to see if that improves things. Either reset all FSUIPC settings to defaults by temporarily removing your fsuipc.ini file (create a backup copy first, of course), or disable the DLL altogether by editing your dll.xml file (change the <disabled> parameter in the FSUIPC 4 addon section to True). Then attempt your test flight again and see if the NGX behaves differently (i.e. the gear raises properly and you're not encountering any overspeed shenanigans any more).

Screenshots, please, or it didn't happen. ^_^

You do realize that you're answering a question that's almost a year old, one that has been answered three times in this thread already, and that you got it wrong, right?

I'd imagine that GPU overheating could cause that. Is your video card fan still spinning and is the heatsink not clogged with crud?

Sorry, but arming the autothrottle is not a prerequisite for arming or engaging VNAV. From FCOMv2, page 11.41.2: My (semi-wild) guess would be that the OP forgot to EXEC the performance data, or didn't enable both flight directors.

Real-world considerations aside, I think it's safe to say that we're dealing with a bug in the NGX code in this particular instance. Whenever conditional waypoints (such as FVO2-4 shown on your ND) and tight turns are part of a procedure, unpredictable routing may ensue. I've seen simple 90 degree turns transform into monstrous 360 degree spirals, witnessed the magenta line "flapping" nervously between two possible routes (both wrong), and -- as happened in your example -- seen turns flipping direction. Let us intersect our fingers and hope for a fix in SP2.

It's controlled by the "Keep FS clock sync'd" option on the FSUIPC Miscellaneous settings tab. However, going by your description, you might just be dealing with the "normal" FSX behaviour of swapping daytime textures for their dusk and night time variants. This will indeed result in brief "loading textures" interruptions, which as far as I know can only be avoided by not flying at dusk or dawn. Perhaps someone else can chip in on this one, as I haven't really been bothered by it.

Hmph... No, not much point in doing that, is there? I guess we'll have to try a different route. Are you using FSUIPC to synchronise your FSX clock, by any chance?

The problem with landing at Gatwick in FSX is that, by an utterly diabolical twist of fate, the scenery of nearby Heathrow is loaded into memory and rendered on-screen at the very moment when one's executing the flare manoeuvre over runway 26L. If you've got a reasonably complex piece of add-on scenery installed for EGLL (such as Aerosoft Mega Airport London-Heathrow), this can lead to a very noticeable hitch lasting up to a couple of seconds -- without fail ruining your landing if not your whole day. You can see glitch in action yourself by positioning your aircraft on runway 08R/26L, switching to outside top-down view at 8x zoom, and entering slew mode. When moving along the runway centerline, you'll see the EGLL scenery pop into existence right after you cross the threshold. Now you don't see me: Now you do: The only workaround I've found is simply to disable the Heathrow add-on scenery when flying into Gatwick. It's less than ideal, but will prevent any scenery-related hitching from occurring at a critical time. Also, who in his right mind wants to fly into Heathrow anyway?

A cabin depressurisation at cruise altitude is guaranteed to grab your attention as well, if only for that infernal cabin altitude horn (which thankfully can be silenced).

Your post contains two question marks, but no actual question. What would you like to know?

I tried it and am seeing the same thing as you: N1 can't be enabled manually between the moment the A/T mode changes to ARM, and point where the thrust mode switches to N1 automatically (when crossing the thrust reduction altitude). I'm not sure if this is a bug or a feature...

A 2.4 GHz Core i3 with Intel HD graphics? Ouch. Unless you're a big fan of 1 fps slide shows, I wouldn't recommend it.

Not... exactly. One can set up an engine cut at V1/Vr/V2, but not an engine fire. The latter requires the use of a timer, and cannot be triggered at a specific Vspeed.

Could you take a look at the "A/T Manual Override" configuration setting within your 737-600's aircraft equipment setup (PMDG SETUP -> AIRCRAFT -> EQUIPMENT), and tell us which option you've got selected?

I've always wondered what the proper procedure is for re-engaging the A/P and A/T after a manual go-around. The FCTM (pages 5.83 and onward) merely states "engage autopilot as needed", and doesn't mention re-enabling the autothrottle at all. Do the two get switched on at the same time? Or separately? At what point during the go-around maneouvre should that happen? Thanks.

Thanks for your clarification. I've managed to reproduce the issue by starting the engines (using the standard start-up procedure) while the reverse thrust levers are not in the stowed position. This is the result: Make sure your throttle is properly calibrated, the throttle is at idle and that the thrust reverse levers are fully stowed before starting the engines. Hope this helps.