NO VPATH CONDITION - OMDB VUTE3B STAR

[TCAS_RA]

Bringing this in from the Discord, as promised.  Appears that FMS is stuggling with maintaining VPATH on the unique OMDB STARs.  Using VUTE3B here as the example.  These "switch-back" type arrivals are causing reversion to VPTCH with NO VPATH CONDITION message in FMS when there is a descent in progress.  In this example, the TOD  is between DB425 and DB421 to meet the altitude constraint at DB421.  I have not flown CL60 into OMDB but other similar platform, irl, I don't recall seeing these reversions.  Once the aircraft is established in the descent after DB425, there is no more vertical discontinuity during the turn anticpation for DB421.  Should be able to maintain the VPATH for DB421?  Maybe worth a look.

Flyability is still nice as the VPTCH transitions back to VPATH passing the bisector of the turn and rollout on the next segment, without pilot intervention.  At least in these conditions.    

 

VUTEB Log.txt state.bin

[TCAS_RA]

Tried to attach the video, but the file is too large, apparently.  Hopefully this is enough with the Log file and State file to have a look in the development laboratory!