Detailed steps to reproduce the issue encountered:
start an intermediate leg (second, third leg) of any bushtrip. Check your active route and next cap and waypoint. It will always be USR01, even if your actual leg is from … USR15 to USR25 for example.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
1.32.7.0
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
A workaround is to use the Direct To function to set the first waypoint. The 2nd & subsequent waypoints then work as expected.
In the Germany Coasts trip, if you select Continue after completing a leg there is no waypoint & the map display does not show the flight plan.
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
The sim does not appear to save the user’s flight parameters at the end of each leg.
Each leg appears uses the same .flt plan - e.g. dach2a-germany.FLT - with just the aircraft position changed, based on the files in the SimStates folder - e.g. StartPos_Leg2.flt, StartPos_Leg3.flt, etc. Since a single .PLN file is also always used, the 1st waypoint for the leg is always for Waypoint 1 in Leg 1.
Ideally, the users position & aircraft state - including the current waypoint setting - would be saved & used as the basis for the next leg of the flight.
This observation is true for all three bush flights included in World Update 18.
If relevant, provide additional screenshots/video:
The problem has existed since SU5 and has also been mentioned several times in this forum. It is due to the fact that the GPS course data is not saved correctly in the cloud after completing a leg. However, there is a way to work around the error. Please have a look here: Help and Support (en-US) This is not the solution to the problem. It is a bug in the MSFS system, which unfortunately has not yet been fixed.
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template: