# KOS Processor PartModule Configuration Fields¶

Note

(The most important part of this page is probably the section below on the EcPerInstruction setting.)

When using ModuleManager or directly editing the part.cfg files a mod ships with, it is useful to know what those settings mean. This page documents what some of the settings in the kOS part config files mean.

These are the settings typically found in the files named:

GameData/kOS/Parts/ name_of_part_here /part.cfg

You can add kOS to any other part in the game by adding the kOS module to the part (although this may cause strange interactions that are not officially supported).

Here is an example of the kOS processor module : the one that is attached to the small disk shaped CPU part (KR-2402 b). Optional fields have been added in comments for clarity:

MODULE
{
name = kOSProcessor
diskSpace = 5000
ECPerBytePerSecond = 0
ECPerInstruction = 0.000004
# Optional fields shown below with default value
# baseDiskSpace = 0
# diskSpaceCostFactor = 0.0244140625
# baseModuleCost = 0
# diskSpaceMassFactor = 0.0000048829
# baseModuleMass = 0
}


If you add a section like that to the part.cfg, via directly editing it, or via a ModuleManager configuration, then you cause that part to contain a kOS computer.

When editing these values, the case is important. You must capitalize them and lowercase them exactly as shown here.

Here is a list of all the potential fields you could set in that section:

## diskSpace¶

• Type: integer
• Default if omitted: 1024
• Effect: The disk space the part has by default if the adjustment slider in the VAB isn’t changed by the user.

## baseDiskSpace¶

• Type: integer
• Default if omitted: copied from initial diskSpace setting
• Effect: The lowest disk space the part can have at the lowest end of the slider in the VAB.

The possible choices for disk space the user can select on the slider is always one of 1x, 2x, and 4x this amount.

## ECPerInstruction:¶

• Type: float
• Default if omitted: 0.000004
• Effect: How much ElectricCharge resource is consumed per instruction the program executes.

This is a very small number so the electric charge can be payed in micro-amounts as the CPU executes. Remember that with default Unity settings (which can be changed on the KSP game’s main settings screen at the launch of the program), the game runs 25 physical updates per second. So if the setting is 0.000004, and program is executing 200 instructions per update, at 25 updates per second, then it’s consuming 0.02 Ec per second, or 1 Ec every 50 seconds.

This is the setting from which the value in the VAB/SPH info panel, 1 Electric Charge per N instructions, is derived (it’s the reciprocal of that display value).

More information about programs reducing power consumption can be found in the section of the CPU hardware description that talks about electric drain.

## ECPerBytePerSecond:¶

• Type: float
• Default if omitted: 0.0
• Effect: How much ElectricCharge resource is consumed per byte of disk space avaialable (not just used).

It is possible to make the disk cost more electricity to run the bigger it is. By default this ships as zero, but it can be changed by a re-balancing mod by changing this value. This value is multiplied by how much available space there is total (used + free), not just how much is currently in use.

## diskSpaceCostFactor:¶

• Type: float
• Default if omitted: 0.0244140625
• Effect: How much additional cost is incurred per byte of disk space added via the editor tweakable.

When using the editor tweakable to increase storage, cost is added to the module. That additional cost is found by multiplying the number of additional bytes by this factor. The default value is balanced for approximately 100 additional funds for 4096 Bytes.

## baseModuleCost:¶

• Type: float
• Default if omitted: 0.0
• Effect: How much cost is added to the part cost by including this module.

While kOS only includes kOSProcessor in dedicated parts, users may choose to add it to existing parts by editing cfg files or using a ModuleManager patch. In cases where the cost of a part may depend on multiple PartModules this allows you to specify the cost for the kOSProcessor itself without changing the part’s cost directly.

## diskSpaceMassFactor:¶

• Type: float
• Default if omitted: 0.0000048829
• Effect: How much additional cost is incurred per byte of disk space added via the editor tweakable.

When using the editor tweakable to increase storage, mass is added to the module. That additional mass is found by multiplying the number of additional bytes by this factor. The default value is balanced for approximately 0.02kg of additional mass for 4096 Bytes.

## baseModuleMass:¶

• Type: float
• Default if omitted: 0.0
• Effect: How much mass is added to the part cost by including this module.

While kOS only includes kOSProcessor in dedicated parts, users may choose to add it to existing parts by editing cfg files or using a ModuleManager patch. In cases where the mass of a part may depend on multiple PartModules this allows you to specify the mass for the kOSProcessor itself without changing the part’s mass directly.