as-lu

Probably, Back in the day we used a sertified simulator called Link, which was crap, and we logged those hours... FSX is a pretty good prosedural trainer if you want it to be, certified or not.

I think this is a small bug in how the T/D point is displayed on the ND. You are turning sharply to the right, 120 deg or so. The FMC will calculate a standard rate turn, which means it needs to overshoot and intercept back on track, hence the "turn" without the waypoint. I have noticed that when such an intercept point and the T/D (or T/C) point is on the same leg (ie between two waypoints), the T/D symbol "jumps" from its calculated position and sticks to the intercept point as seen in your pictures. It only applies to the generated image on the ND, as the path in the FMC remains correct. A bug, I think, but it rarely happens an isn't a problem as such.

I prefer the NGX. The T7 is not my cup of tea, but I got it anyway, if nothing else to keep PMDG in business. Here is hoping for the SP2 release. Oz

StrangeMine (HF4) flares just fine. Flaps 30, 2 deg deck angle on app, Vref + 5, idle at 20-30 ft, adding about 2 deg (about 4 deg deck angle on touchdown). I tried up to 20 kts headwind, and with Vref + 10 same result: a flare somewhere between 600-800 ft.

I had this too, a couple of times, in the original release. Haven't seen it since HF2, though. To fix it I down-selected the waypoint at LSK 1 (LEGS page) and up-selected it right back, i.e. making the FMC re-calculate. Each time I saw it, this made it go away.

+1

If you have FSUIPC, delete the FSUIPC ini-file and let it rebuild (make a back up). If you have FS-recorder, repair the installation after adding the hotfix. Just a thougt.

Same, thank you

This was submitted by Armen L Cholakian about an hour ago. If it is a new DDoS going on, the server is going to be choked up. PMDG can hardly be blamed for that.

This is OT, I know, but this forum needs nothing if not humor.- IanThey are available on YouTube: