Working-Title-MSFS-Mods / fspackages

Working Title FS Packages
MIT License
1.15k stars 109 forks source link

TOD indicated in place of FL setted #625

Closed jdeyrieux closed 3 years ago

jdeyrieux commented 3 years ago

after to add a FL to a waypoint, the plane is at this FL already, then TOD (green) is added to the MFD. FL constraint expected. image

K20017 commented 3 years ago

The CJ4 does not input any cruise altitude in the constraints or automatically fill in what the crossing altitude will be for every fix. It only shows constraints for those pulled by the nav data or pilot input. So you don't need to put FL420 in there.

jdeyrieux commented 3 years ago

I understand, my question was more precisely about : is TOD expected in this case ?

K20017 commented 3 years ago

That's probably an erroneous value as it's probably not liking the strange FL420 constraint there.

taguilo commented 3 years ago

Hi, Actually what should happen is, if you have an Arrival/Approach with altitude constraints loaded in the FMS, and you include another altitude constraint in, for example, a cruise waypoint, and VNAV is not able to comply (because descent should start before arriving at that wpt), then the constraint value should display in yellow; in this case with no further info to the pilot, who needs to figure out why the yellow color. This is not modelled yet (but I guess will come later).

cwburnett commented 3 years ago

@jdeyrieux this is occurring because you have set the VNAV target altitude for your current altitude. Therefore, VNAV is determining when you'd need to begin a descent to reach FL420, which in this case is exactly the waypoint since you're already at that altitude. Remember that VNAV in this aircraft is for descent planning, not cruise altitudes, so it always takes the next constraint and evaluates when you need to begin a descent to reach that altitude at the specified flight path angle. Adding cruising altitudes as VNAV constraints will always yield this behavior.

taguilo commented 3 years ago

VNAV is both for descent and cruise. It smart detects when a wpt constraint is in the climb or the descent portion of the flight plan. The destin is 655 miles ahead so it should have detected that. Quoted from FMS3000 VNAV section: "The initial location of the TOD is at the intersection of the planned cruise altitude and the planned descent path." And "The aircraft is considered to be close to the descent path when it is 50 NM or 20 percent of the distance from origin to the destination, whichever is smaller (but not less than 6 NM)."

Hope this helps.

jdeyrieux commented 3 years ago

Thanks!