Pentium4 2.6gig 800mhz FSB (Dell 8300)ATI Radeon9700proWindowsXP Home1gig SDRAM100gig HDFrame rates are a problem after using this plane for awhile (this is only when I choose the rear cabin option or use the 2D panel in a turn). I notice that the plane seems to need allot more thrust coming in for landings than it should, reverse thrust is not strong enough to help stop the plane on landing rolls, and the braking is kind of weak. I had to adjust the AIR file from -20 to -50 to give me more reverse thrust power. At KMDW I would just over shoot the runway when trying to land and end up in the trees. KMDW is a perfect airport to test aircraft such as this (737s), these planes fly in and out of that airport all the time. Overall the plane is underpowered because I can barley take off from KMDW. I tried to adjust my fuel load to 50% fuel in each tank but that did not solve the problem (still testing, I might not have the trim set correctly). I can't use the rear cabin because the frame rate hit is too great on my system or better yet it's noticeable enough to #### me off (machine specs above). Can't turn on the inside panel lights at night, it would be good to hear some APU engine sounds if the thing is on. I'll try and post more findings as I see them....

Hi,As for the brakes being weak and the plane being undepowered.I would think again. These guys have put some SERIOUS work into the FDE and performance, and I know this for a fact.Obviously the several B737NG pilots who tested it would have noticed such horrible performance issues you're describing.I believe you are having trouble with the a/c, but I dare to blame something else than the AIR -file.Tero

Well Tero all I know is ATA flies these things in and out of KMDW all the time and I have yet to land this thing without running out of runway because the reverse thrust is not helping stop the plane. Try taking off from KMDW, you can barley do it...

I've noticed the thrust reverse sound playing over and over again instead of being constant when using the thrust reversers. Seems to play then it's almost like the end of the sample and so it plays again.

Hi all,well I would like to second some of the glitches that have been reported such as the APU and engine #2 fire bottle discharging and other minor things that have been reported so far.One thing I noticed in the use of the FMC is that the cost index doesn't have any effect on the CRZ speed/mach in the FMC. Did anybody else find this?Regards,Bjorn

HiYes the cost index doesn't have any effect on the CRZ speed/mach in the FMC, so the same here.

Hi,I'll try it later tonight.Meanwhile, you DO have your autobrake set for landing (2,3 ?)and spoilers armed properly ? Also, is your Vref speed right, that is taken from the FMC ? One more, make sure you do land in the vicinity of the touch down zone, not half way the runway.Tero

Here are a couple of little 'issues' I've discovered:1. The plane's steering on the ground is out - it should have a tighter turning circle than it currently has.2. Although 'mapped' on the CH Flight Sim Yoke (and working fine with all other FS planes), the buttons to engage/disengage the Autothrottle and Autopilot don't work. Have to use keybord or mouse clicks....Also, how do you get VC, cabin or wing views? Minor issues though, overall delighted (so far).Toni.

"- The APP/GS dive issue, I've been experiencing it as well, workaround is to not to engage APP until the glideslope becomes visible, use LOC/VOR until GS becomes active instead"This is actually the correct procedure in case of a false (deflected)LOC beam in the real world. Nevertheless, the glide-slope conroller will *not* engage if, say in alt hold, until half a dot deflection, as per aircraft manufacturer specifications. The plane will never "dive" unless you capture at 300+ IAS...Wonder what was the setup at the time. Email me."AP fails to disconnect upon autoland touchdown, manual disconnection (through depressing "Z") does not disconnect it either, I actually have to click on the buttons to turn it off, rather annoying when there are other aspects of the procedure one has to take care of at the same time"The AP does NOT fail to diconnect because it DOES NOT auto-disconnect in the real world after touchdown. By the way getting out of APP mode, *after* GS is captured is : AP off *and* flight directr reset...This is why LOC capture is better performed in VOR/LOC mode because this way loc capture *can* be deselected (see comment above). Of course in the FS world this will never happen. A shortcut would be nice yes !Vangelis=========================================== E. M. Vaos Precision Manuals Development Group [email protected] www.precisionmanuals.com===========================================

Not sure if this an issue at all since the real NG AP is somewhat known to have flaws too, but I have the NG overshooting an LNAV path by around 3-4 NM, when a heading change of e.g. 120deg is involved (e.g. when changing airways). I'm somewhat scratching my head whether this overshoot is a bit too much ?Other than that I'm more than impressed regarding the AP performance. Great job !Mike

I have also noticed the auto pilot key playing the sound but not disengaging it.

I don't believe that this is exactly a "flaw". when LNAV changes waypoints it tries to join the line running BETWEEN the previous and next. With a big turn this will cause it to end up a bit outside, and then fly an intercept to get back on course. There is something that you can do to make things smoother for your virtual pax and not have them wonder why you are zigzagging back and forth during the turn. (Hmm, has our pilot been drinking??) :)Simly go to the legs page, downselect the first waypoint (the waypoint you are currently turning towards) to the scratchpad, then upselect it back into the same spot. This will cause the FMS to recompute a path from your CURRENT point in the turn, direct to the next waypoint. Do this a couple of times, once in the middle of the turn and once fairly late in the turn. Maybe 3 times if it's a really big heading change. This way the plane will roll out direct to the next waypoint rather than flying an intercept for the above mentioned line.-Shaun

Insufficient fuel warnings throughout the flight, even though I had twice the fuel I needed for the trip. The fuel amount had disappeared from the progress area of the fmc and nothing I did could get it back.I found that every time I tried to start up FS2002 with the PMDG 737 FS2002 would crash. I had to start flightsim with another aircraft and then select the PMDG 737 afterwards and even then when selecting a PMDG 737 with a VC it would crash so I have not had the chance to see the VC yet. This may go away after I get my registration code from you all because the program crash comes as soon as the 10 day unregistered warning pops up.On approach to CYYZ as soon as the glideslope was captured the plane took a nose dive and went straight into the ground. On my second flight to KIAH the approach and landing worked beautifully and the landing was perfect. I will try CYYZ again to see if it happens again.system specsWindows XP at homeP4 3.0 512 rambus memoryATI 9700 pro video card200 gig hd (80% free space)Audigy 2 soundcardWilliam

I too have FPS problems with the 2D panel - not using the VC or VC/cabin versions at all. I have an Athlon XP2400, 512MB Ram, GeForce4 Ti4200 and SB Live!, and have not had this problem with any other payware aircraft. The FPs jump from high to single-digit lows causing unflyable stuttering.ThanksJonathan

Hi PMDG!!This is a really nice piece of software here...And I'm sure by the way I see you workin' that you'll solve all the little bugs...So, may I suggest you implement a real clock with all the functions we find in almost all FS addons today?? You know, chrono, ET, zulu/local time, etc...FritzPS: How do get auto-calculations of V-Speeds for take off???