Kerbal Space Program

I may have set the priority too high. It should probably be Normal or High. This does not affect the default ship. I'm not certain what part could is needed to cause this outside of this ship. I'm also not sure if it happens for other people as it's hard to find people to test this.

Here is a different ship file with some instruction on how to fly it. (located in the ships description in the VAB etc.

Instructions:
To reporduce bug:
1. After laoding turn on RCS and SAS.
2. If desired hit Abort to empty ore tanks.
3. Hit 1,2,3 to turn on main engines and max out throttle to take off.
4. Wait to hit altitude and see the ship explode.

The F3 log may or may not exist.

File:
[[https://www.dropbox.com/s/tpfqfj8d87w6uht/The%20Orion%20V4%201_1_2%20v2%20Bug%20version.craft?dl=0]] <- Same craft as in the previous entry but with the above text in the description. I forgot that this version does not have the hotkey in the description like I normally put in this vessel.

[[https://www.dropbox.com/s/5ice9vzf2bim71w/The Orion V4 1_1_2 v2 boosters.craft?dl=0]] <- boostered version (3213 parts) though it oddly gets an extra part according to the map view compared to the VAB/SPH. I think all other versions of this ship do also.

This is an unmodded ship in a fresh install. the only thing I did after the fresh install was import the save file because I have things in it I like to keep. Like an old version of this ship landed on minmus. There are only 13 flights or so in the whole save. And I only kept the ships I needed for testing this basically.

Edit: to fly the boostered version above. Don't turn on the 1,2,3 engines. Just use spacebare to activate the booster sections. If you use the engines(execpt maybe 2, which is insufficient to help regardless.) it will blow itself up with heat damage.

Arugela wrote:

[[https://www.dropbox.com/s/5ice9vzf2bim71w/The Orion V4 1_1_2 v2 boosters.craft?dl=0]] <- boostered version (3213 parts) though it oddly gets an extra part according to the map view compared to the VAB/SPH. I think all other versions of this ship do also.

This is an unmodded ship in a fresh install. the only thing I did after the fresh install was import the save file because I have things in it I like to keep. Like an old version of this ship landed on minmus. There are only 13 flights or so in the whole save. And I only kept the ships I needed for testing this basically.

Edit: to fly the boostered version above. Don't turn on the 1,2,3 engines. Just use spacebare to activate the booster sections. If you use the engines(execpt maybe 2, which is insufficient to help regardless.) it will blow itself up with heat damage.

Noted and got the craft. Checking out the V3 one with boosters atm. I notice that you've clipped things pretty heavily, which could be a cause, but if it holds on launch, it shouldn't explode in flight, right?

edit: wait, how do I launch the v3 one with boosters? I didn't see instructions for that one checks back edit2: Oh I see, it's the same as the one you posted above. Or rather the one further up, but I've got it.

To stop the explosions on runway restart the game and it should stop.

Could you test if other ships blow up on the runway after this. I think I tested it but I forget for certain if everything else does too. I wanted to recheck that. (I'll be doing the same in a few minutes when my ship explodes again.)

Edit: I finally got an F3 log on the explosion. It starts with structual linkage from the Radiator panel large I mentioned in the thread. The part I can't remove without the file becoming corrupt after saving and reloading the ship in the VAB. Maybe it is related afterall.

Post:
[[http://forum.kerbalspaceprogram.com/index.php?/topic/138905-the-orion-and-the-kraken-6000m-auto-explosion/&do=findComment&comment=2576393]]

I'm reverting back to the VAB and loading and launching a different vessel to see if it also explodes on the runway before restarting the game.

Revert to VAB from launch after bug and relaunch same ship: Explodes again.
Revert to VAB from launch after but and relaunch different(stock) ship: *Does not explode!

***I'm starting to think this has to do with that part in the other thread. there are two Large radiator panels on the nose of the ship. One or both of them removed from the ship/saved/ then reloaded will permanently corrupt the .craft file as per the other thread. This is the first part that explodes. I wonder if it is causing the issue somehow.

[[http://forum.kerbalspaceprogram.com/index.php?/topic/139421-ye-olde-file-corruption-issue/#comment-2573577]]

If looking for this use the V4 craft. The version 3 craft is it one of the top radiator panels below the neck of the ship, but it will be hard to find. In the V4 one I only have it and one copy of it directly behind the drills attached to the bottoms of the MK3 cockpits at the front of the ship. Those parts are corrupted or something.

That was a typo. I meant launchpad on that occasion. I intermix those words occasionally.

Currently trying some things. Even turning on unbreakable joints doesn't stop it from exploding on launch.

https://www.dropbox.com/s/zqnhw250iiqhmad/The Orion V4 1_1_2 v2 ParttestRedGreen.craft?dl=0

The remnants of the Orion v4 1.1.2 v2 vessel. It is down to just the offending radiator panel and two other parts. It demonstrates something the part is doing by taking the adapter part on and off. If the radiator is removed and the file saved and reloaded the file will again be corrupt!

The pics are in the forum thread about it. I can't seem to get the pics to load in this one.

[[http://forum.kerbalspaceprogram.com/index.php?/topic/138905-the-orion-and-the-kraken-6000m-auto-explosion/&do=findComment&comment=2577826]]

Solution found:
1.Find the offending part
2.use a text editor to find all references to the part(this would be the entire Part<> and all link references. Link references would likely be in the Part<> of the mother part.
3.Save file.

Note: on the smaller ship at some point gained a double link reference on the mother part to the same part. I'm not sure how this occurs but this showed that the part reference was screwing up on any attempt to remove it. I believe claw was referring to this in the main thread. After realizing that the mother part also had references to the part I removed them along with the part<> entry itself.(I was previously unaware of the link reference on the part it was attached and had attempted to only remove the Part<> section of the part causing the error to persist even after attempting to remove it simply via editing the file.) The issue now seems to be resolved.

Finalcraft:
https://www.dropbox.com/s/j3y4926w3qqiuhc/The%20Orion%20V4%201_1_2%20v2%20boostersfixed.craft?dl=0