Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

103 Excellent

About Donstim

  • Rank

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you have the New Lights light enhancement mod, you will need to uninstall it. It is incompatible with the FBW A32NX and causes this behavior.
  2. We published such validation quite some time ago for the FBW A32NX flight model....https://flybywiresim.com/notams/a32nx-flight-model/
  3. The stable version does not have full vertical descent management (VNAV). It will attempt to obey any altitude constraints, but will do so by flying an open descent to reach them. An open descent uses idle thrust and adjusts pitch to stay on the target airspeed. Thus, it will give you the highest descent rate for the configuration you're in that maintains the target airspeed and will generally reach the constraint altitude early. Depending on your weight, the descent rate can easily reach 4-5,000 fpm in the early part of the descent if you are light. Similarly, in climb, the airplane can achieve 5,0000 fpm initial climb rates if you are light (for example, 60T or less)
  4. I hope there are no trademark issues with the IRL EFB-Pro.
  5. From the FlyByWire documentation: FlyByWire A32NX | Assistance Options The A32NX is not compatible with the Microsoft Flight Simulator assistance feature "Auto-Rudder". It is required to deactivate this feature in MSFS. We recommend turning off all assistance features in MSFS as they interfere with the A32NX systems.
  6. Hi, just wanted to follow up with you on this. I see that there was an issue identified last year about this time citing an unrealistically high glide ratio (26:1) for the A32NX: https://github.com/flybywiresim/a32nx/issues/3322. Does this sound similar to what you were experiencing? There have been several flight model updates since then, the most recent being about a month ago. A Google search for A320 glide ratio shows several research studies (e.g., https://www.researchgate.net/publication/279217100_Is_Green_Dot_Always_the_Optimum_Engines-Out_Glide_Speed_on_the_Airbus_A320_Aircraft) based on a clean glide ratio of 17:1, and a full flap, gear down landing configuration glide ratio of 9:1. The Airbus FCOM gives a descent rate of 2.5 NM/1000 ft (glide ratio of 15:1) with all-engines-inoperative at green dot speed clean. The landing procedure for all-engines-inoperative is to use CONF 2. In this configuration with gear down, the FCOM provides a descent rate of 1.6 NM/1000 ft (glide ratio of 9.7:1). Tests at 60T with the FBW A32NX provided the following results: Clean at Green dot speed: 3.2 NM/1000 ft (glide ratio of 19.4:1) CONF 2/gear down at 163 KCAS: 1.5 NM/1000 ft (glide ratio of 9.1:1) CONF FULL/gear down at Vref+10: 1.4 NM/1000 ft (glide ratio of 8.5:1)
  7. Yeah, that doesn't sound right. I assume your airplane is up-to-date? Just want to also note that spoiler deployment is inhibited in CONF FULL and only about 1/2 extended in other configs with autopilot on. Was the airplane fully configured before cutting fuel to to the engines? What speed were you trying to maintain? If neither engine is producing thrust, then it isn't a matter of weight, only L/D. I will be glad to give this a check as it is well outside the normal envelope and not covered by the available data, but I'm out of town until Sunday.
  8. Flight performance, including with flaps and spoilers extended, gear down, engines at idle match the real airplane very well. https://flybywiresim.com/notams/a32nx-flight-model/ Oh, and engine - out performance is modeled as well, so you can practice your V1 cuts.
  9. Regarding the earlier discussion on setting pitch trim for takeoff, see https://docs.flybywiresim.com/pilots-corner/beginner-guide/preparing-mcdu/#perf and the "setting pitch trim advice" here: https://docs.flybywiresim.com/pilots-corner/beginner-guide/engine-start-taxi/#after-engine-start. For the vertical guidance symbols, see https://docs.flybywiresim.com/pilots-corner/advanced-guides/flight-guidance/vertical-guidance/nd-symbols/?h=sym There is a wealth of information in the Fly-By-Wire documentation. You may want to start here - https://docs.flybywiresim.com/pilots-corner/beginner-guide/overview/
  10. Yes, just enter a From/To pair in the Init A page. It can be the same From/To pair that you had before.
  11. Have you followed the guide? https://docs.flybywiresim.com/pilots-corner/beginner-guide/engine-start-taxi/#engine-start In addition to the engine mode selector being set to IGN/START, you need the APU available and APU BLEED on .
  12. See if this helps...https://docs.flybywiresim.com/fbw-a32nx/support/reported-issues/#remove-old-marketplace-installation
  13. Wish you had tried it with the FBW. Would have been interested in how it did.
  14. No, this video does not show how to fix floaty planes. It shows how to fix a bug that was introduced in one of the early sim updates that was fixed fairly quickly by Asobo.
  15. Yes, that's FBW. That video was made by just using the Windows 10 Xbox Game Bar function. You can enable it by going to Windows settings, Gaming, and turning on the Xbox Game bar. You can then start recording by simultaneously pressing the Windows key, Alt, and R. Or to get more features, you can download and use something like OBS Studio. It's free and open source. https://obsproject.com/
  • Create New...