Difference between revisions of "Parts/Utility/decouplerSeparatorTR-2C/decouplerSeparatorTR-2C.cfg"

From Kerbal Space Program Wiki
< Parts‎ | Utility
Jump to: navigation, search
m (XZise moved page Parts/stackSeperatorMini/part.cfg to Parts/Utility/stackSeparatorMini/part.cfg without leaving a redirect: move to new location (already exists), was updated to 0.23)
m (*update to 0.24.2;)
Line 25: Line 25:
 
// --- node definitions ---
 
// --- node definitions ---
 
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
 
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_bottom = 0.0, -0.07590994, 0.0, 0.0, 1.0, 0.0
+
node_stack_bottom = 0.0, -0.07590994, 0.0, 0.0, 1.0, 0.0, 0
node_stack_top = 0.0, 0.07590994, 0.0, 0.0, 1.0, 0.0
+
node_stack_top = 0.0, 0.07590994, 0.0, 0.0, 1.0, 0.0, 0
  
 
// --- FX definitions ---
 
// --- FX definitions ---
Line 67: Line 67:
 
     isOmniDecoupler = true
 
     isOmniDecoupler = true
 
     ejectionForce = 15
 
     ejectionForce = 15
 +
}
 +
MODULE
 +
{
 +
name = ModuleTestSubject
 +
 +
// nowhere: 0, srf: 1, ocean: 2, atmo: 4, space: 8
 +
environments = 15
 +
 +
useStaging = True
 +
useEvent = False
 +
}
 
}
 
}
  
}
 
 
}}
 
}}

Revision as of 22:32, 11 August 2014

This is the configuration file for TR-2C Stack Separator.
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 = stackSeparatorMini
module = Part
author = NovaSilisko

// --- asset parameters ---
mesh = model.mu
scale = 1
rescaleFactor = 1


// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_bottom = 0.0, -0.07590994, 0.0, 0.0, 1.0, 0.0, 0
node_stack_top = 0.0, 0.07590994, 0.0, 0.0, 1.0, 0.0, 0

// --- FX definitions ---

sound_vent_large = decouple


// --- editor parameters ---
TechRequired = advMetalworks
entryCost = 6200
cost = 450
category = Structural
subcategory = 0
title = TR-2C Stack Separator
manufacturer = O.M.B. Demolition Enterprises
description = Similarly to the TR-18D, the TR-2C is a utility for slicing a rocket into two halves, but now in a more compact size. The manual says the explosive content is just enough to eject anything attached to the unit in a safe, controlled manner. The delivery guy did have a full bomb suit on though, so try not to drop it.


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

// --- standard part parameters ---
mass = 0.02
dragModelType = default
maximum_drag = 0.2
minimum_drag = 0.2
angularDrag = 2
crashTolerance = 9
maxTemp = 3400
fuelCrossFeed = False

stageOffset = 1
childStageOffset = 1


// ----- DO NOT EDIT BELOW THIS POINT ------
MODULE
{
    name = ModuleDecouple
    isOmniDecoupler = true
    ejectionForce = 15
}
MODULE
{
	name = ModuleTestSubject
	
	// nowhere: 0, srf: 1, ocean: 2, atmo: 4, space: 8
	environments = 15
	
	useStaging = True
	useEvent = False
}
}