As a bush trip creator I do many changes on the trip while developing. So the
main question is: How to delete a save-mission with SU10? I.e. I start at
Airport A, flow several WP and come to a stop at Airport B. I detect, Airport
A was a bad idea and change it to Airport A1. There is now no chance to start
the mission at Airport A1. When starting the leg, it shows in the activity
screen and briefing screen the Airport A1, but the plane is placed on runway
of Airport A. Changing destination of a leg seams to be good (B to B1), but
needs more tests. A simple test modified activity, and briefing. Also start of
Leg 2 places the plane the Airport B1. Maybe it will be an idea to remove,
ignore or reset the cloud save when
The flightplan changes (WP/Airports) or
Any airport of the flightplan changes (ignore WP changes for reset) or
The version number of the bush trips changes (1.0.0 to 1.0.1) or
A Ingame “reset” function
any other option where the creator can delete a saved mission only
,
Before cloud save of the mission state, it was possible to delete the folder
in the localstate/missions/activities for the creator or the tool used by the
creator. I think such a possibility is also useful for the MS/Asobo bush trips
and marketplace bush trips from partners, if basic things change. (closed
airport, switching to another, see EDDT->EDDB, the LANO issue, etc.).
I can confirm the contribution of BuffyGC, since I am also creator of bush
trips. The philosophy of ASOBO is presumably that with a necessary
reinstallation successes of bush trips are not lost, which was already
discussed in some forums. But this can also be achieved by other means, for
example by asking for the backup of successes when uninstalling MSFS. However,
the storage of data in the cloud also becomes problematic for MS/ASOBO when
updates are made in the official bush trips. A reset function, as BuffyGC
suggested, would certainly be a good interim solution until a final solution
is found. A final storage in the cloud would be the final end for all
developers of bush trips to update offered trips. I don’t think this is a good
idea.
Another bush trip author here but nowhere near as important as the other two
posters here. I am also interested in how saved games once in the cloud can be
deleted as I end up doing this many times at the current local storage
location during the creation of a trip. It is not unusual for initial airports
to change once I am testing so all advice is welcome.
Hello @BuffyGC We don’t have a proper solution for
this at the moment. The only thing you can do is clear your cloud save but
you’ll lose all progress and logbook so that’s not a good option. The problem
has been forwarded to designers. Regards, Sylvain
Thanks @FlyingRaccoon for the answer. Not
really happy with this, but looking forward to get it solved later. I already
get the request from several commercial users, including the ones making the
official trips for the title. It seams, it is a bigger issue for them then
expected. In case of trigger changes, object activation, waypoint changes
there are sometimes unexpected things. When I have more information and can
reproduce their problems, I will come back to you. Thanks again, BuffyGC
Hello @BuffyGC@Koschi @ProfSC Something I’m not sure to understand. Why
isn’t restarting the mission a good alternative to deleting the cloud save?
The cloud save just stores the last waypoint index so we agree this can cause
some inconsistencies when the legs are modified. But doesn’t restarting the
mission from the beginning solves this problem without the inconvenient of
loosing the overall progression? Regards, Sylvain
Hi Sylvan, thanks for reply and looking deeper into this topic. The change of
the flightplan is exacly this issue, especially when airports are switched to
another one. I agree, it is not such “hot” as thought after the first tests
and I really like to keep the progress when applying small other changes then
major flightplan changes. And for faking a full restart with loosing progress,
I’ve already implemented a solution into BTI. I will run further tests with
changing Airports and Waypoints later the week with the restart option and
come back to you. Many thanks again and greetings to the whole team. BuffyGC .
I’ll add my thoughts to this. First, thanks for the improvements for bush
trips in SU10. I had mostly stopped flying FS2020 entirely while waiting for
SU10’s performance, reliability, and bush trip improvements. I have made and
published a few different bush trips in the past year. I’m trying to rebuild
one of them to work better with SU10’s new, more severe weather that affects
low-level, marginal weather flying. While testing, I crashed to desktop (CTD)
while flying the first leg. If I continue the first leg, FS2020 wants to
resume from where I was flying. Since it is the first leg, the closest I can
come to restarting the trip is to start flying, hit ESC, and then click
“restart”. This repositions the aircraft to the start, but I then hit another
CTD. Fortunately, I suppose, I can restart FS2020 and “continue” the bush trip
from the saved starting location. As a developer, I would like an easier
solution to reset rather than having to restart while in flight–especially if
the existing process is prone to CTDs. Thanks. Brian
Hi @FlyingRaccoon , first, all apologies for
the delay, busy times currently. Here some more feedback: When changing
waypoints and especially the start or end of the route, the flight plan does
not fit, neither in the VFR chart nor in the GPS. Several other users are
reporting issues with CTD. Just after a waypoint, a CTD appears. When re join
the mission, the time period to restart is very short, because the same CTD
appears again. When getting a restart, the mission starts at the airport, but
a CTD happens immediately again. Creating the mission in another path and with
another name with the same content to force a “new” bush trip will work then.
Maybe there is an issue with the saved file which leads to CTD or anything in
load/continue. Especially for the creators of mission wuld it a great feature
to start from scratch. But I learnd also for users it can help to reset a trip
to avoid CTDs. Thank you very much, BuffyGC
I observed a variation of this in one of my missions published on flightsim.to. (And discussed it with @BuffyGC at the
time.) It’s this mission: <https://flightsim.to/file/29399/smoky-mountains-
bush-trip> It has a long first leg, and I frequently crash after the second
touch-and-go, which is at the Knoxville airport. I could usually restart
FS2020 and resume the bush trip and continue with the rest of the leg without
crashing, but the leg would never “complete”, since restarting caused FS2020
to think I had not visited the first two mandatory waypoints. The only way to
succeed at competing the first leg was to resume and then hit ESC and restart,
or to go back and visit the mandatory WPs. So, I will add to the original
request:
Either save the completion of mandatory waypoints in the cloud, so they are remembered after a resume, or
Automatically reset or alert the user if there are mandatory waypoints in the current leg that are between the origination point and the resumption point of the saved trip
I observed a variation of this in one of my missions published on flightsim.to. (And discussed it with @BuffyGC at the
time.) It’s this mission: <https://flightsim.to/file/29399/smoky-mountains-
bush-trip> It has a long first leg, and I frequently crash after the second
touch-and-go, which is at the Knoxville airport. I could usually restart
FS2020 and resume the bush trip and continue with the rest of the leg without
crashing, but the leg would never “complete”, since restarting caused FS2020
to think I had not visited the first two mandatory waypoints. (Mandatory
waypoints in BushTripInjector are implemented with CounterTriggers and
CountActions.) The only way to succeed at competing the first leg was to
resume and then hit ESC and restart, or to go back and visit the mandatory
WPs. So, I will add to the original request:
Either save the state of Counter and other Triggers in the cloud, so they are remembered after a resume, or
Automatically reset or alert the user if there are Triggers in the current leg that might have been lost