Legend

Originally - back in the time of propliners - it had to do with the captain not being able to see the nr 2 engine - so he had to hear it starting up. After #2 got started OK he could start number 1 - which he could see himself.Can't remember where I read that but it sounds logical. I guess they just kept the procedure of starting number 2 first.

Happy birthday RSR!

Really looking forward to this. Will the manuals be released (for download) via the PMDG website?

Well, it happened immediately after changing the video card, and the cause was always "NV4_Disp.dll". I'm not the only one apparently - Google showed a lot people with similar problems. Chipset, BIOS, sound drivers etc. are all up to date. But you're right of course, time to start changing things. Most of the components of the computer itself are three years old now.

Well, I recently changed my 9600 to a GTX460 (1024MB), and have a lot of problems with it in FSX - BSODs (that seems to have stopped after manually changing NV4_disp.dll to a newer version), artefacts... but occasionally I can play a bit around with it. Like yesterday. In the "Africa relief" mission I got up to 70 FPS - something I've never ever seen before in FSX. That was with the 260.99 drivers (upgraded from 260.89). I still use WinXP 32bit BTW - I guess NVidia doesn't pay too much attention to a decade-old OS based on a 2-decade old architecture.

Oh dear... think of all the discussions that would appear then!http://www.ems.psu.edu/~fraser/Bad/BadCoriolis.html :(

The picture looks great, can't wait to see the full version. My credit card is ready!For the previous 737NG there was a great tutorial on just about every system written by Timothy Metzinger. That document really helped me get into the aircraft. I hope something similar will be written for this one as well.

This looks really good, Richard. Not being a native English speaker I'm a bit nervous about using Voice FS2Crew (I'm thinking of getting the button version as well) but this being so clear and linear I'm giving it a try tonight.

OK, then I won't pull more hairs out trying to find a solution. Thanks, Mike!

Apologies for digging up this topic... but I just installed the Captain Sim weather radar. It installs beautifully into the panel, but it seems the buttons don't work - I can only turn it on, and change tilt and range, via the 2D popup. Anyone has the controls working in the 3D pit?

I printed it out on my Canon IP4000 printer with separate ink cartridges. Then had it bound in a copy shop. Total cost wasn't very much (considering it's around 1400 pages), less than 30 Euro I guess.

Looking goood!Dank je wel!

Agree, after a not-so-wonderful start where I got an OOM error every flight, I did the /3GB magic (thank you, Gary A) and it turned me into a happy bunny. Lovely aircraft, good to finally see some different logic than Boeing's. One little snag, it didn't follow the vertical profile in the tutorial, but maybe I overlooked something (yes, I did reset the altitude window to 4000). Thank you for another wonderful product, PMDG!

Thanks - I had searched with MD11 and routes... didn't find the other thread.

Just wondered, what are typical routes for the MD-11? I know KLM uses one on their Schiphol - Dutch Antilles route (don't even know exactly which of the islands actually - could be Aruba or Curacao :shame: ). Is it also used in short(er) flights?Thanks!(oh, and I don't have it yet - have to wait till the end of the month, I'm afraid)

>You are not leaning or any pressure on the flight sick at>all? Flight stick isn't 'spiking' or anything? >>JayNo, after I engage the A/P I don't touch it anymore. It's completely spike-free - it has Hall-sensors instead of pots, so technically it isn't even possible to spike, but I checked the "joystick analyser" software and there it also shows no spiking. Apart from that, I did not mark the "controls override" boxes in the PMDG options menu. And it only happens during the climb phase. As soon as engine mode changes to CRZ, the problem disappears.

Anyone? It happens on every flight nowadays; also when I don't use ActiveSky (so I don't think it's influenced by that).Also I noticed some strange message on the FMC today - "max alt FL217" or similar - and that while the Boeing had a zero fuel weight of 540768 Lbs, and I had 166000 Lbs of fuel on board - well within limits. Also, when I programmed the flight in the FMC I could go directly to FL350 - so it's not overweight or anything. I did another test where I cleared all weather - same results. So if anyone knows what could be causing this, please let me know!

Recently I reinstalled the 747, today I wanted to do a pretty long flight (EHAM-TNCM), but during climb every few moments the autopilot disconnected. Sometimes there were 30 seconds in-between, sometimes it disconnected the moment I pressed the CMD-A button. In total it disconnected some 60 or 70 times today I think. I have NO idea what causes it; the disengage bar stays up, I've checked my hotas (Thrustmaster Cougar) for unwanted keypresses but there are none. I use FSUIPC to suppress gusts / turbulence, and I also use ActiveSky V6 with "FSUIPC wind smoothing" checked. Also there doesn't seem to be extreme weather - it was a nice, 15kt tail wind during climb. Setup had been done correctly AFAIK, VNAV and LNAV were engaged.After I reached cruise altitude (so when Engine mode changed from CLB to CRZ) the problems were over and I had an uneventful flight. But it was very annoying, the first 30 minutes or so.Anyone knows what this is?

...and that solved the problem! Thank you, Tim. It has been there... can't remember deleting it... strange...

As soon as I pick the R4D or DC-3 from the aircraft list in FS9 and click OK, I get an error that GAUGESMAAM_R4D.gau could not be loaded. I can't click the message away (or rather, it comes back directly) so I have to kill FS9.exe. When I use Explorer to see if the gauge is there, it's no problem. I've also checked the FS9.cfg file to see if FSSound.dll is loaded (it is). So now I'm at a loss as to what's going on. Has anyone else had the same problem and solved it? Preferably without re-installing FS9 - that would take several days I'm afraid.Thank you!Gert

Hi,just to be sure, is this the correct procedure I'm following? I want to do a flight from EHAM to ZSPD - about 11 hours flight time - on January 14th. I've downloaded dat files (20070114_15Z_archive.dat) plus 13 consecutive hours - as I'm starting with a cold & dark situation. So, after I start up ASv6.5, I1. press button "Load Wx" and choose 20070114_15Z_archive.dat 2. press button "New Route" and import EHAM-ZSPD.PLN (which I created using FSBuild2). After that btn "Process" and wait until it's finished processing.3. press button "GE Pro". It asks if I want to install textures, I click yes4. Question if I want to start a predefined flight, "No"; then start Flight Simulator. In FS I create the flight (B744 at EHAM, time 16.35 local (15.35Z) and choose "Fly Now"5. Then, wait a few minutes until FSv6.5 has finished ("Un-pause on FS Ready status" is checked).Thank you very much!Gert Wijbrans

Don't worry, in a good discussion I don't take things personal.About these tips, I never had the idea I gave up things. It looks better than before I implemented them - maybe if you really start counting single trees or so there's a difference, but the look and feel is even better than before. I'm pretty good with computers, but I realise there are many people that know better how to optimise settings - and not from a marketing point of view where deliberate (too) low system specs are given ("it runs on the specs we gave, it just doesn't look like the pictures we used to lure you into buying" ;) ), but from another fan's experience. This was a general remark BTW, not aimed at PMDG.IMHO, the planes from PMDG are as optimised as possible while still retaining all their functionality. Although I'm good with computers, I'm not a programmer myself, but if I compare the myriad of options in the PMDG planes with some other (payware) aircraft, I think they did a good job.Yes, the plane is resource-hungry, but you get a lot in return.Also, as you yourself said, your system has a - by now - older processor, only 512MB of memory and "only" 40 GB of hard disk space. Presumably you run WinXP, which needs at least 256MB of RAM to run pretty smooth, but more is better. That means you have 256 MB left for FS9, and that isn't very much.

Hoi,you didn't say anything about your system specs, but there are some tricks to let even a pretty low system still have good frame rates. Of course you should start with disabling everything you don't need during flight - virus scanners, antispam etc. Next, see http://forums.simflight.com/viewtopic.php?...hlight=fps+tips for some very good advice on how to set up Flight Simulator. On my P4 2.4 @ 2.53, 1024, GeForce 6600GT I went from an average 10 to an average 18 FPS using this advice. Of course, in densely-populated areas it's a bit lower, but still very flyable. Good luck!

Dan... I thought that's why the company had an autopilot installed. So the pilots have time left for "pleasurable distractions". I use Snapper, which doesn't take much resources, and have a button programmed on my throttle to take the shots - never have to leave the throttle and stick alone.Chris, I had the autopilot on to save this from happening. After all, we'd just spend 9 hours flying - didn't want to botch it. And a 9-hour flight looks nice in my logbook ;)Jeff & others - I thought the Queen only caused turbulence :( the airplane ahead of us - a B727 - had just taken off, maybe a minute earlier, I don't know if it creates a lot of turbulence at the beginning of the runway. IIRC, the nose came down only a second before touchdown - it landed nose-first I think - but it happened so quickly that I didn't realise if main gear had touched down already or not. However, it could be the cause - sounds logical. And yes, I do have ActiveSky installed and active.Matt, will check later, but as I said, I think it happened slightly before touchdown - and in that case it was probably wake turbulence. Isn't it a bit strange that only the Queen can't land on bitumen? Never had any problems with other aircraft. I really must find this discussion. Thank you all!

A horrible crash occured today at Shanghai's HONGQIAO International Airport. The airplane, a Boeing 747-400, can be considered a total loss. Miraculously, no people were killed during the disaster.The pilot, Mr Gert Wijbrans, declared, "I was doing a standard landing. All three autopilots were engaged, everything looked normal. Flare and rollout mode were armed. Flaps were set at 30, speed was at 149 knots - VREF + 5. Then at the moment of landing, the nose suddenly came down too fast at the runway, resulting in the loss of the aircraft. Landing weight was at approx. 562k pounds, so well within structural limits. Only seconds before landing, Mr Wijbrans made the below picture, showing everything seems normal. http://xs101.xs.to/xs101/06231/Land.jpgAn committee, led by PMDG and several helpful people of the famous AVSIM forum, will conduct an investigation to the causes of the crash.