Scott434

apparently reduction and accel alt do not currently function correctly. The reduction from take off to climb thrust setting on Takeoff pg 2 was being ignored. I submitted a ticket and was told that it would be fixed in SP1. Thinking that the fix might be in HF4, I tried different altitudes for reduction and accel alt and it seems that it is still is not fixed. Since this is a complex sim, it is possible that I am not doing something exactly correct so if others can alter the transition from takeoff to climb thrust using the reduction alt on pg2 of the Takeoff page then please report back. No matter what I set reduction alt to, the NGX switches to climb thrust around 800'.

This works and is how I have it set up. The other way is to simply move your throttles to N1 as has been suggested.

Thanks Al, great informative post once again. REX must do some "blending" so I guess it becomes a trade off between accepting REX as good enough for the intended purpose against another program to buy, learn and administer.

I am sense (all subjective of course) a smoother "NGX experience" and believe there is a slight fps gain judging by the fps numbers (I usually never have this displayed while flying). Landings are refined. The NGX is exceptional in so many ways and runs without a hitch.

I use REX2 OD for environment and weather. I cannot comment about the differences with ASE since I do not have ASE. For my purposes, I simply want the weather to reflect local conditions when I am flying. REX downloads from weather stations and then loads/adjusts fsx appropriately using its fantastic textures for clouds, water etc. IMHO, REX does this extremely well and supplies some incredible beautiful skies and does so with one add-on therefore eliminating an additional program.I would like to hear from anyone who has run REX weather and ASE to learn what the primary differences are between the two however. If you end up using REX for the graphics, what does ASE add? I fly primarily Washington, British Columbia and Alaska with the NGX and the Beaver using OBBX NA Blue, REX Overdrive (HD textures) and REX real time weather. It truly is pretty sweet.

Interesting article. Pages 1 and 2. Pages 3 and 4 Pages 5 and 6 of 6

If that is indeed correct, I believe Mr. Gollnick must have made a "cut and paste" error when responding to you. I have a feeling that such a basic and trivial thing will be eventually corrected.

Alaska Airlines 738 at CYVR. Imagine for a minute that there was a "send lat, long, alt, aircraft type/livery data" capability/function while a PMDG aircraft was present in FSX. PMDG could assemble this data stream and present a real time "Flightaware" type map showing where all of the NGX aircraft were (and other PMDG aircraft). This would be way cool and a total PMDG differentiator. Just saying.

This "trend" has been the the norm for a very long time for complex multi-feature s/w products. I recall moving to this model late 90's. We "rolled out" features on a regular "milestone" scheduled basis. At each planned milestone, the product was evaluated and released based on the maturity (feature and regression testing state) of the build. Those features that were not "hardened" were not integrated in the scheduled release and had to wait until the next scheduled "rev" milestone. Without using this model, customer's would have to wait years before for a final product hit the market. While it seems that pmdg are somewhat sheltered by being having a lock on premium fsx addons and might enjoy the luxury of not having to cover a full payroll based on the revenue generated by these products (purely speculative), there are great advantages to using the phased incremental rollout model. Other than the obvious (not waiting for 3 years per product), one of these advantages is the exposure of less code to more users in a gradual way. This effectively widens the "beta" spectrum and allows early discovery of larger problems. It potentially shortens the response time to serious bugs since the lines of code delta is smaller and partitioned into distinct functional areas. This also, by definition reduces the total number of bugs per release cycle thereby increasing the customer's perception of quality. I am very sure that the "area under the curve" since the Aug 4 release date would have been much smaller had this approach been adopted. IMHO (and in the grand scheme of things totally irrelevant), the ngx would have benefited greatly using this approach. A practical example of this might have been rolling out the ngx much much earlier with less features along with a scheduled list of added features to be rolled out in time (no dates, just the planned sequence of features). I am quite sure that the majority of customers would have rather had the ngx earlier with less. Example might be the HGS, the crazy (in a positive sense) number of aircraft options, cabin pressure/temperature, brake pads choices, certain obscure fmc extras etc. The point is that the ngx would ultimately evolve into its final wonderful state but in an evolutionary sense with much less "gnashing of teeth"/"churn". In my view, Ryan is completely correct. The NGX should have many many many smaller less impact REGULAR updates and the above mentioned feature roll out. Ideally, a "check for updates" feature would be available from within FSX (from the addons->pmdg menu). If not technically possible due to fsx limitations then as part of a stand alone program such as the livery/textures program. No muss no fuss just regular slow but steady progress. ( A side benefit would be the reduction of the forum "noise" on the topic of release and hopefully more focus on the actual flying of the NGX). The above "arm-chair-quarterbacking" was simply a single voice from the sea of customers and was written in the most positive and constructive spirit. I have had the NGX installed and have been flying since the release date Aug 4 without a single major problem. This is a more than a great aircraft and I am very grateful for the dedication and technical abilities of the PMDG team. It has no doubt brought a ton of enjoyment to many and will keep doing so for many many years. As my sig says, Thanks PMDG!

