Is there a way to fix a LV-N partial break in KSP with notepad?

[AfailingHORSE]

I launched something yesterday that was had some LVNs with a decoupler on them, when I jettisoned the coverings they hit noting, yet my nukes arent getting any fuel. When I asked about this in the IRC yesterday I was told that it was because that LVNs partially broke off, is there a way to fix this in notepad?

Edited May 30, 2014 by AfailingHORSE

[Cmdr. Arn1e]

probably get the right advice if in the right place - this will probably get moved to the gameplay sub-board when a mod gets round to it...

[Kasuha]

Your fuel is likely not related to the way how you decoupled them or how you removed their shrouds.

Shrouds should come off automatically if you activate the engine so if you have removed them manually, maybe you just need to activate them - either stage once again, or right-click on each engine and select Activate.

If that does not help, post a screenshot of your ship.

[AfailingHORSE]

When I activated the engines was when the shrouds came off, I'll post a pic of the behemoth later. Also, completely forgot about the gameplay subforum...

[Eric S]

Yup, need screenshots or .craft files, fuel flow in KSP can have some odd behaviors until you get used to it, though I think Kasuha is the expert on that.

[nobbers12345]

I also have an issue where the shrouding doesn't come off.

It works though.

[Vanamonde]

Moved to gameplay, with a request for screenshots that include the HUD overlay.

[AfailingHORSE]

And picture, when I tested it fuel was going through the bicoupler. and thank you mod

Edited May 29, 2014 by AfailingHORSE

[Claw]

I can't tell anything from the picture. It looks like you clicked on a different tank than what the LV-Ns are connected to and I don't see anything blatantly wrong (assuming you're talking about the LV-Ns in the center).

If it's all stock, you can upload the save file and I'll have a look.

[AfailingHORSE]

That is the same tank the LVNs are connected to. It also has mechjeb on it due to part count (over 700)

[BudgetHedgehog]

I see two engines that have no fuel.. which engines are they and which is the empty tank?

[Claw]

That is the same tank the LVNs are connected to. It also has mechjeb on it due to part count (over 700)

Ahh okay. I was mistaking what is highlighted for the tank you clicked on. I have MJ so I can still have a look if you'd like. 700 parts might be right around my computer's limit.

[AfailingHORSE]

I see two engines that have no fuel.. which engines are they and which is the empty tank?

The LVNs, and there is no empty tanks, I went into notepad and filled everything with fuel (the game cheated me, I feel no shame in cheating it).

Ahh okay. I was mistaking what is highlighted for the tank you clicked on. I have MJ so I can still have a look if you'd like. 700 parts might be right around my computer's limit.

Right then, dont look at the destroyer then, that is 800+ parts and a docked ship. I will upload the PU after I finish this capture

Edited May 30, 2014 by AfailingHORSE

[AfailingHORSE]

Persistent

[Taki117]

Fuel does not flow through Decoupers! That's the issue. Because your nukes are attached to decouplers they are not getting any fuel (As indicated by the empty gauges in the staging list) to rectify the issue you need to run a fuel line from the tank to each engine, or simply get rid of the decouplers. HOWEVER: This is a during construction fix, to fix the fuel flow issue in flight close KSP, pop open the config file (Located in /GameData/Squad/Parts/Utility/StackDecoupler) using your favorite text editor (Notepad will do) and find the line "fuelCrossFeed = False" Change "False" to "True" save changes and load KSP, Profit.

[Claw]

Taki, are you going off of the pic or the persistence? I can't see decouplers in the pic, but I can't check the persistence till later.

I see the yellow stripes, but I think LV-Ns come with those.

[Kasuha]

I'm not able to load that persistence because it's not stock. LV-Ns mounted this way should have access to fuel in that tank assuming there is fuel, except if you mounted some part without fuel crossfeed (e.g. structural panel) between the bicoupler and the tank or between engines and the bicoupler.

There might be some structal problem with the ship. I have already met a ship that looked correct but when I went through the persistence, parts were connected way differently than what their physical placement suggested. Most probably it was caused by some bug either during ship docking or during construction of the ship in VAB.

[BudgetHedgehog]

to fix the fuel flow issue in flight close KSP, pop open the config file (Located in /GameData/Squad/Parts/Utility/StackDecoupler) using your favorite text editor (Notepad will do) and find the line "fuelCrossFeed = False" Change "False" to "True" save changes and load KSP, Profit.

Probably best to change just those decouplers in the persistent.sfs - changing it globally might have serious unintended future consequences. Would not recommend the above advice.

[AfailingHORSE]

There are no decouplers under the LVN, just a Bicoulper...

[Claw]

There are no decouplers under the LVN, just a Bicoulper...

Okay, I have time again. I'll be looking at it shortly.

[AfailingHORSE]

Thanks

1234

[Claw]

For some reason, your save file seems to think the bi-coupler is connected to a structural panel.

Anyway, here's here's how you fix it.

Go to your ship and quicksave. Open your quicksave.sfs (maybe make a copy first) and CTRL+F your way to this part by searching for the uid 1132969913

You're looking for the part below.

			PART
			{
				name = adapterLargeSmallBi
				uid = 1132969913
				mid = 1993374284
				[COLOR="#FF0000"]parent = 55[/COLOR]
				position = 5.00679016113281E-06,-

15.6500091552734,1.35898590087891E-05
				rotation = -3.243357E-07,-0.3826842,3.698444E-

07,0.9238794
				mirror = 1,1,1
				istg = 0
				dstg = 0
				sqor = -1
				sidx = -1
				attm = 0
				srfN = None, -1
				[COLOR="#FF0000"]attN = top, 55[/COLOR]
				attN = bottom01, 60
				attN = bottom02, 59
				mass = 0.1
				temp = -175.2057
				expt = 0.5
				state = 0
				connected = True
				attached = True
				flag = NASAmission/Flags/NASA
				rTrf = adapterLargeSmallBi
				EVENTS
				{
				}
				ACTIONS
				{
				}
			}

The parts highlighted in red need to be changed as follows:

...
				parent = 3
...
				attN = top, 3
...

Save and quickload.

Good luck,

-Claw

Edit: By the way, 700 parts my butt. That thing was 1012. Although I was happy to discover that my computer was able to handle it.

[AfailingHORSE]

Sry, last I checked it was 700, I try that after lunch.

[AfailingHORSE]

It worked, however, it was not the quicksave.sfs but the persistent.sfs I need. Thanks

[Claw]

It worked, however, it was not the quicksave.sfs but the persistent.sfs I need. Thanks

Well, you can do either one. In any case, I'm glad you got it fixed.