Hi all,I don't know if this problem is with the PMDG MD-11, my new Samsung LCD monitor, or with my video card. Here's the problem I'm having:First of all, I create a flight and select the PMDG MD-11. I create the flight departing from Birmingham Airport or KBHM on runway 24. I'm not flying to another airport. I depart on runway 24, fly out about 5 miles, and then fly downwind for a practice landing using ILS runway 24. When I perform this flight, I use the FMS. So when I enter the departure and arrival airport, I enter KBHM/KBHM into the FMS. This tunes the ILS for runway 24 and also tells me what my Vref and approach speed should be. The problem starts after I retract the flaps, and my screen goes black at this point every time. FS crashes and I get the message that FS has to close. It only does this with the PMDG MD-11. I've tried this same flight with the PMDG 737s, the PMDG 747-400, and the Level D 767-300, using the exact senario. By the way, I've tried this flight without using the FMS and the problem has not occured so far. Since the problem seems to occur when I use the FMS, I went to the PMDG MD-11 Options and noticed that I can select the 912 or the 920 FMS software. I selected the 912 and the problem still occurs. I need to mention that I had just bought a new Samsung LCD monitor and I replaced my Nvidia Ge Force Ti 4200 with the Ge Force 6200. When I went back to the Ti 4200, the problem still occured but when I selected the 912 software for the FMS, the problem stopped but I only tested once or twice. So I replaced the Ti 4200 with the GeForce 6200 and the problem returned. The problem with the 6200 is that after I select an aircraft from the Create a Flight screen, the screen flickers and it does this when I select any aircraft, selecting the airport, and selecting the time of day. Each time I select and click OK, the screen flickers a few times and stops and I don't understand why it does that with the Ge Force 6200. So, I'm confused as to what is causing these problems. I think I'm just going to go back to the GeForce Ti 4200. Have any of you had this problem?Ken Manning

Try this: Program a route in the MCDU for a departure, even it only selected runway, then a fix such as a nearby VOR and then select your arrival. Now when you fly it you might skip flying to the VOR but when you select your IAF or FAF for the approach as your next fix to fly direct to you should not get the crash.The FMS may not like a departure/arrival segment at the same airport without at least one enroute fix in the route.

Try this: Program a route in the MCDU for a departure, even it only selected runway, then a fix such as a nearby VOR and then select your arrival. Now when you fly it you might skip flying to the VOR but when you select your IAF or FAF for the approach as your next fix to fly direct to you should not get the crash.The FMS may not like a departure/arrival segment at the same airport without at least one enroute fix in the route.

Hi Dan,Thanks for the tip. What I actually been doing was entering into the FMS KBHM/KBHM and then I would insert that. It would automatically come up with a fix, which was LOWGA, and it was only 6.6 miles. LOWGA is the approach for runway 24. I tried your tip. I would enter KBHM/KBHM for the departure and arrival into the FMS but this time I did not insert it. Before I did not select the runway. This time, I selected runway 24 and entered a VOR, which was the Brookwood VOR practically on runway heading. When I did this, I haven't had any more problems so far. There is just one thing about the MD-11 that puzzles me. I noticed that when I arm the approach by pressing the APPR/LAND button, the auto-flight does not track the glide slope prior to tracking the localizer. It seems that the localizer must be alive and tracking before the glide slope will track. But at the last minute, the MD-11 will all of a sudden drop it's nose to chase the glide slope and then the airspeed increases and the sink rate is way too high. It seems that I must be on the localizer before the ball starts to come down. It will not track the glide slope if I'm not on the localizer.Ken Manning

The Boeings have an option to capture GS before localizer, but I would never want to do that.Get on localizer and intercept GS from below, that is the standard practice and the safest. If you are intercepting the GS at the FAF then you should be at the intercept altitude before FAF, usually 2 or 3 miles before if vectored there by ATC.

Hello, I get this issue sometime:I 'm trying some failures after takeoff and then landing back to the departure airport. My departure/destination/altn in the FMC are different (LIMC/LIRF and LIME); after takeoff and after the failure I select on the FMC the next waypoint lateral revision and i set as new destination LIMC (the departure airport), I put a STAR and sometime FS9 crash with black screen.....Any advice about?

Try this: Program a route in the MCDU for a departure, even it only selected runway, then a fix such as a nearby VOR and then select your arrival. Now when you fly it you might skip flying to the VOR but when you select your IAF or FAF for the approach as your next fix to fly direct to you should not get the crash.The FMS may not like a departure/arrival segment at the same airport without at least one enroute fix in the route.

Hi I got the same Problem with my test flight from LSZH to LSZHI Start from Runway 28 using deges1w transition, after the left turn i begin to ascend and then suddenly the screen goes black (inside FS9) and then after 5 seconds it pops up the message that FS9 has crashed. This happened 3 times at the same point of flight.I have not defined any other waypoints, it usually happens right before the second last waypoint.I tried then an other flight without using fmc at all, just takeoff without any settings and then it seems to work, i got no crashes.But the simulator should not crash, regardless of what fmc settings i use (the PMDG 737 and 747 is running fine, no crash)I will also post a screenshot from the situation about 2 seconds before the "Black Screen" so you guys might see something that causes the crash. (Will edit this thread in about 2 hours)ThanksRegardsMorpheus187

There is a known bug when you program a flight in the FMC that has the same origin as destination, apparently it doesn't happen when you add some waypoints (not relaated to SID/STAR or transitions).

It worked with entering another destination as you suggestedanyway i think this bug should be fixed :)see here the screenshot of the situation a few seconds before the "blackscreen" crashRegardsMorph

I think too that this bug sholud be fixed: to make another example, i was simulating some failures after a takeoff and I had to go back to the departure airport, so I typed the airoport in the field New Destinatin and.............. CRASH!And sometime also with intermediate waipoiont i get this crash.Hope PMDG' gonna fix that!

It worked with entering another destination as you suggestedanyway i think this bug should be fixed :)see here the screenshot of the situation a few seconds before the "blackscreen" crashRegardsMorph