Difference between revisions of "Parts/Command/mk1Cockpits/mk1Cockpit.cfg"
(Created page with "<pre> 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 ...") |
(Updated for 0.23) |
||
| Line 1: | Line 1: | ||
| − | + | 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 = Mark1Cockpitmodule = Partauthor = C. Jenkins// --- asset parameters ---mesh = model.muscale = 0.1// --- node definitions ---// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Znode_stack_bottom = 0.0, -2.15, 0.0, 0.0, 1.0, 0.0, 1// --- editor parameters ---TechRequired = flightControlentryCost = 4200cost = 1800category = Podssubcategory = 0title = Mk1 Cockpitmanufacturer = C7 Aerospace Division.description = C7 Aerospace is proud to present our second generation cockpit. This unit is equipped to ensure survival in some of the worst conditions possible. The extra re-enforcement has slightly increased the weight.// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollisionattachRules = 1,0,1,1,0// --- standard part parameters ---mass = 1.25dragModelType = defaultmaximum_drag = 0.1minimum_drag = 0.1angularDrag = 2crashTolerance = 45maxTemp = 3400vesselType = Ship// --- internal setup ---CrewCapacity = 1INTERNAL{ name = mk1CockpitInternal}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.375 }}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}} | |
| − | 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 = | ||
| − | |||
| − | |||
| − | |||
| − | // --- asset parameters --- | ||
| − | mesh = model. | ||
| − | |||
| − | |||
| − | // --- node definitions --- | ||
| − | // definition format is Position X, Position Y, Position Z, Up X, Up Y, Up | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | // --- editor parameters --- | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | description = C7 Aerospace is proud to present | ||
| − | // attachment rules: stack, srfAttach, allowStack, allowSrfAttach, | ||
| − | |||
| − | |||
| − | // --- standard part parameters --- | ||
| − | mass = 1. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | // --- internal setup --- | ||
| − | CrewCapacity = | ||
| − | |||
| − | |||
| − | |||
| − | { | ||
| − | |||
| − | } | ||
| − | |||
| − | MODULE | ||
| − | { | ||
| − | |||
| − | |||
| − | } | ||
| − | |||
| − | RESOURCE | ||
| − | { | ||
| − | name = ElectricCharge | ||
| − | amount = | ||
| − | |||
| − | } | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | } | ||
| − | |||
Revision as of 14:55, 18 December 2013
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 = Mark1Cockpitmodule = Partauthor = C. Jenkins// --- asset parameters ---mesh = model.muscale = 0.1// --- node definitions ---// definition format is Position X, Position Y, Position Z, Up X, Up Y, Up Znode_stack_bottom = 0.0, -2.15, 0.0, 0.0, 1.0, 0.0, 1// --- editor parameters ---TechRequired = flightControlentryCost = 4200cost = 1800category = Podssubcategory = 0title = Mk1 Cockpitmanufacturer = C7 Aerospace Division.description = C7 Aerospace is proud to present our second generation cockpit. This unit is equipped to ensure survival in some of the worst conditions possible. The extra re-enforcement has slightly increased the weight.// attachment rules: stack, srfAttach, allowStack, allowSrfAttach, allowCollisionattachRules = 1,0,1,1,0// --- standard part parameters ---mass = 1.25dragModelType = defaultmaximum_drag = 0.1minimum_drag = 0.1angularDrag = 2crashTolerance = 45maxTemp = 3400vesselType = Ship// --- internal setup ---CrewCapacity = 1INTERNAL{ name = mk1CockpitInternal}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.375 }}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}}
