horizontal parachutes

[MacLuky]

Hi,

I'm trying to patch an old mod and get this:

 

I've copied and paste a bit to make the drag work, but struggle to understand what I am doing:

 

PART
{
// this is a sample config file, for determining a good file format for defining part parameters
// comment line - ignored by cfg parser
// empty lines, or lines without a '=' sign are also ignored
// all other lines are split at the '=' sign, and the left operand is used to know what parameter we are setting
// diferent parameters require data in different formats (see docs), and each module has it's own parameters (again, see docs)
// each assignment must be in a single line. Lines without assignments will be ignored. (You CAN turn on word wrap, though)
// each keyword here relates to an existing variable in the assigned module. If the keyword isn't found, it is ignored.
// conversely, if a keyword is left unassigned (as in not in the file), it will be initialized with it's default value
// This is done automatically, so any public variable defined in the loaded module can be accessed this way (provided it's value can be parsed)


// --- general parameters ---
name = parachutekpollo
module = Part
author = Ledenko

// --- asset parameters ---
MODEL
    {
        model = KerbonTech/Parts/KP0110/kp0110chute
    }
scale = 1

rescaleFactor = 1

// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z, size
node_stack_bottom = 0.0, -0.09, 0.0, 0.0, -1.0, 0.0, 1
node_stack_top = 0.0, 0.330, 0.0, 0.0, 1.0, 0.0, 1
node_attach = 0.0, 0.09, 0.0, 0.0, -1.0, 0.0

// --- FX definitions ---
sound_parachute_open = activate


// --- editor parameters ---
TechRequired = specializedControl
entryCost = 7600
cost = 1700
category = Utility
subcategory = 0
title = K-P0110 Parachute Module

description = This is actually an integral part of the K-P0110 command module. If it somehow becomes separated, it means you've voided your warranty.

// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision
attachRules = 1,0,1,1,0

// --- standard part parameters ---
mass = 0.3
dragModelType = default
angularDrag = 3
crashTolerance = 12
maxTemp = 3100

breakingForce = 100
breakingTorque = 50

stageOffset = -1


  DRAG_CUBE
  {
    cube = PACKED, 0.6256,0.6346,0.7139, 0.6256,0.6346,0.7139, 1.108,0.7327,0.6962, 1.108,0.9453,0.1664, 0.6256,0.6357,0.7139, 0.6256,0.6335,0.7139, 0,0.2645,0, 1.233,0.6659,1.233
    cube = SEMIDEPLOYED, 15.34,0.2139,1.823, 15.34,0.2139,1.823, 9.335,0.6554,18.06, 9.335,0.6494,18.5, 15.35,0.2155,1.823, 15.35,0.2123,1.823, 0,9.231,-1.073E-06, 3.459,18.6,3.459
    cube = DEPLOYED, 52.6,13.17,6.153, 52.6,13.17,6.153, 115,22.3,18.44, 115,22.05,18.73, 52.6,13.22,6.153, 52.6,13.12,6.153, 0,9.235,-9.537E-07, 12.15,18.61,12.15
  }


// ----- DO NOT EDIT BELOW THIS POINT ------
MODULE
{
  	name = ModuleParachute
	invertCanopy = true
	autoCutSpeed = 0.5
	capName = cap
	canopyName = Canopy
	semiDeployedAnimation = mainhalfdeploy
	fullyDeployedAnimation = mainfullydeploy
	stowedDrag = 0.22
	semiDeployedDrag = 1
	fullyDeployedDrag = 500
	minAirPressureToOpen = 0.01
	deployAltitude = 500
	deploymentSpeed = 0.12 //1
	semiDeploymentSpeed = 0.4 //1	
}
	MODULE
	{
		name = ModuleDragModifier
		dragCubeName = SEMIDEPLOYED
		dragModifier = 0.67
	}
	MODULE
	{
		name = ModuleDragModifier
		dragCubeName = DEPLOYED
		dragModifier = 25
	}

MODULE
{
	name = ModuleDockingNode
	referenceAttachNode = top
	nodeType = size1
}
MODULE
{
name = ModuleAnimateGeneric
animationName = Dockingprobeanim
startEventGUIName = Extend Docking Probe
endEventGUIName = Retract Docking Probe
}
}

Anyone that could shed some light on this would be forever in my debt, I'll name a ship after you ;-)

[Superfluous J]

In the VAB you can define the angle that radial chutes splay out, to keep them from being drawn over each other. This is a purely visual thing.

It looks like either your part's default is a high number, or you accidentally set it to a high number.

Look at the stock radial chute config and see if there are any settings missing. I bet the config you posted here is from an older version of KSP that didn't have the angle setting yet.

[MacLuky]

Spread Angle you mean? no that is set to the same value. I've been comparing stock cfg to the old one, but I believe they should be almost identical now.

Perhaps: invertCanopy = true?

I've also peeked at restock, but my guess is that in the past the deploy direction was along the Z axis and now its the Y, which would imply it cant be fixed in the cfg

@linuxgurugamer have you seen this before in your endeavours to resurrect old mods?

Edited February 9, 2020 by MacLuky

[linuxgurugamer]

It's  probably so nothing in the .mu file, but I'm  not positive.

Maybe ask @stupid_chris