question

Hello, I've been doing some testing of my bushtrip and discovered that it appears that a rather large number of changes have been made to the bushtrip ecosystem in MSFS. Below I will add my findings and implications some of the changes have made.

1. The time is no longer reversed at the end of leg. Previously, the time would revert to exact moment the leg started, making each leg start at the same time. Now next leg starts when previous ended. In some scenarios this will force people to fly in pitch dark night, making landing on smaller airports or airstrips virtually impossible.
2. The bushtrip template inside documentation is incorrect. Here are the flow events from INTRO flow state provided in the template:
   

   XML

   <StartFlowEvents>
     <FlowEvent id="UNACTIVATE_PUSHBACK"/>
     <FlowEvent id="UNPAUSE_SIM"/>
     <FlowEvent id="PANEL_COPILOT_FORCE_DISABLED"></FlowEvent>
   </StartFlowEvents>

   If such values are used in bushtrip the mission starts with menu like "Travel To" enabled, plus a bunch of other ones, including Objectives panel opening automatically at start. The values used to be:
   

   XML

   <StartFlowEvents>
     <FlowEvent id="UNACTIVATE_PUSHBACK"/>
     <FlowEvent id="UNPAUSE_SIM"/>
     <FlowEvent id="PANEL_COPILOT_FORCE_DISABLED"/>
     <FlowEvent id="PANEL_CHECKLIST_FORCE_DISABLED"/>
     <FlowEvent id="PANEL_FUEL_PAYLOAD_FORCE_DISABLED"/>
     <FlowEvent id="PANEL_TELEPORT_FORCE_DISABLED"/>
     <FlowEvent id="PANEL_OBJECTIVES_FORCE_DISABLED"/>
   </StartFlowEvents>

   and above are the ones that should actually be used by people to ensure a proper mission is created.
3. When bushtrip is continued, the FUEL_PAYLOAD panel is never disabled. That's a weird one which definitely worked before. Either the out of fuel calculator is not working or something else is causing the fuel panel to be constantly visible even after take off.

From my perspective it looks like the states at the end of bushtrip legs are currently behaving incorrectly. Either something is not being triggered or state definitions have changed. Below snippet worked before:

XML

<SimMission.FlowStateAction InstanceId="{81E4FFFD-1D53-40C5-A13E-932466A4B998}">
  <FlowStateName>LANDING_REST</FlowStateName>
  <AutoStateSwitchEnabled>False</AutoStateSwitchEnabled>
  <StartActions>
    <ObjectReference InstanceId="{3FD4EC3E-1F13-42D5-8D97-5A6F28FAFDC8}" id="REFUEL_ACTION"/>
    <ObjectReference InstanceId="{6FC29791-E22E-4FB4-8280-BB5425EB3FEB}" id="REFUEL_NOTIFY_TRIGGER"/>
    <ObjectReference id="RTC_Ground_Aircraft_Outro" InstanceId="{5DAADB19-3BA3-4235-BCC0-39CD6F4CD4D9}"/>
  </StartActions>
  <NextState id="BUSHTRIP" InstanceId="{23552DE7-1761-4299-93D1-012CFA6CF761}"/>
</SimMission.FlowStateAction>

At the moment the refuel action can be triggered, however the dialog will not show up (I moved the dialog to airport landing calculator). I have noticed all these changes and problems when new "end of the leg/bushtrip" menu was introduced. Think this might have been around Xbox update. I will be grateful for any information about changes to bushtrips and any dates when further updates/changes are planned.