Ran into a weird one tonight.  Loaded a simbrief flight plan from PAOT to NZAA

( PAOT DCT OTZ J123 BET Q59 CDB DCT ZOULU A331 ZIGIE V7 JOELE V12 HNL V4 BINJO DCT CHOKO B326 ATIBA B590 VLI R599 DUGAN NZAA)

then added a bunch of stepclimb information to it.  

FL STEPS PAOT/0300/OME/0290/CDB/0300/ZOULU/0320/ZIGIE/0330 JOELE/0340/NIXAM/0360/ATIBA/0370/KAPNO/0380/VLI/0370 NONON/0390

Got a few warnings about altitude restrictions that I told it to ignore, then went to validate the plan and every time it zeros out the flight plan.  I see the following error in the logs:

ucFltPln ValidateCurrentFltPlan Started
Error in BuildFPRoute
System.InvalidOperationException: Nullable object must have a value.
   at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
   at P2A_2020.FltPlan.CalcEnrouteSpeedsAndAltitudesAndRemoveTOD()
   at P2A_2020.FltPlan.BuildFPRoute(Boolean CalcTOD)
 GPS FlightPlan Changed - 12/24/2020 22:46:44
ucFltPln ValidateCurrentFltPlan Done

My guess is I found a glitch with stepclimb data conflicting with Time of Descent waypoints or something.  

 

P2A does not currently support entering a step climb and then have ATC follow it.  The way to do this currently would be to validate and file the flight plan with the lowest of your desired altitudes, FL290 in this case, as your cruise altitude.  Then when you want to step up, request a new altitude from ATC.

Regards,

Dave

Thanks.  Will do that next time.