actually, great idea. Let's all keep bumping this thread so it remains visible on page 1. It is really deserves a pin more so then other pinned topics.

guys, I posted a precise guide to setting up thrust reverers using FSUIPC. it is dead simple. here are a few key things:- don't use FSUIPC for throttle axis or calibration. - use FSUIPC to program throttle dec with repeat to the saitek throttle lever button that is triggered when moving the lever past the idle detente. Program throttle cut upon release of this same button.- as Patrick pointed out, set autothrottle option to section, Never OverrideThe above is exactly what inhale been using and it works perfectly.

The reason I asked for further explanation is that your reasoning was contrary to my understanding. This option should be ON as it only makes sense to use the FSX number NOT the nav data number. Unless of course there is further discovery, follow the recommendation in the PMDG intro.

could you explain a bit more. would it not be better to use the FSX value so that you land correctly? after all, you are actually landing at an FSX airport regardless of what the plate says. not sure I fully understand this.

Hotfix3 is still doing this (see below). The contents of these files looks like the output of some embedded debug code. PMDG, shouldn't your "reach" be limited to the FSX installation folder? Might be a cause of some instabilities.

While performing a TOGA takeoff, what exactly triggers the switch from TO to CLB thrust mode? Is it the altitude you set for "Reduction" (pg 2 of Takeoff page) only? I am setting Reduction to 3500 but thrust is still being set to CLB at approx 1500 in spite of the Reduction setting. I assume I am missing something. My scenario is a simple hop from CYYJ to CYVR with a quick cruise altitude of 3500 ft. FMC flight plan is all good everything works (speeds and altitudes). What I want to do is takeoff with reduced thrust (0 pax, 0 cargo), fly the FD (not CMD), with vnav and lnav engaged until 3500 at which point I would like to retract flaps and carry on. I have set the cruise altitude to 3500. What ends up happening is in my takeoff and climb to 3500, it switches CLB-2 at around 1500 which causes an under speed condition (yellow box on speed tape). This behavior is with the "Reduction" height set to 3500 (pg 2 of Takeoff page). Been at it for quite some time now so it time to ask those who know. Thanks for the help.

If you could post a screen shot that would be great!

great work, very helpful and timely. This should be pinned.

I agree. But ... the real question is when is it appropriate.l think the "RTFM" applies when someone has purchased a complex top shelf product and puts ZERO effort into learning the bare bones basics and expects to be spoon fed. Do you think this same person is going to be a contributing member to the community? Not likely.I recall one post where someone posted a question asking why they could not start the engine with ctrl-E! In this and similar cases, RTFM is a very polite response. Or what about "do I need FSX sp2". I mean where does it end? Another example is people who ask questions without using the search feature beforehand for topics that have been beaten to death. Perhaps UTFSF should be the appropriate response.Other than these extreme examples, I agree that we should err on the helpful side but like everything else there is a limit.BTW, can someone tell me how to run the NGX on my xbox?

Easier method using Button assignments. Thanks John.

Actually, that is what I was trying to do at first but did not know how! This is the most desirable way for the reason you mentioned. I will post another pdf guide with this method shortly. Thanks John!!

The attached pdf provides step by step details on how to setup the Saitek Throttle Lever to operate the NGX thrust reversers using FSUIPC.

can someone with FSUIPC and a Saitek Yoke tell me if FSUIPC can read the mode switch located on the top rear of the right hand grip? Thanks!

when your wife is "driving" and you are gaining a lot of momentum, and you call out "Rotate".

Simon well appreciated, 19,353 words!! - thank you again. For convenience, I assembled all of Simon's posts and pictures into a single PDF.

you have likely mapped a button FSX uses to turn on/off the adf/vor ident tones. If so, simply remap them to something else.