Hi,
It happens to me as well sometimes to be on VNAV and suddenly it goes PITCH HOLD without any obvious reason.
May be it is due to some AIRAC problems. I do not know.
LNAV/VNAV do not behave always as expected as I mentioned in another post today (EICK STARS).
Regarding YCFS I did not have any particular problems there.
I am using Win7 - Majestic Q400 PRO - Prepar3dv4.5 - Latest patches and AIRACS.
We'll see if we could get some answers.
Regards,
JP
Hi,
When descending ENROUTE with VNAV it works quite well even that most of the time I use VS to have it more stable (avoiding ups and downs too quickly and most uncomfortable).
It is when using VNAV/LNAV that I sometimes encounter problems. If possible, there as well I would prefer to descend following the LNAV with VS. A full GNSS for the LPV would be nice giving better minima.
JP
The following info on VNAV limitations might be useful
If the runway is not on approach path (offset path), one can not use the FMS 3D approach for the final approach leg. Either one should switch to the ILS, or fly the leg visually
Often (same as in the real FMS) when transitioning through FAF, VNAV will disengage to make sure pilots are aware that either it must be re-engaged with re-set accordingly, or the source must be switched to ILS for the ILS approach
VNAV Path will disconnect if it encounters a restricted leg type. Restricted legs are (for example) Course to Fix, Heading or Course to intercept, Course to DME
Hi,
I have the same issue on p3d v5. I think the problem is after last update. Before that it was ok.
VNAV armed correctly, and switching to pitch hold on every waypoint. It looks like some kind of a VS calculation problem. When VNAV is set properly, a/c is starting to descending iaw. VNAV PATH. Then on next waypoint VNAV is switching off and PITCH HOLD is set. But the VNAV page in FMS showing vertical deviation (under path). That looks like the FMS ic calculating something wrongly.
Comments
Hi, All.
I have a same problem.
and found the video which made by other person.
https://youtube.com/watch?v=pwGhhw_FqkI
Hi,
It happens to me as well sometimes to be on VNAV and suddenly it goes PITCH HOLD without any obvious reason.
May be it is due to some AIRAC problems. I do not know.
LNAV/VNAV do not behave always as expected as I mentioned in another post today (EICK STARS).
Regarding YCFS I did not have any particular problems there.
I am using Win7 - Majestic Q400 PRO - Prepar3dv4.5 - Latest patches and AIRACS.
We'll see if we could get some answers.
Regards,
JP
JP, Which did you use VNAV TO or VNAV ENROUTE.
After I experienced the problem with VNAV TO, I tested VNAV ENROUTE function.
Then It seemed to work correctly.
Is it problem of VNAV TO function?
Please test it.
Thanks.
Hi,
When descending ENROUTE with VNAV it works quite well even that most of the time I use VS to have it more stable (avoiding ups and downs too quickly and most uncomfortable).
It is when using VNAV/LNAV that I sometimes encounter problems. If possible, there as well I would prefer to descend following the LNAV with VS. A full GNSS for the LPV would be nice giving better minima.
JP
The following info on VNAV limitations might be useful
If the runway is not on approach path (offset path), one can not use the FMS 3D approach for the final approach leg. Either one should switch to the ILS, or fly the leg visually
Often (same as in the real FMS) when transitioning through FAF, VNAV will disengage to make sure pilots are aware that either it must be re-engaged with re-set accordingly, or the source must be switched to ILS for the ILS approach
VNAV Path will disconnect if it encounters a restricted leg type. Restricted legs are (for example) Course to Fix, Heading or Course to intercept, Course to DME
Thanks Boss,
It explains everything especially:
2. as you mentioned "often" and you are right it is not all the time.
Regards,
JP
Hi,
I have the same issue on p3d v5. I think the problem is after last update. Before that it was ok.
VNAV armed correctly, and switching to pitch hold on every waypoint. It looks like some kind of a VS calculation problem. When VNAV is set properly, a/c is starting to descending iaw. VNAV PATH. Then on next waypoint VNAV is switching off and PITCH HOLD is set. But the VNAV page in FMS showing vertical deviation (under path). That looks like the FMS ic calculating something wrongly.