Deovandski

I found a workaround which consists of changing the orbit of the problematic vessel followed by switching to another vessel that existed before the second stage deployment. Then, use the timewarp as you can only return to the problematic vessel after its current altitude is higher than its previous apoapsis. It seems that this combo somehow forces the changes in orbit to be saved with the best part being that all further changes are saved without any issue.

Hello, my fellow space travelers! I come here today to ask for assistance as somehow my modded KSP 1.1.2 x64 is having issues when updating the orbits into the persistent.sfs. However, All other values do seem to be updating as normal, and combing through the logs did not give me a substantial clue into what is going on... This issue started after a certain point of launching a specific vessel "Maxplorer I" which is included below. The vessel itself resembles a Falcon9 style where the first stage returns while the second stage payload goes its own way. Saving seems to work as expected for launch, LKO of the entire vessel, separation, return and recovery of the first stage, but then the issue happens when attempting to change the orbit of one of the Probes (Second Stage of Maxplorer I consists of two of them.) You can see the Steps for Issue Reproduction (Video) which starts right after I "safely" recover the first stage, and move into both of the probes to change their orbit out of LKO without success. I saw one or two unhandled exceptions from Mechjeb, but I don't have enough evidence to blame it as I used it for quite a handful of other missions before without triggering this issue... Save + Log Current Mods (All up-to-date as of 6/18): Installed through CKAN (CKAN mod list): "Chatterer", 0.9.8 "CrowdSourcedFlags", 1.50.5 "EnvironmentalVisualEnhancements-HR", 2:EVE-1.1-2-1 "ColorCodedCans", 1.4.8 "OrbitalDecay", 1.5.1 "FirespitterCore", 7.2.4 "WiderContractsApp", 1.3.3 "KSP-AVC", 1.1.6.1 "LSPFlags", 2.0 "WaypointManager", 2.5.2 "DistantObject", 1.7.1 "MechJeb2-dev", 2.5.7.0-596 "InterstellarFuelSwitch-Core", 2.0.7 "AstronikiSunflareforScatterer", 1.1 "CommunityResourcePack", 0.5.2.0 "NavUtilities", 0.6.1 "xScience", 4.18 "CanadianFlags", 1.0 "KerbalPlanetaryBaseSystems", 1.1.1 "ModuleManager", 2.6.25 "KerbalAlarmClock", 3.6.3.0 "KAS", 0.5.8.0 "DistantObject-default", 1.7.1 "FirespitterResourcesConfig", 7.2.4 "SCANsat", 16.1 "RasterPropMonitor-Core", 1:0.26.0 "KIS", 1.2.11.0 "RasterPropMonitor", 1:0.26.0 "DMagicOrbitalScience", 1.3 "EnvironmentalVisualEnhancements" 2:EVE-1.1-2-1 "FuelTanksPlus", 1.10 "Scatterer", 2:0.0246 "TextureReplacer", 2.4.13 "AviationLights", 3.9 "SAVE", 1.3.1-1999 "TweakScale", 2.2.12 Not installed through CKAN: "KSP-players", 23.1.1 Let me know if there are any further resources that I should make available in order to find the root cause. Regards Deo

It would be interesting to see a Kerbal to suddenly pop during an overheat event and a green kerbal sized popcorn (represented as a debris) replace him/her... Perhaps adding this somewhat before a kerbal pop would be an interesting in-game warning.

Well, this approach definitely goes well with the stock notification. However, during a vessel launch I believe that a similar AppLauncher notification like the one implemented on the ScienceAlert mod would be a quicker method in notifying the user that something went kerbalistic...

I did not see anything similar, so I would like to request a mod that informs the user when a building has been destroyed by having warnings displayed through the AppLauncher (show in red.) This mod would be most useful while on the process of putting a vessel in orbit, especially after 30km for scenarios where the vessel only starts gaining surface speed late in the launch process (which is often happening to me in the 1.0.2) Such warning could simply be a change in the displayed icon so that it is not intrusive .