May 25, 20224 yr Has anyone else noticed that the plane does not respect the FMC flight plan altitude restrictions when descending in VNAV mode? 7950X3D | RTX 4090 | 64GB DDR5
May 25, 20224 yr Yes, and I've also found it to be VERY lazy about airspeed restrictions in some cases. i7-6700k • Gigabyte GA-Z170X-UD5 • 32GB DDR4 2666 • EVGA FTW ULTRA RTX3080 12GB
May 25, 20224 yr Yes, I have noticed this as well. Really waiting on that updated LNAV and VNAV logic. MSFS 2024. Primary Planes: Black Square TBM850, Duke, Baron, Caravan; A2A Comanche; FSReborn Phenom; Fexix A321; PMDG 737-7, 777: Utilities: Active Sky (Passive Mode); BATC, FSLTL.
May 25, 20224 yr 33 minutes ago, Cpt_Piett said: Has anyone else noticed that the plane does not respect the FMC flight plan altitude restrictions when descending in VNAV mode? Yup, it either misses them too high or decides it needs to get down to the next restriction miles and miles away resulting in a staircase descent.
May 25, 20224 yr Author It seems very buggy at the moment. Doing some testing between VHHH and VMMC. Descending on the STAR it didn't meet the restrictions. There was a restriction at 11,000ft and I had set the target altitude for 3000ft. It completely disregarded the 11,000ft restriction. I did a touch and go at Macau then tried to reconfigure for an approach into Hong Kong Intl. As I was setting up for new destination in the RTE page, then tried to select a new STAR and APPR in the DEP/ARR page, everything just froze. FMC is completely unresponsive. I cannot change the heading (or anything else on the MCP). Also I cannot change NAV frequencies. The plane keeps flying, but... I'd expect better than this at $69.99... 7950X3D | RTX 4090 | 64GB DDR5
May 25, 20224 yr 15 minutes ago, Cpt_Piett said: It seems very buggy at the moment. Doing some testing between VHHH and VMMC. Descending on the STAR it didn't meet the restrictions. There was a restriction at 11,000ft and I had set the target altitude for 3000ft. It completely disregarded the 11,000ft restriction. I did a touch and go at Macau then tried to reconfigure for an approach into Hong Kong Intl. As I was setting up for new destination in the RTE page, then tried to select a new STAR and APPR in the DEP/ARR page, everything just froze. FMC is completely unresponsive. I cannot change the heading (or anything else on the MCP). Also I cannot change NAV frequencies. The plane keeps flying, but... I'd expect better than this at $69.99... Make sure it's not paused at top of descent
May 25, 20224 yr I haven't observed this problem so far. So long as one is in VNAV mode, altitude restrictions should be obeyed unless one has pressed the ALT INTV button on descent. Also what are the FMA indications during descent? John Wiesenfeld KPBI | FAA PPL/SEL/IFR in a galaxy long ago and far away | VATSIM PILOT P2 i7-11700K, 32 GB DDR4 3.6 GHz, MSI RTX 3070ti, Dell 4K monitor
May 25, 20224 yr Author I was descending in VNAV and LNAV, didn’t use ALT or SPD intervene. 7950X3D | RTX 4090 | 64GB DDR5
May 25, 20224 yr Just now, Cpt_Piett said: I was descending in VNAV and LNAV, didn’t use ALT or SPD intervene. Did they change the VNAV code for the MSFS version? I was under the impression it was the same code, which would be strange since I've flown the NGXu in P3D a lot and don't recall ever having seen it bust a restriction. VNAV PATH or SPD? Was that a hard restriction or maybe a below restriction? Edited May 25, 20224 yr by threegreen
May 25, 20224 yr Author VNAV PTH IICR. I didn’t make any changes in the FMC. I’ll do more testing to see if it was an isolated incident or if it persists. Edited May 25, 20224 yr by Cpt_Piett 7950X3D | RTX 4090 | 64GB DDR5
May 25, 20224 yr 2 hours ago, somiller said: Yes, and I've also found it to be VERY lazy about airspeed restrictions in some cases. Hard waypoint restrictions or target speed? Because in VNAV PATH there is a certain margin (10 or 15 kts, selectable in the FMC) that the aircraft will accept below or above the target speed. Also when the A/T is in arm mode you have to manually adjust thrust as needed until it goes back into FMC SPD or another speed mode.
May 25, 20224 yr Author 1 hour ago, threegreen said: Hard waypoint restrictions or target speed? Because in VNAV PATH there is a certain margin (10 or 15 kts, selectable in the FMC) that the aircraft will accept below or above the target speed. Also when the A/T is in arm mode you have to manually adjust thrust as needed until it goes back into FMC SPD or another speed mode. It disregarded the restriction at HAZEL and continued descending to the set altitude of 3000ft. 7950X3D | RTX 4090 | 64GB DDR5
May 25, 20224 yr 11 minutes ago, Cpt_Piett said: It disregarded the restriction at HAZEL and continued descending to the set altitude of 3000ft. FMC navdata base updated to the current cycle I guess? Edited May 25, 20224 yr by threegreen
May 25, 20224 yr Haven't seen that. It undershoots ALT sometimes by a couple of 100fts, but I've never seen it ignore restrictions. I'd say it's a GIGO error, probably old/faulty navdata. Did you double check charts vs FMC? However since it's generally buggy for you (frozen cockpit), I'd say it's probably something else. Better open a ticket. For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
Archived
This topic is now archived and is closed to further replies.