To PMDG (Anthony),Because of the VNav and LNav deficiencies in the PMDG737 I've taken to hand flying the aircraft away from the departing airport. However, this creates a whole new problem. It seems that as you fly over waypoints they are not removed from the flight plan. This only happens if the a/p is engaged. Consequently when I do engage LNav and the a/p the aircraft immediately tries to turn back to the first waypoint. Ouch!I hate to keep making comparisons between this and the 767PIC but I can hand fly a SID with that aircraft and the waypoints are removed as I pass over them. Shouldn't this also happen with the PMDG737?Thanks,

Absolutely! This is a function of LNAV, not of A/P being engaged.PMDG, please fix.Lee Hetherington (KBED)

Lee,Thanks for chipping in on this, it's appreciated. However, I don't think I made myself clear enough and now that I have flown this flight again I'm happy that the MCP and FMC work correctly in this situation.Previously I didn't have LNav engaged, the second time I did and when hand-flying the aircraft, each waypoint was removed from the FMC as I passed over it. My mistake the first time was in not engaging LNav.On this occasion a false alarm.Cheers,

Oops. Glad to hear it is working properly. Yeah, if LNAV isn't engaged, the FMC won't advance.PMDG, never mind.Lee Hetherington (KBED)

I wonder if that is entirely true. It's one of those things that are very hard to determine just by searching through my manuals. I even have the Honeywell guide to the 744 FMC, but that's of no help either. However, I just tried it out in PS1, which is usually very well researched and found the following. I took off from EHAM and after take-off deliberately strayed slightly off course, so obviously not in LNAV. The first two paypoints were actually removed when I passed by, with a crosstrack error of less than three NM. For the third I strayed slightly further off course, to just over 5 NM of XTK error. That waypoint was not removed and while I write is still the active waypoint. One of the engage criteria for LNAV is that it will intercept the active route if it is less than 3 NM XTK. So I think it is possible that within that range waypoints are removed even when not in LNAV.Leo Bakker

Hi Leo,Interesting reading. Only PMDG programmers will know if this is a problem or not and it would seem they are keeping quiet about it. So quiet I'm wondering if they're still bothering to read these pages.To be honest I've just about given up posting any more bug reports. The silence has finally ground me down. I find it hard to believe they are all coding. I see another member of the group has found time to tell us about forthcoming liveries. Perhaps it might be better policy to acknowledge these concerns?Cheers,

Hi Ray,Well, I just read a post by Lefteris about one of my issues and most of that will be fixed. However, not every single item has been answered, that's true. I can live with that for now, I'll just wait for the patch and see what happens after that.This particular item was not meant to be one of my bug hunting reports, though. I'm not sure if the team are even aware that the possibility that I mentioned exists. What I personally would like to see happen in this forum, after the patch, is a general quest for knowledge, so to speak, about the 737NG, even though not everything may be incorporated into the sim itself. I personally like these "fact finding missions", where you pour through your manuals to see what you can come up with or to hear from actual pilots or technicians. In some cases, such as in this one, you'll see that manuals may not answer all the questions that you might have.I have noticed that my Boeing manual is more limited in scope than my Lufthansa manual. For instance on the question of autobrakes, which lead to quite a thread, apparently the team's documentation didn't provide some of the answers that I was able to come up with in my Lufthansa manual. So some things that we see in the sim may not be bugs as such, but just an indication of how difficult it is sometimes to find out exactly how it works in real life. Along the lines of the Boeing slogan of "Working together" I hope that the PMDG team and its users will combine their efforts to make this "as real as it gets". Or at least "as real as it is realistically possible to get" :-)Leo Bakker

Hi Leo,You obviously have a great deal of knowledge about how the Boeings work - I'm afraid I don't. All I have for comparison purposes is the 767PIC. I really wouldn't have a clue about proper operational procedures for certain functions - all I can do is trust that the PMDG group do have the knowledge and implement them correctly.Inasmuch as this particular feature is concerned if the VNav and LNav problems are corrected by the patch and I can fly a SID without recourse to hand-flying them I'll be satisfied. I can only hope that all the other problems are also fixed and the package delivers what it promises. I hope you are equally satisfied with the patch.Cheers,

One other thing with manuals is the fact that specific airline manuals do not list all the *options* for a particular item if such an option exists and this alone causes questions. I own a good number of airline and boeing NG manuals plus every CBT for the NG series but even then you really have to dig for correct or common options installed on most NGs. [h5]Best Wishes,Randy J. Smith[/h5][h6]The Next Great one? PMDG's 737NG is here![/h6][h3]" A little learning is a dangerous thing"[/h3] [h5]AMD XP 2200 |MUNCHKIN 512 DDR RAM |ECS[/b ][i] K7S5A MB[/i] |GF3 64 MEG @ 215/545|WIN XP PRO |MITSUBISHI DIAMOND PLUS 91 19"[/h5]