ClF3

Care to share that list? I've played KSP about a year ago and trying to get back in, but kinda lost in the options (especially now that i'm discovering that not all mods have their 1.2 updates yet)

Just ran into another problem: while having science monitor open, KSP was complaining (in the debug log) about a sharing violation on persistent.sfs. Closing science monitor resolved that issue.

I've noticed a few times that after hitting the confirm button in the tracking station, another one immediately popped up. I'm not sure if that's another confirmation for the same vesselID, or if somehow KSP cycles to the next VesselID in the list and wants to nuke that one as well (I haven't ever noticed any missing ships or crews in this way). This being related to some kind of bug is of course pure speculation from my part. I've read there's a configuration option that limits the maximum amount of debris. It's set quite high by default, but you could lower that to automate these cleanup actions (of course this does rely on an accurate classification as debris by the game)

As NJP said, it could be a bug presenting itself (I've once spent most of a sunday trying to figure out a way to get a bunch of satellites launched without exploding, before I read here that it could simply be bug-related). One cause might be clipping parts, so doublecheck that you don't have anything clipping into other parts. Otherwise, pray that a future update will get the problem fixed.

Equip the screwdriver and hover over the engine. Hold the action key (default 'x') and click. I think that's how I did it when I removed some monoprop engines from a lander.

Not really related to the original topic anymore, but I'm curious: how do you actually do this? Regularly launch a vehicle to load up on the fuel and recover that to sell? Or is there another trick to getting that fuel sold?

The problem isn't in what "standard" a computer uses. The problem is in what kind of variable declaration the application does. This also reflects on storage in databases and the like. Also, simply saying 'bit 0 defines which epoch the date is in' isn't going to work either. You need to modify all the software that uses these timestamps to understand this entire concept of an epoch. When you're going about touching all the software anyway, might as well give it a proper fix and introduce a 64-bit value for timestamps (which gives 5.8x10^11 years - well beyond the expected lifetime of our sun)

If you need another example, I can send you mine tonight. Just let me know

Actually more like the year 2038 of the KSP universe (somewhere in 2038 the unix time stamp runs out of positions - the number of seconds since 1970-01-01)

Send a Flotilla to Duna! http://forum.kerbalspaceprogram.com/threads/70026-Flotillas-A-Primer-in-3-Chapters

Don't count on Amazon removing it (unless perhaps if Squad files a complaint). It's been up there since late May already...

Cool tool! It throws me an error as soon as I open my persistent.sfs though. I can click continue and it seems to work ok but the Refresh and Statistics menu options are greyed out. Windows 8.1 (fully updated) See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ObjectDisposedException: Cannot access a disposed object. Object name: 'RichTextBox'. at System.Windows.Forms.Control.CreateHandle() at System.Windows.Forms.TextBoxBase.CreateHandle() at System.Windows.Forms.Control.get_Handle() at System.Windows.Forms.RichTextBox.get_TextLength() at System.Windows.Forms.TextBoxBase.AdjustSelectionStartAndEnd(Int32 selStart, Int32 selLength, Int32& start, Int32& end, Int32 textLen) at System.Windows.Forms.TextBoxBase.GetSelectionStartAndLength(Int32& start, Int32& length) at System.Windows.Forms.TextBoxBase.AppendText(String text) at KerbalScienceMonitor.mainForm.kerbalParseScience() at KerbalScienceMonitor.mainForm.kerbalLoadData(String s_filename) at KerbalScienceMonitor.mainForm.menuItemOpen_Click(Object sender, EventArgs e) at System.Windows.Forms.Command.Invoke() at System.Windows.Forms.Control.WmCommand(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- KerbalScienceMonitor Assembly Version: 0.1.0.0 Win32 Version: 0.1.0.0 CodeBase: file:///C:/Users/andre/Downloads/ksp/KerbalScienceMonitor_v0.2/KerbalScienceMonitor.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34250 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

I've actually seen cases where radiators actually amplified the issue. One rocket that was exploding shortly after reaching orbit suddenly started (partially) exploding on the launchpad after I put some rads on. In another case, I had a part with rads connected suddenly explode in low orbit, removing the rads resulted in a stable situation (or rather, the problem exhibited itself a while later)

So it looks like Jebretary may have messed up for me big time. It appears to have reverted my entire save including the git repository to a state 4 days ago. No clue how or why it happened, but from what I'm seeing, Jebretary appears to be the only thing that could have caused this. Basically, what I did was add a comment to my latest persistent file, then start up KSP. When I loaded my career save, I noticed the science amount listed was much lower than I remember from last night and sure enough, I was back to several days ago. Checking Jebretary showed the last quicksave and persistent save all around that time and nothing since (except for two persistent updates that have been created while i was clicking around to check on the state of things). My Ships directory has also been reverted to presumably around that same time. Since there's still KAC saves sitting in my career directory, I think it's safe to rule out any kind of filesystem issues (and also, thanks to KAC, I ended up losing only 4 or 5 hours of play) I have a zip of my save directory, if there's any interest in attempting to do a post-mortem to see what may have caused this issue.

If you have the cash, upgrade the building so you can have more active contracts. Then you can pick up the rescue contracts and stow them away until a convenient time (or combo with another contract) and still progress through some more exploration stuff