linuxgurugamer

New release, 1.9.0.2 Removed old, unused code, and code obsoleted by the ToolbarController Changed default for UseDistanceOverride from true to false, to match old behaviour Removed some unnecessary window calls Added back button on Spacecenter screen, opens window to direct people to Stock Settings pages Added option to disable the button on spacecenter scene

Apparently I made the useDistanceOverride default to active, I've fixed that in the next release which will be out later this evening. I've also put the button back on the SpaceCenter screen, but all it does is open a small dialog directing you to the stock settings pages, hopefully this will eliminate some confusion

Use Editor Extensions Redux. It can do this already

Try that and report back.

@Lisias Are you planning on updating Tweakscale to add the new 1.875m tank size?

See this: Read this BEFORE asking for support: http://forum.kerbalspaceprogram.com/index.php?/topic/83212-how-to-get-support-read-first/ Most likely something isn't in the correct place, but without a log file, that is just a guess

Ummm, read the post right above where you started. The settings page got removed and the settings are now in the stock settings page:

Did you check the settings? Please list here what the settings are. KSP kills a vessel when the pressure at the altitude of the ship is >1. Stage Recovery needs to grab the kerbals before this, so it calculates that altitude and then adds 1000. It would be possible, I suppose for a vessel to come within 1000m of the kill altitude and then go out, but highly unlikely.

True, I'll be watching with interest

Good luck. I would tend to doubt it, because boarding involves a lot of steps, including destroying the active vessel (the Kerbal), making the boarded vessel the active vessel, etc.

Does this work if the Kerbal is not the active vessel? In other words, if Kerbal runs out of monoprop while on EVA, can you switch to the vessel and pilot it to get the ladder within range?

I'm not a mind reader. Post what you have done so I can see it

Ok, I think I know what's going on. The Ships folder is being installed for all of them, I'll have to do some work to separate out the vessels.

Just because something is old doesn't mean it's obsolete. Unity is under continuous development, as other engines. Look at it this way. Let's assume that they start a total rewrite with a new engine. It's going to take several years before it is released, by which time the engine will be "old". KSP doesn't have a large enough user base to make this economically feasible at this time

And how do you know that a new engine won't have it's own issues?

Click on the Changrlog, will show you previous releases

Bob's Panic Box does exactly that

Because the game was written for it. Changing to another engine would require a complete rewrite

Maybe look at Smart Parts?

I think the question is at what Pe does ksp delete ships. I'll have to investigate that, although it does look like that OS already in there

New release, 1.9.0.1 Changed license to MIT Moved all settings into stock settings page, both to reduce code and to have the settings persist on a per-save basis Note: Existing settings are not migrated Replaced all Debug.Log with new Log.Info to reduce log spam Added code to remove events when mod is destroyed (ie: scene change)

Looking at the code, the PreRecovery happens in the following circumstances: Vessel is not the active vessel Vessel is not a Kerbal on EVA The vessel is in the home planet's SOI (ie: stock game would be Kerbin) Vessel is NOT landed Vessel is below a certain altitude (somewhere between 25,000 & 30000) Vessel is beyond a certain distance from the active vessel If someone could get me a save from before it removes Kerbals, but leaves the ship, I could get this figured out.

I've never seen that, probably because I never allowed any kerbals to be in a doomed ship. Do you have any ideas as to what might be happening? Any pattern? Regardless, it's working as it used to, so I'll release it this morning

@gamerscircle New beta, my tests showed it's working. Would appreciate you (or anyone else) taking a look and testing: https://jenkins.spacetux.net/job/M-S/job/StageRecovery/8/artifact/StageRecovery-1.9.0.1.zip Thanks

I have no problem with the legal issues. I was only commenting with regards to the etiquette. Apparently some people feel, as @Snark says, that they don't feel any need to contact an author, even if the author is still active. That, IMHO, is just plain being rude. Legal, yes, polite, apparently not. I, however, will continue to try to contact any mod author before taking over a mod. Obviously I'm spraying water into the wind over here, therefore I am going to refrain from commenting here unless something very significant happens.