In my case, only 3rd-party bush trips (speak FS Academy VFR and IFR products) have been reset. I did the US California bush trip and that was marked 100%.
Same here. I have finished the patagonian one and the balkan tour. But only my current progress on the nevada tour seems to have been saved. I have also lost all my landing challenges progress.
I was halfway the Patagonia Bushtrip, installed sim update 5, and the progress is back to 0% (oddly, my progress in the Balkans is still about 50%). The trip restarted where I left it, in leg 8, but the waypoints were all gone, and the GPS pointed back to Tierra del Fuego (hundreds of NM away at this stage). I still made it to El Calafate where leg 8 finishes (but crash landed ). Now when I enter the bushtrip I’m back on Tierra del Fuego (leg 1). I don’t want to reflight that many hours because of a bug…
My bush trips (denmark 83%, sweden 80%) were correctly taken to SU5, but I can fly the last leg as often as I want (getting the leg completed screen) but I do not get the 100% of the trip. So no way to complete them
was able to complete the trip by starting it again from first leg. It is then possible to get to the leg you want to do by activating developer mode, opening teleport windows and teleport to the destination of first leg. wait a few seconds till it counts as finished and continue with teleporting to the second destination and so on. Was able to finish the first legs in about a minute.
Lost all my bush trips?
I completed all but but not the from the wold update 6.
Now doing the Germany Bush Trip but problems intermittent with the Bonanza?
One leg you can set altitude the next leg no altitude setting the next leg no heading setting next leg all is working?
All bush trips completed prior to SU5 were reset to 0% for me. I can fly the first leg with the POI and nav showing, however as soon as I go to the second nothing is shown in the map or coordinates (recall seeing this in another topic). Exploring the world through bush trips was one of the joys of the sim, and now that’s gone.
Really hope this can be formally logged and fixed in the next update.