>...the pedestal panel is lesser than default>aircraft in some areas -certainly not looking like the real>one though-,...If one looks at the texture folder, the pedestal area in the VC is covered in correct detail... ;-)

I have found one possible cause for low frame rates: when using the FS default key (or joystick) assignments to open the panel views, it is possible to have multiple versions of the main panel open (like the normal main + zoomed-in version on top of it). Having two main-panel views open at the same time causes a drop in frame rate, even without any further action whatsoever: from 15 to 5 FPS in my case. Closing one of the main panels restores the original frame rates again (ie. 15 FPS for me). I checked that this effect does not occur when using the click buttons on the panel to open panel views.Furthermore, I noticed that derated thrust settings are not followed by the A/T on take-off and climb: if I set R-TO 2 with 0 degrees Celsius reduced temperature (ISA conditions), the N1 max is set at around 86%, but the A/T increases beyond this limit, regardless of N1 or TO/GA modes used.Related to this is the incredible climb rates, of even (momentary) 6000 FPM!, achieved with a CLB-2 setting.Something that has been noted by others: the FMC CLR key sometimes produces characters (X or Y) instead of clearing when clicked. When using keyboard control, this is not a problem as always works.One-time glitch?: sudden appearence of "brakes" when A/T reduced to CRZ setting, although autobrakes were off. Only way to remove was turning autobrakes on and off again.Hope this helps you in finetuning an already great product!Erwin Altewischer

