Difference between revisions of "Parts/Command/mk1InlineCockpit/mk1InlineCockpit.cfg"

From Kerbal Space Program Wiki
Jump to: navigation, search
m (BobBot moved page Parts/Command/Mark2Cockpit/part.cfg to Parts/Command/mk1InlineCockpit/mk1InlineCockpit.cfg without leaving a redirect: Renamed part configuration file after update.)
m (*update to 0.25;)
Line 1: Line 1:
{{Part config|Mk2 Cockpit|2=PART
+
{{Part config|Mk1 Inline Cockpit|2=PART
 
{
 
{
 
// this is a sample config file, for determining a good file format for defining part parameters
 
// this is a sample config file, for determining a good file format for defining part parameters
Line 33: Line 33:
 
category = Pods
 
category = Pods
 
subcategory = 0
 
subcategory = 0
title = Mk2 Cockpit
+
title = Mk1 Inline Cockpit
 
manufacturer = C7 Aerospace Division
 
manufacturer = C7 Aerospace Division
 
description = A next generation inline cockpit. Designed for sleek high speed aircraft.
 
description = A next generation inline cockpit. Designed for sleek high speed aircraft.

Revision as of 22:48, 7 October 2014

This is the configuration file for Mk1 Inline Cockpit.
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 = Mark2Cockpit
module = Part
author = C. Jenkins

// --- asset parameters ---
mesh = model.mu
scale = 0.1

// --- node definitions ---
// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Z
node_stack_top = 0.0, 7.5, 0.0, 0.0, 1.0, 0.0
node_stack_bottom = 0.0, -7.75, 0.0, 0.0, 1.0, 0.0
node_attach = 0.0, 0.0, 5.12, 0.0, 0.0, -1.0, 1

// --- editor parameters ---
TechRequired = advFlightControl
entryCost = 5800
cost = 1600
category = Pods
subcategory = 0
title = Mk1 Inline Cockpit
manufacturer = C7 Aerospace Division
description = A next generation inline cockpit. Designed for sleek high speed aircraft.
//attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollision
attachRules = 1,0,1,1,0

// --- standard part parameters ---
mass = 1
dragModelType = default
maximum_drag = 0.08
minimum_drag = 0.08
angularDrag = 1
crashTolerance = 40
maxTemp = 3400

vesselType = Ship

// --- internal setup ---
CrewCapacity = 1

INTERNAL
{
  name = GenericSpace1
}

MODULE
{
	name = ModuleCommand
	minimumCrew = 1
}

RESOURCE
{
	name = ElectricCharge
	amount = 50
	maxAmount = 50
}
MODULE
{
	name = ModuleSAS
}

MODULE
{
	name = ModuleReactionWheel
	
	PitchTorque = 10
	YawTorque = 10
	RollTorque = 10
	
	RESOURCE
	{
		name = ElectricCharge
		rate = 0.3
	}
}
MODULE
{
	name = ModuleScienceExperiment	
	
	experimentID = crewReport
	
	experimentActionName = Crew Report
	resetActionName = Discard Crew Report
	reviewActionName = Review Report
	
	useStaging = False	
	useActionGroups = True
	hideUIwhenUnavailable = True	
	rerunnable = True
	
	xmitDataScalar = 1.0
}
MODULE
{
	name = ModuleScienceContainer
	
	reviewActionName = Review Stored Data
	storeActionName = Store Experiments
	evaOnlyStorage = True
	storageRange = 1.3
}
RESOURCE
{
	name = MonoPropellant
	amount = 7.5
	maxAmount = 7.5
}
MODULE
{
      name = FlagDecal
      textureQuadName = flagTransform
}
}