SkyMarshal

Erm. Heads up, Yemo: the game just crashed on me when a vessel underwent rapid unplanned disassembly... and a barometer was the last thing to fly off. Methinks a massless object on its own crashed the physics system.

Any specific way code contributions should be handled?

Out of curiosity, is there any chance of setting up github repositories for these? I'd love to help out.

I greatly dislike blizzy's toolbar :/ I'm going to reinstall the OS on this machine tomorrow (or saturday) and then I should be good to go. (This is the only way to get rid of the bloody Visual Studio ......... I spent about 4 hours yesterday hunting down false leads.)

I was intending to poke around and see if we can make the button only show up in the Space Center (for configuration) and just pop up the UI when a docking port is targeted... but Visual Studio is a monster and the VS2013 trial I grabbed waaaay back can't even be uninstalled (and prevents the installation of the community version)... so it'll be a while before I can contribute.

Doesn't help much when re-entering, sadly.

I guess I'll report this here as I don't really see an issue tracker anywhere: SETI - Community Tech Tree sets the masses of the thermometer and the barometer to zero... which, in Squad's especially derpy Deadly Reentry knockoff, results in a near-zero thermal mass. They explode when hit with a lukewarm fart :/ (For some reason, the barometer seems more volatile than the thermometer)

Not sure if this's been reported (if there's an issue tracker, I cannot find it) but the "Invalid value length for Vector3" error in the log (for reference, I am running v1.1.0.6 on KSP 1.0.4 on Win7 x64) can be fixed by changing line 86 of the "US_1C10_Wedge_Quadcore.cfg" file (in the ModuleJettison for "fairing_nodeX") from "jettisonDirection = 0 0" to "jettisonDirection = 0 0 1".

Out of curiosity, how do you handle code submissions?

Assuming this can be marked 1.0.4 compatible on CKAN?

Is it safe to assume this to be 1.0.4 compatible?

I'll mark it as 1.0.4 compatible on CKAN, then. Thanks for all the hard work!

CKAN got confused due to some overly promiscuous compatibility tags. Should be fixed. Is the latest version 1.0.4 compatible?

Just curious, but as Nertea handled the update just by stating the existing Community Tech Tree is 1.0.4 compatible, is the SETI-CTT mod for 1.0.2 also 1.0.4 compatible?

This is probably related to the issue the nuclear spaceplane ran into, but the suicide burn information for nuclear powered vessels is... totally wrong. I pancake'd poor Jeb into the Mun twice before I realised what was happening.