Scale in parts.cfg

[Burning For New Frontiers]

I was attempting to mess with the dimensions of a few parts, so I edited scale = 1 to scale = 1 , 4 , 1, to increase the height of the part. Then KSP refused to load the part. Any ideas why ? Am I doing something wrong, or is it just impossible to change only one dimension of a part ? 

[Phineas Freak]

The "scale" and "rescaleFactor" parameters require a single float value and are not comma - separated:

scale = 1.0
rescaleFactor = 1.0

You probably meant the MODEL{} node scale method:

MODEL
{
    model = Path/To/Model/File
    scale = 1.0, 1.0, 1.0
}

that can be used to scale each axis (X, Y, Z) independently.

[Burning For New Frontiers]

Ah. I see where I went wrong. thanks!

[Stone Blue]

@Burning For New Frontiers Just realise that the MODEL scale line, will rescale ONLY the model... and NOT the attachment nodes... If you want to rescale the model AND the attachment nodes with it (so everything will attach in the proper place on the enlarged model), you want to use the rescaleFactor def... the rescaleFactor defaults to 1.25m ... So, IIRC, to enlarge the part to a 2.5m, you would rescaleFactor = 2 ... rescaleFactor = 1 would be a 1m based part...

You can use a combination of the two, but then theres math and ratios involved to figure out...

As a sidenote, you should really only have to define the scale = (the one OUTSIDE the MODEL node), if the part was modelled using a scale other than 1m in the modelling program... So scale = 1 is 1m units, 0.1 is one modelled using 0.1m unit (decimeter), 0.01m unit (centimeters)

 

Edited July 26, 2016 by Stone Blue

[Burning For New Frontiers]

Thanks, but I already know that. I'm fiddling with the nodes to place them right, but it's slow as hell, thanks to my laptop's chronic lack of RAM.

[Stone Blue]

@Burning For New Frontiers OK... I just didnt know if you knew one rescaled with the nodes, and one doesnt...

I've found Felbourn's NodeHelper mod to be invaluable for setting up nodes... However, when using it with the rescaleFactor, it does some weird stuff... You can use it to place the nodes, but I dont let it write the new changes... I copy down the node coords, and edit them into the .cfg myself...

[Burning For New Frontiers]

Thanks! 

Thanks! Unfortunately my rig is sooooooo slow. So, no mods. ;(

[Stone Blue]

34 minutes ago, Burning For New Frontiers said:

Thanks! 

Thanks! Unfortunately my rig is sooooooo slow. So, no mods. ;(

Well, NodeHelper is just 3 small files, and only 32Kb total... So that alone shouldnt really affect your performance at all... ??

[Burning For New Frontiers]

I have less than 1 GB of total RAM.

[Stone Blue]

31 minutes ago, Burning For New Frontiers said:

I have less than 1 GB of total RAM.

Hmmm... you mean hardware-wise?... or 1GB left over after Windows7, 8, 10 sux down 1GB-1.5GB by itself?

[Vanamonde]

You're asking about something modders have experience with, and so your question has been moved to the modding section. Good luck with it. 

[Burning For New Frontiers]

1 GB by itself. I like to think that I'm now immune to the effects acute lag-itis.

Anyway, a doubt. What does PartDatabase.cfg do in the KSP folder? And how do you make parts appear in-game, when the save files are already there? I'm not sure how I lost them. Plus, is it possible to swap models, say replacing a Mk 1-2 Command Pod with a Mammoth while retaining command module functionality and other silliness?

Edited July 28, 2016 by Burning For New Frontiers