Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

znypan

Members
  • Joined

  • Last visited

Everything posted by znypan

  1. I'm aware. I'm saying what PMDG is going to model
  2. The issue has been fixed by the devs for the next sp.
  3. Different WX maybe? I've checked the NGX with different LIDO generated flightplans and it's very accurate when it comes to fuel consumption (+/- 2% all the time). As long as the trip fuel is caclulated using the same mean wind component as the one you get in FS you should get very similar results. If you want, send me one of your FPs so I can have a look what the problem may be.
  4. No. For the PMDG one. But it happens that he's right since the real aircraft behaves like he said.
  5. First TOGA hit should give an 8% climb rate. GW and temps you tried it?
  6. Yes I see what you mean. This should be already fixed with Hotfix 2. Can you confirm this?
  7. Can you provide the route you were flying including the runway changes and the altitude? It would also be great if you remember any approx. payload/fuel values
  8. Yes. Make sure that the PFD has announced LAND3 (you'll also see FLARE in white) prior hitting toga. . That's when the ILS is actually coupled.
  9. Make sure that you use the fsx registry utility to correct the registry path of fsx: http://www.tweakfs.com/store/free_tools_module.php
  10. Please spend some time and go through the tutorial flight.
  11. That sounds normal. As long as everyone realises that the drill is Go Around, TOGA-Flaps 15 almost silmutaneously, positive rate-gear up the aircraft climbs as it should.
  12. That's not accurate. All you need is the GA mode to be armed. For a flight with no flightplan like the one you're tying, this occurs below 2000 ft AGL during descent.
  13. Have a look at the last item in this FAQ.http://forums.vatsim.net/viewtopic.php?f=43&t=56205 I'd suggest you repair your simconnect. People had the same issues due to faulty simconnect installations. For some reasons the WX engine injects hight temperatures in high altitudes. No jet can fly with an ISA+40. http://www.hifisim.c...leshooting.html
  14. So the question here is why an aircraft is not autorotating while another one does. They're different aircraft. Different aerodynamics. A Harrier can takeoff almost vertically while an F14 cannot. They're _different_ aircraft. I'm not quite sure about what exactly we're looking for in this post.
  15. You get unable 250 because in the descent VNAV page you have a restriction 240/10000 by default. Go and change that to 250/10000.The VNAV is calculating a monotonic path for descent. Which means when you descend your altitudes and speed restrictions must get lower. What you're telling the FMC is I want to cross 10000/240 and then below that you ask it to accelerate to 250. Something else you could do is to put 250B/ instead of 250/ for ARTIP. Also if you're flying with WX make sure you insert the correct values in the descent forecast page especially if you're flying with a tailwind component. A tailwind component could give you a TOD +10nm prior to the TOD you would get with no winds aloft.
  16. It's better practice if you disengage the AP at 200 above the runway elevation;)Btw ILS doesn't necessarily mean flying with AP. You can also fly it using the FD.
  17. It's the other way around.
  18. I've been using the Saitek yoke and pedals throughout the whole alpha and beta testing of the NGX. The combo worked like a charm for me.
  19. Make sure you have removed the chocks

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.