Chaos81

Am I the only one that felt like I was going to fall out of the sky looking at this shot? :( For some reason that shot really makes me lose my bearings, and I'm not one to get dizzy easily.Almost forgot, thanks for the shot Vin.

Bernd,Look at the EIS control panel on the glareshield. You'll see increase/decrease range keys.If you aren't sure where I'm talking about, look at pages 23 (AGEN.10.11) and 427 (INST.30.1) of the PMDG MD11 systems manual.

Glad you've got it working again. :(

The only issue I remember with initialization was fixed in the latest patch. Are you running that patch? v1.20.0055To check if that is the issue, open the load manager, and load some weight, whether it be a passenger or cargo. For whatever reason when the plane was at 0 load, it wouldn't initialize. If that is not the case, it might be an activation problem and I'd suggest emailing support. EDIT: I could be wrong on it being an activation issue, but that's the only thing I can think of. Why it would happen after setting it to your default flight, I'm not sure. Sorry I can't be of more help.

Alex, can you test TNCB and see if you get it there as well?Jim, if you get a chance can you test TNCM and see if you get the same issue as Alex? Are you using the 0905 navdata like Alex is? Just wondering if this is some sort of weird navdata problem. I'm using the stock navdata, and that might be why I'm not seeing it. Hopefully we'll get this one figured out.

Keith, unless I'm just misunderstanding you here, you won't be leaving VNAV by pressing the knob to climb.Quick example. You take off and are cleared to 13,000 feet. While climbing to 13,000 feet VNAV SPD will be displayed on the PDF. At around 12,000 feet (I'm not sure if it's 1,000 feet before or another number), VNAV SPD will switch to VNAV ALT. You level off at 13K and fly awhile. ATC finally clears you to 29K feet. So you dial in 29,000 on the MCP, then press (left click) the altitude knob. VNAV ALT changes back to VNAV SPD and away you go.Forgive me if I've just completely misunderstood you, but the above is what happened in the quick test I just ran.EDIT: I guess what's confusing me is why you think you're leaving a VNAV climb.

That's a strange one and I don't think I've seen any other reports of it. Maybe send an email to support, they might have a suggestion for you. Sorry I can't be more helpful, just never seen this one before.

Martin,When exactly does it freeze? Is it when you push the DIR INT button, or are you doing something on that page? Any specific time during the flight this happens?

Been awhile since I've flown the 744, but don't you have to press the altitude knob to get it to climb to the new altitude?

Alex,I forgot to reply last night, but I checked both my FS9 and FSX installs at TNCM and the waypoint was where I would expect it to be, inline with the runway.I know Jim said it moves around, but is it always in that position for you, or do you also see it move around? Have you seen this at a different airport?

Can one of you post a screenshot of this?

Michael,I'm assuming you're trying to select the new destination using the "FROM" waypoint? If that's the case, this is a known issue and has been reported. As a workaround (At least it did for me, I don't know if anyone else has tried it) try doing a LAT REV using the "TO" waypoint.

Great to have them back. Thanks Tom and everyone that helped get the forums back online. :(

Dan, thanks as always.

I know this doesn't help you figure out why you're having the problem, but I just printed 20 pages worth of the manual and didn't have any problems.Can't say I've ever seen your issue, sorry.

Ian,Did it just start suddenly for you? Did you make any changes recently? I'm imagine anything you can think of, could help PMDG solve the issue. I don't want to speak for PMDG, but I know they are aware of the issue and are looking into it.

Malte,1) This has been reported to the proper people. As a workaround, use the waypoint you are flying to, instead of the waypoint you are flying from. It worked for me when I tested it out last week anyways. Try it and report back.

I wonder how well that would work on VATSIM. :(

There's your problem. :(For whatever reason, whether it be FSINN or something else, that temp is way too warm for that altitude, and would be the cause of sluggish performance.Try a flight off-line, without FSINN and see what happens.

Try the Flight1 registry tool.http://www.flight1.com/view.asp?page=library

Michael, if you're currently having problems with it not installing for whatever reason, I don't think a new installer will change that. (I could be wrong, but from what you're describing, it doesn't sound like an issue with the installer)What is happening when you try to install? Is it telling you that it's currently installed? Make sure you clean the PMDG files out of your registry (Only if you know your way around, otherwise I would not attempt to do so). I'd email support and tell them what's going on.Last but not least, make sure you email them to get your download link like it mentions in the email you get upon purchase of the extended download service.

James,Press the autopilot disconnect key a second time. That will silence the warning.EDIT: Of course Dan beats me to it. :(

Are you using FS2Crew? I don't know for sure, but "flt1fs2c.dll" sure looks like a Flight 1 and FS2Crew dll and not a PMDG problem. Like Dan said, I'd head over to the Flight1 support forum or even the FS2Crew forums and ask about it.

Chris, is it only the PW version?

Louis, I believe, and maybe I've just misunderstood things, that this is a FSX/Microsoft issue of some sort. I know there is a section in the PMDG introduction about things like this.I know if you try to reload the same type (Engines) plane, this will happen. Based on what you're saying about it not happening when you first load everything, this sounds like the same issue.EDIT: I found what I was thinking of. Look at page 77 (and 76) of the MD-11 Introduction. I believe that's what you are experiencing, but I might be wrong.