I just made ONE little test-flight ending with a crash with the patched 737. Most of the 2 - 3 main-problems I noticed in the first place with the original PMDG 737 seem to be still there! A new bug(?): - I cannot enter any coordinates for the intial position anymore. The ones shown on the INIT-page were completely wrong (though the display on the ND was OK).Of course the IRS is not simulated, so this does not matter much anyway :-(- I still cannot enter a waypoint for missed approach into the FMC.- selecting the airport - display, the FMC still shows me all the airports squeezed on one side of the ND-display (probably some error in the navdata?)- and the most annoying bug: I deliberately waited until my T/D was far behind and then selected a new altitude: AGAIN the aircraft entered a 12000+ ft/min descend (see picture), overspeeded and finally crashed (I deliberately waited to see what would happen).The PMDG 737 should be grounded by the FAA!Walterhttp://forums.avsim.net/user_files/27615.jpg

I cannot enter any coordinates for the intial position anymore. The ones shown on the INIT-page were completely wrong (though the display on the ND was OK).Of course the IRS is not simulated, so this does not matter much anyway :-( Just LEFT CLICK TOP LEFT LSK1, this will at least put the right coordinates on the text for ya ;) and the most annoying bug: I deliberately waited until my T/D was far behind and then selected a new altitude: AGAIN the aircraft entered a 12000+ ft/min descend (see picture), overspeeded and finally crashed (I deliberately waited to see what would happen). Ok, so how did you get the aircraft to DESCEND? If you wait to long, just reseting the FMC will not normaly bring the plane down because Vnav will not be able to follow the path, so did you engage LVL CH or did it come down on it's own the moment you reset your MCP ALT? I would like to try this myself, how far past TOD did you wait? PMDG are aware of some potentail issues related to this so as much information that you can provide will be of great help. What simulator, what time of day, were you in window mode, etc...Thank you [h5]Best Wishes,Randy J. Smith [h4]P M D G 7 3 7 NG[/h4] [h3] Realism on the horizon [h5]AMD XP 2200 |MUNCHKIN 512 DDR RAM |ECS[/b ][i] K7S5A MB[/i] |GF2 MX 32 MEG and still runs GOOD!|WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"[/h5]

> Just LEFT CLICK TOP LEFT LSK1, this will at least put the>right coordinates on the text for ya ;)O.K. Thanks (of course this is only a cosmetic matter until the IRS is simulated to some degree ;-)).> Ok, so how did you get the aircraft to DESCEND? If you wait>to long, just reseting the FMC will not normaly bring the>plane down because Vnav will not be able to follow the path, >so did you engage LVL CH or did it come down on it's own the>moment you reset your MCP ALT? I just reset MCP ALT and used VNAV. I have no idea what would have happened if I had used LVL CH (will try this next time when l feel like crashing a 737 ;-))...Seems like VNAV WAS NOT able to follow the path yet it still just attempted to do this and remained engaged. I would have expected a message like "unable to XXX" or "drag required" or something like that ... instead it just settled for a 12600 ft/min descend until it crashed :-(Well, maybe there was some improvement compared to the unpatched version, because then the rate of descend was 16500 ft/min :-)(Only that the captain intervened last time and saved the airplane ;-))>I would like to try this>myself, how far past TOD did you wait? I think I was something like 6000-7000 feet too high on the descent profile.> PMDG are aware of some>potentail issues related to this so as much information that>you can provide will be of great help. What simulator, what>time of day, were you in window mode, etc...Thank youStill FS2002, Windows XP (full screen), about 11:00, 737-600 (in case this matters). LOWW-LGKR. Cheers,Captain Walter (killed on August 3rd, 2003)

>> Seems like VNAV WAS NOT able to follow the path yet it still just attempted to do this and remained engaged. I would have expected a message like "unable to XXX" or "drag required"What was your speed during that ? Shouldn't there be a VNAV (overspeed) disconnect then anyway ?Mike

>What was your speed during that ? Shouldn't there be a VNAV>(overspeed) disconnect then anyway ?Speed was Vad (aircraft disintegrating speed) ;-)Seriously though...the overspeed-alarm sounded all the way down until breakup (unfortunately VNAV did not hear it). When I took the screenshot speed was 355 KIAS.I don

I also had this VNAV problem on a short flight, although I did not pass the TOD. I reset MCP alt before TOD and the a/c began descent at -1200 fpm also and stayed at that rate. Switching to CHG LVL made a steeper descent. The a/c was on a slow crz speed, at 13000'.I set 3000' in the MCP prior TOD.Initial crz in FMC and MCP was 5000'. I reset FMC and MCP alt to 13000' and the a/c handled the climb fine with smooth alt capture.I am trying a longer scheduled Alaska flight today. A friend reported he had no probs with VNAV on a properly set flight plan, PHL to MCO.Regards,Robert

O.K. Made a further flight LGKR - LEPA. I DID NOT exit FS2002 but cleared the FMC and prepared for the next flight. Strange things happened on this flight concerning the ND. 1) Airports showing up (as always) in some fantasy - places (see screenshot).2) Strange second magenta - line ending in a fantasy - place where LEPA and LGKR are more or less at the same place!!! THE REAL LEPA was not shown on the FD (apart from the fact that it was at the end of the first magenta-line).3) no T/D display on the ND (well, I found it later somewhere near the end of the first magenta-line). However the T/D was correctly calculated by the FMC and also shown on the FMC. Descent also started at the right time.3) FS 2002 now always "hangs" when exiting it.4) VNAV stalled the aircraft on climb (manually intervened). Reason may be that I flew manually until FL 100 and then engaged VNAV, which obviously confused it.Walterhttp://forums.avsim.net/user_files/27701.jpghttp://forums.avsim.net/user_files/27704.jpg

3rd flight (LEPA - LPMA) - 3rd problem: FMC generated a 3000 ft cruise level - flightplan again (after entering altitude restrictions near LPMA). Of course no VNAV available if one tries to fly using this FMC - mess...All in all the patch solved almost none of the problem *I* had with the PMDG 737 :-(Walterhttp://forums.avsim.net/user_files/27821.jpg