Part is not loading to KSP

[PatPL]

Hi!

There's my problem:

I've made a model and texture, like always, then wrote part.cfg file. The problem is, that in game this part is shown like a "Resource" in debugging menu.

I think i have added new resource incorrectly:

part.cfg:

RESOURCE

{

name = KG

amount = 0

maxAmount = 2499

}

resources.cfg: (In other folder)

RESOURCE_DEFINITION{

name = KG

density = 0.001

unitCost = 1

flowMode = NO_FLOW

transfer = NONE

}

Please help and thanks for taking a look at my thread!

[OrbitusII]

Can we see the whole config file? I'm guessing you may have missed the "PART{}" braces that go around the entire config.

[PatPL]

Of course!

Here it is:

PART{

name = weightsmall

module = Part

author = PatPL

mesh = model.mu

scale = 1

TechRequired = aerodynamicSystems

entryCost = 5000

cost = 1

category = Utility

subcategory = 0

title = M-2500 Small Weight

manufacturer = Stability Airplanes Weights

description = Low-Tier weight, that can be used in smaller planes. One KG of mass costs 1 funds. Can be decoupled.

attachRules = 0,1,0,0,0

mass = 0.001

dragModelType = default

maximum_drag = 0.2

minimum_drag = 0.2

angularDrag = 1

crashTolerance = 8

maxTemp = 3200

stagingIcon = DECOUPLER_HOR

stageOffset = 1

childStageOffset = 1

MODULE

{

name = ModuleAnchoredDecoupler

anchorName = anchor

ejectionForce = 500

explosiveNodeID = srf

}

RESOURCE

{

name = KG

amount = 0

maxAmount = 2499

}

}

[nli2work]

missing attach node definition might have something to do with it.

node_attach = 0, 0, 0, 0, 1, 0, 1

and if you don't have an object in the MU named "anchor" the decoupler module will throw NRE whenever you try to decouple. explosiveNodeID also needs a surface attach node defined.

[PatPL]

Thanks for Your help!

node_attach = 0, 0, 0, 0, 1, 0, 1

worked!

[CaptainKipard]

I recommend the use of MODEL{} nodes instead of the old mesh variable. Mesh variables force you to keep only one .mu file per folder and there are obvious benefits to keeping multiple models in a folder, one of which is the ability to share a single texture if, e.g. you're making a set of similarly themed parts.

I also recommend the use of transform-based NODE{} system. It makes positioning of attach nodes and stack nodes much easier.

Edited October 4, 2014 by Cpt. Kipard