Hi,Just a quick note. I've landed at MDW a few times with no problem (22L was active, not sure which you were using). Also, after seeing your post I tried a V1 cut on the same runway and stopped with no problem. Sorry but, you're most likely doing something wrong. :( As to landing, are you sure you're crossing the runway threshhold right at vRef? (this is denoted by a green REF on the PFD speed tape) As for takeoff, it does eat up a bit of runway but the V speeds and accelleration are fine as there is still pleanty left to stop on.-Shaun

Hi,Some new stuff, as of yesterday.35. If VNAV for one reason or other disconnects, the ALT HOLD annunciation is correctly visible on the PFD, but the MCP light fails to illuminate. If this is real life behaviour, disregard (I doubt it is tho).36. The flight director appears (ie. the cross-hairs) only after I press the TO/GA button. I suspect that they should be visible all the time after turning the f/d on, before takeoff that is.37. After the f/d appears, after engaging TOGA, it activates HDG SEL. Is this real-life behaviour ?38. Seems that the f/d does not command acceleration at the acceleration height that is defined in the FMC, ie. it does not command lower ANU for acceleration, but instead keeps indicating a very steep climb angle.39. VNAV seems to disconnect on its own. Have had this happen many times. I have read the threads about the possible reasons behind this, but have failed to identify my situations with them. Meaning that it does this erratically. Sorry for not being able to provide more background. This calls for some additional testing.40. When promptly advancing thrust levers to MAX thrust and then pulling throttles back (with a/t OFF!), a sound of a kind of "buzz" goes off, and the engines rev up to takeoff thrust. Is this again a feature of the NG ?? The thrust increase can be cancelled to again touching the thrust levers and bringing them back to idle.41. In the night lighting, the MCP display readouts actually become "boxed". Their font size decreases very slightly and reddish vague boxes appear around the numbers themselves. This looks weird.42. The FMC IRS pos entry seems to have some weird format. I have tried the format that the boxes indicate (ie. the same as PIC), and I have tried the format that Randy suggested (ie. without the dots). I have yet to try the format with spaces in the places where "degree" -symbols are. I believe someone stated that it should work with this. 43. The "MAZLOFTRI" should always be in the exact same position on every panel it is assigned to. When changing to the overhead, its position changes to upper right corner, which is pretty inconvenient, as one has to move the mouse back and forth to quickly access different panels. Guys, this seems a "non-issue", but believe me, it affects the usability and needs a fix.44. The autopilot speed hold. This bothers me a lot. The engines rev up and down and up and down to hold the set speed (at level flight). This reminds me of a badly configured PID-controller that does not integrate enough. What it means that once the A/T sees that "now were getting a tad too fast" it pulls back too much, then it sees "oops, now were getting too slow" and revs up to where it was without actually learning from the mistake it did a second ago, causing it to oscillate with abt 20% N1 all the time. Seriously not ok.45. The engines won't start if the fuel control switches aren't in the CUTOFF position initially when starting. I know that the real aircraft is not started with the CNT switches at RUN, but I think it should start if fuel is on and there's enough RPM in the secondary fan. If I quickly put the SW to CUTOFF and then back to RUN it starts.46. The FMC message annunciator light shows up even if there's nothing in the scratchpad, ie. no message. Again, disregard if this is true IRL.47. The standby gauges (excluding the artificial horizon) are almost unreadable. The ASI/ALTIMETER and the RDMI definitely need some finetuning in the graphics, imo. FYI I'm using a 21" monitor with 1280*960 so I should be able to read everything clearly. I'm sure that with a lesser resolution/screen size the gauges are unreadable.regardsTeroI have a couple more, but I forgot my notes home, so I'll be updating this msg later.

>36. The flight director appears (ie. the cross-hairs) only>after I press the TO/GA button. I suspect that they should be>visible all the time after turning the f/d on, before takeoff>that is.That happens in real also, FD appears only when TO/GA pressed.>37. After the f/d appears, after engaging TOGA, it activates>HDG SEL. Is this real-life behaviour ?I think is is real but I have to check to be 100% sureChrisAthens Greece

Chris,Thanks for the info. I suspected those two had to be non-issues.Tero

CDU Clean key is supposed to clear entire scratchpad entry when push&hold, but not on our 737NG :-(

I really love this aircraft! It flies great and it is "fun" to be a beta tester along with so many others.. reminds me of the Fly! daysSeriously, I do not mind some initial teething problems as long as the authors stick with it and fix the most pressing bugs..Now for my pet peeve, after the other stuff has been fixed, maybe..A little feedback on the panel graphics:For some reason, this panel is produced in 1280x960x24 bit color, which is lovely when examining the bitmaps, but does not seem to be handled well by FS2002.. the standard throughout all my add-on aircraft is 1024x768x8, this includes the visually stunning Dreamfleet panels.:Problems1. Banding of color.. just look at the center post picture, and yes, this appears on all the posted screenshots as well, so it is not just on my system2. Inconsistencies in panel color/lighting effects.. compare the main panel left corner with the zoom panel left corner.. one has a nicely textured look, the other is almost flat..These panels could be among the best ever, but the end result right now does not do justice to the great gauges which are truly world class!I've tried to fix the banding myself by reducing the colors from 24 to 8. but then I also lose the outside view which goes black.. so I guess I do need the authors to jump in and help..Keep up the good work, this has the potential of being a classic!

For #33, you must hit TOGA (MCP panel, screw top left corner)and then the command bars will appear. The pitch bar will first show a 10 degree's down until about 60 Kts and then show a 15 degree up command.

Hi Has anyone experienced a severe pitching up and down in the cruise and causing a loss of altidude.I had to turn off the autopilot to regain control and then switch it back on.This happened after one and a half hours of flying in the cruise at FL330 at mach 0.79 with MCP speed selected and LNAV engaged.This happened when over Bacelona VOR on the way to Ibiza.I was in the process of tuning the Nav radios to the Ibiza rwy ils freq at the time when this began to happen this could be a coincidence.I had no fuel inbalance at the time which i had been controlling by using cross feed to even up the fuel.I did have the APU fire bottle discharge warning.I was not flying online at the time and no weather programs running so no pressure changes. Regards Paul Cooper

This has probably been reported already but the barometer changes on the HG side but not on the MB side of the gauge when adjusting. However both are updated in the PFD.

"33. I don't get any F/D bars visible on the EADI for takeoff, even though I have programmed the FMC, armed A/T and set F/D on. The green box appears and activates for F/D, but no F/D crosshairs are visible UNTIL I select a lateral mode. This could (and probably is) be a NG feature. "According to our Boeing Maintenance Manual, TOGA triggers the FD bars, Tero. The FMA should show TOGA as a pitch mode. Depending on what NG variation your have, the FMA Roll mode should either be blank or HDG SEL. On the former, the FD roll command shows wings level. On the latter, heading error."The pitch bar will first show a 10 degree's down until about 60 Kts and then show a 15 degree up command."... or if there is an engine failure, 12.5 degrees.If the FD's are not selected on before TOGA is pushed, there is an automatic "pop up" mode where the FD bars appear at 80kts.. and will remain there for 150seconds.With the Rad Alt at 400', you can change F/D pitch and roll modes... and/or you can engage the A/P.If you simply engage the A/P, depending on what type of NG you are flying, the following happens...Pitch mode changes to FLCH (MCP SPD annunciated on the FMA) and the roll mode goes to HDG SEL, or, on the other type the roll mode stays in HDG SEL.If you select LNAV before TOGA, LNAV is annunciated on the FMA. What happens next is again dependent on the NG you are flying...The roll mode could remain wings level until 50' (where LNAV takes over) ... or it could be HDG SEL until 50'(where LNAV takes over).Hope this helps.Cheers.Ian.

Just a couple of things I have noticed.Cant get take off speeds to show in FMS or activate no matter what I do.Installed product several times and cant get FS2002 to recognise the 737 with wingletsRob

bump

>Iron Claw (what's your real name ?)>>Bank limiter was set to 30, that was the first thing I>checked.>>MikeIron Claw is his real name ---- I Ron Claw - he just forgot to hit the space bar between the I and the Ron when he registered and as I know him personally his family name is Claw.