sinonquoi

Hi, Thanks for the reply, yes it is very annoying (same here with the IAS mode, it first goes to 500fpm and then adjusts pitch to keep the IAS). Bumpy ride :sorry: Surely the fact that default VS is +/-500fpm must be written somewhere in the xml gauges, relating to AP, so there are only 2 possible, right ? Gauge_KMC321.xml or Gauge_KAS297.xml (and their vc variants) Is there any other possibility ? Any gauge gurus out there ?

Hi Bert, Thank you for your work, I've installed your mods and they work great. I have 2 additional points regarding the AP : 1/ There is no GA mode by default, but if you go and modify the aircraft.cfg [autopilot] section with "pitch_takeoff_ga=8" instead of "0" you will get the proper pitch for take-off/go around by hitting "Ctrl-Shift-G" (default FSX command for activating GA mode). I find this very helpful and probably realistic 2/ Is there any way to modify the default VS speed when arming the alt capture mode. It's set at 500fpm which is really low compared to normal climb schedule (I normally hit 1500fpm @180kts). Modifying it in the aircraft.cfg has no effect, I guess it's inside an xml gauge which I understand nothing about... :( Any insight appreciated... Regards!

What a great forum ! Thank you guys, I really appreciate the quick and insightful feedback... Now I see the light ! Yes of course cutback for NADP2 doesn't make any sense, I will retry NADP1 with Cutback & NADP2 without it, it all makes a whole new sense to me now!

Hi all, Maybe reviving an old topic everyone is happy with, but I have a hard time trying to figure this one out : If I want to make a NADP2 departure using the Cutback feature in the FMC, how do I manage speed ? Let me explain : - I set my Takeoff ref page 1 normally (using derate/assumed temp as needed), that gives me my N1 settings and V speeds - I select CUTBACK on page 2, keeping the default thrust reduction/acceleration heights (800 & 3000 by default), it gives me the reduced thrust setting that will apply passing 800ft AGL - I arm Autothrottle and VNAV on the ground When I take off, VNAV arms at 400ft AGL, and therefore Autothrottle will reduce thrust to cutback settings by 800ft agl. However, I'm not sure how to handle speed : if I have activated VNAV (turning the A/P on), the FMC will set V2+20 for speed and keep it up until 3000ftAGL. My understanding from the above discussion is that, using NADP2, I should accelerate to flaps up speed as soon as possible after 800ft AGL, right ? Should I then use SPD INTV instead of FMC speed as described above, or am I missing something ? But then if I do that, depending on weight I might have a hard time keeping positive climb under reduced thrust and trying to accelerate to Flaps up speed at the same time... Any insights on this, or am I mistaken ? Thanks! T. Simon

I have not done anything special, I had ReamTrim 1.7 module installed prior to installing PMDG 737 NGX and it worked right at first install. Dońt know what could explain the difference...

Hi all, Just to add my 2 cents, I use realtrim v1.7 for FSX, and it works perfectly with the NGX. I am using a Saitek Cyborg evo joystick, I have assigned 1 button to realtrim and it makes trimming a breeze : when pressure is applied to the joystick to adjust pitch, I then just push the assigned button while releasing the joystick back to neutral and it's perfectly trimmed. Personally I find this pretty realistic, at least compared to my own experience flying a real light aircraft. In real life you know when you're trimmed because you feel the pressure disappearing in the hand holding the yoke while you trim with the other hand (I flew a Robin DR400, I'm French too...). To me, realtrim reproduces that feeling pretty well...

Thanks for all the good feedback ! Ok, since Jgid had the exact same issue this is most probably either a bug or navdata issue. I checked the LFOP.txt file in FSX\PMDG\SIDSTAR folder, the line describing CEN N SID is correct, I don't know enough about how the navdata works to investigate more... As per AP engagement, yes 400ft AGL is mentioned both in the FCTM and in the tutorial flights. I read in a Ryanair FCTM that if AP is not engaged by 1500ft then it should be mentioned in the departure briefing, so I gather the SOP is to have it on by 1500ft latest... I tried again with HDG select and VOR/LOC armed, it works perfectly, so I guess I will do all my SID departures following that mode and then switch to LNAV upon reaching the transition, so as to minimize navdata issues... Any thoughts on how to check/fix navdata ?

Hi all, I'm having a blast with my newly acquired 737NGX, even more so with FS2crew installed... I have an issue, though : this happens every time, even with no external weather, FS2crew not started, just the aircraft : - Take off from Rouen airport (LFOP) rw04, using SID CEN 3N which says (official chart) : climb MAG 042°. At 1000 (488) turn right MAG 271° to intercept and follow RDL 241° ROU (MAG 241°) to ELBOX then RDL 083° CEN (MAG 263°) to CEN. - FMC fully configured with take off RW04, SID activated, LEGS checked showing proper waypoints as per the SID description - LNAV/VNAV armed on the ground, then CMD A selected at 400ft above ground, which translates to 920ft altimetric - Planes starts to follow the LNAV path perfectly, executing a right hand turn at 1000ft to reach 271° magnetic heading Then things go wrong right before reaching the next waypoint, which in the FMC is a calculated (INTC) waypoint, for the ROU RDL 241° intercept. Every time I am about 2nm from the intercept point (LNAV still active of course, correct path visible in the CDU), plane starts to turn strongly right to a heading of 330° approximately, goes beyond the waypoint and then starts turning back left, overshooting the 241° radial before re-aligning with the correct path. What could be wrong ? I have tried putting a speed restriction down to 180kts at (INTC) waypoint, thinking it could be a case of flying too fast to intercept the radial properly, but it does change anything... If I take off from the other direction (RW22) with the reciprocal SID (CEN 3S), everything goes fine and the planes captures the 241° radial perfectly and smoothly... Has anybody got any idea what could cause this, and how to fix it ? Thanks for your feedback... T. Simon

Thanks for the tip, I had checked and the files are not available for download, I guess copyright issues. Seems like PM is the only way, for some reason I don't understand it is not possible to PM bliksimpie at the moment, I hope he is still around and looks at this thread sometimes... Cheers!

Hi all, Seems like it's not possible to send a PM to Bliksimpie now (it says "user cannot use messaging system"). Anybody know how to get those adjusted GNS430/530 gauge files ? Thnks!