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.

FBW A320NX - EXP version has VNAV!

Featured Replies

Yeah I had that too, I am too high at the IAF. I think it might be that speed constraints are not considered appropriately for the calculation of the TOD, or that the flight model is too slippery. I am sure that will eventually get fixed.

For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.

  • Replies 68
  • Views 15.1k
  • Created
  • Last Reply
7 hours ago, captain420 said:

Did a short flight from RJAA to RJBB and also faced the same problem. Did a managed descent and was way too high. I have no problems with the dev version without VNAV being implemented. I thought VNAV was suppose to take me down automatically while obeying constraints? I am starting my descent about 120-160 miles out too. So should be plenty of time for the plane to come down.

I was having this same problem, but when I watched the Easyjetsimpilot video tutorial I noticed that removing the + sign before altitudes, on the mcdu flight plan page.
  example: +8000 and leaving only altitude 8000 without the + sign, the aircraft started to obey the restrictions.

google translator translation.

lol

Edited by Ricardo Andrada

Same problem here, the VNAV starts the descent far too late and you end up way high for the approach. 

Mark   CYYZ      

 

3 hours ago, Ricardo Andrada said:

I was having this same problem, but when I watched the Easyjetsimpilot video tutorial I noticed that removing the + sign before altitudes, on the mcdu flight plan page.
  example: +8000 and leaving only altitude 8000 without the + sign, the aircraft started to obey the restrictions.

google translator translation.

lol

How do you edit the constraints? 

I’ve tried several flights since the implementation of vnav, and several times I’m left way high at IAF.  I still monitor the descent closely using the TOD calculator. Usually I’ve started descent a while before the calculated vnav. I’m also in the habit of programming a hold (or two) during the approach, as more often than not I’m too high.

7950X3D | RTX 4090 | 64GB DDR5

320 Sim Pilot just released a video on VNAV:

Edit (from the video above): managed desc (in this early implementation of vnav) does not take into account speed changes. Which certainly could explain the issue of ending up too high. 
Another limitation at the moment (which I guess is related to the above) seems to be that the flight plan can be incorrect as it initially reflects current speed. Hence the FBW mod will not display the flight plan as it should be in the ND. Instead it seems to add vectors, increasing the length of the plan, which affects the TOD.

Edited by Cpt_Piett

7950X3D | RTX 4090 | 64GB DDR5

2 hours ago, Cpt_Piett said:

320 Sim Pilot just released a video on VNAV:

Edit (from the video above): managed desc (in this early implementation of vnav) does not take into account speed changes. Which certainly could explain the issue of ending up too high. 
Another limitation at the moment (which I guess is related to the above) seems to be that the flight plan can be incorrect as it initially reflects current speed. Hence the FBW mod will not display the flight plan as it should be in the ND. Instead it seems to add vectors, increasing the length of the plan, which affects the TOD.

By "speed changes" does he mean "speed restrictions" or manual speed changes with the knob on the glareshield?

For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.

12 minutes ago, Fiorentoni said:

By "speed changes" does he mean "speed restrictions" or manual speed changes with the knob on the glareshield?

Good point. I think both. Ie an early (above 10000ft) speed restriction in the flight plan. But also the fact that the flight plan is computed based on the current speed and not the expected approach speed. But it’s still early days and I guess things will become clearer in time.

7950X3D | RTX 4090 | 64GB DDR5

3 hours ago, Cpt_Piett said:

Como você edita as restrições? 

Eu tentei vários voos desde a implementação do vnav, e várias vezes fiquei muito alto na IAF. Eu ainda monitoro a descida de perto usando a calculadora TOD. Normalmente eu comecei a descer um pouco antes do vnav calculado. Também tenho o hábito de programar uma espera (ou duas) durante a abordagem, pois na maioria das vezes estou muito alto.

51964494186_c98b48af5a_c.jpg

51964776489_4b20bb6d3b_z.jpg

51964776469_1845d53530_z.jpg

 

 

I made this sequence of photos, I hope it can help you.

Archived

This topic is now archived and is closed to further replies.

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.