downscc

Mine is working just fine with Orbx NCA, I have not even looked at the Aerosoft Forum since I don't have an issue.

Why the patch? I am using this product in v5 no problem. However, I've found that quite often when the AF file is modified in v5 that often there is a problem with autogen on airport surfaces and elevation issue abound.

Rhett, the aircraft autoland feature does not require that the ground based ILS system be certified as a CATIII system. This is up to the pilot to know such things, and you should have dialed in the minimums for ILS27 (492 ft MSL) and before reaching minimums it is up to you to disconnect the autopilot to land manually.

Yeah, the FSDT is dated but still looks okay; and, I'm not very fond of Aerosoft support so I tend to stay away from them if I have any choice. That explains why I prefer UK2000 to the VAS killing mega airport heathrow.

Do you have a specific example of a missed approach procedure with a speed constraint that you have tried to use? You are very sparse with information.

The problem has been identified, PMDG said they cannot reproduce the problem at the time. If you have additional information that is relevant to recreating the problem then i recommend you use the open ticket as the communications channel to convey this. When does the "unable" message appear and how does it relate to the go around?

Full names in the PMDG forums please. You are saying something changed..., doesn't it seem reasonable that what changed was how you are configured or doing things? The NGX has not fundamentally changed in years. If you disconnect A/T at 1000 AGL then I assume you are controlling your speed manually until the flare, so when do you reduce power to Vref-5 and idle?

Has anybody taken the time to submit a trouble ticket as I advised last May? That will get more results than repeating the same thing over and over in the user forum.

Agree, the T2G KMCO is relatively new and really looks good, good performance too.

That is a very old thread. Full names on all posts in the PMDG forums. Do you realize that 40% N1 or higher is idle depending on speed and altitude? I set the throttle options such that the position is shown when moving, if the N1 needle is at the bottom of the moving throttle blue arc then you are at idle. See also the fuel flow. It will always be about the same at idle regardless of N1... usually 0.82-0.94 lbs x 1000 / hr depending on engine variant. The aircraft can be slippery and if you are descending above 900-1200 fpm it might not slow down unless there is drag out there, such as flaps, speedbrake or gear. It takes time to learn how to manage your energy, don't blame the aircraft yet.

Double posting isn't going to fix things any quicker. There's no announced update to NGX so minor bug fixes are in the queue.

My guess is that it is the Orbx objectflow.dll that is actually causing the delay. Make sure everything is up to date in the FTXCentral2 tool..., they release a new library just last week or so.

Not that I've noticed. There are things that lengthen load times, mostly stuff that is loaded by the dll and exe xml files but not the scenery. It isn't loaded if it's not within range. The only time that load times would be affected is when you delete the scenery indexes and P3D needs to rebuild them. The indexes are the key to not requiring a lengthy load time for sceneries on each load.

There is no update to the information already pinned in a topic on that subject. She is in tech testing. Wow..., we went three days without someone asking for an update. Must be a record.