Difference between revisions of "User:Greys"

From Kerbal Space Program Wiki
Jump to: navigation, search
(Model Assets: fixed newline after phi comment)
(General Parameters:: Wrote section intro text, changed section title, and created data type table v0.0.0.0.0.pre1)
Line 138: Line 138:
  
  
== General Parameters: ==
+
== PART{} Parameters: ==
 
{{Box|module is depreciated except for a small number of modules which have not yet been replaced with a partModule}}
 
{{Box|module is depreciated except for a small number of modules which have not yet been replaced with a partModule}}
 +
{{Box| I, Greys, Don't give any shits about the accepted "order" of defining variables, it is baseless, pointless, places related variables distant to each other, doesn't make sense, and does not serve to increase accessibility, as such I will be writing this page without that order.}}
 +
 +
The order of keys in a .cfg file is completely unimportant. All config nodes and keys are loaded in one solid step, before any other code is given the chance to access the data, as such all of the information in a .cfg file is available to the code immediately. It will not occur that one thing doesn't load right because some piece of information has not been loaded yet. Organize your configurations as you see fit.
 +
 +
What does matter is the kinds of information that the code expects a key to contain.
 +
Also, Capitalization Always Matters. In both Keys and Values, if it's not capitalized the right way, it won't do what you want. This becomes problematic because KSP's capitalization scheme is rather inconsistent.
 +
 +
þ This table will likely need multiple revisions to achieve an optimal representation of the truth in a form that conveys the information adequately.
 +
{| class="wikitable"
 +
|-
 +
! Data Type !! Something !! Example
 +
|-
 +
| Integer || A Number without decimal values and without any formatting || 40008
 +
|-
 +
| Float || A number with decimal values but still no formatting || 40.008
 +
|-
 +
| Text || Plain text || Hi, my name is Guacamole, and I'm stealing your car right now.
 +
|-
 +
| String || A set of letters and numbers, capital or lower case, without spaces or punctuation (exceptions...) || SmallGearBay
 +
|-
 +
| Address || An address relative to /KSP/GameData/ (always use /, never \) || /Squad/Parts/Engine/liquidEngine2-2/
 +
|-
 +
| List || A set of comma separated values, usually integers or floats || 0.00, 0.147, 0.00, 0.0, 1.0, 0.0, 1
 +
|-
 +
|}
 +
 +
  
 
þ This also can be tablized
 
þ This also can be tablized

Revision as of 05:43, 3 September 2013

Does not include the new 0.18 or 0.20 config format changes
This document is presented as a tutorial when, as suggested by the page title, it should be a reference.
Ø comments indicate notes on existing content that is incorrect or inadequate, and will need to be addressed
þ comments are formatting or structural changes that need to be made

GameData

All add-on files should be placed in the GameData folder, located in the root KSP folder alongside the KSP executable. Everything related to a given Add-on should be contained within a folder created specifically for that Add-on. Inside the dedicated folder, the directory structure is largely unimportant.

All of the stock parts are contained within GameData as well, and Squad uses this structure:

/Flags/            -- Flags must go here or they won't be loaded as flags, Capitalization Matters
/Parts/Aero/       -- Aerodynamic parts
/Parts/Command/    -- Command pods, probe cores, and reaction wheels
/Parts/Electrical/ -- Parts that create and store electricity 
/Parts/Engine/     -- Engines
/Parts/FuelTank/   -- Fuel Tanks
/Parts/Structural/ -- Parts that don't do anything, and don't contain resources
/Parts/Utility/    -- Parts that do things and don't contain resources (except some of them do)
/Parts/Wheel/      -- Things that roll
/Props/            -- Props are the functional little elements in IVAs
/Resources/        -- This folder contains the file that declares all of the stock resources
/Sounds/           -- Can you hear the love tonight
/Spaces/           -- Spaces are IVAs

(This is just the way Squad does it, you can do it any way you want)


All assets will be loaded in a depth first alphabetic order, in sets based on file type. Parts will be displayed in the order they are loaded in. Because of this parts located in /GameData/Squad/Parts/Utility/ will always be listed before those in /GameData/Squad/Parts/Wheel/, even if the wheel part's name is before the utility part's name alphabetically.

Aside from load order, the directory structure of /GameData/YourFolder/ only serves as an organizational tool for the developer.

.CFG Files

File type .cfg is used for every configuration file in KSP except persistence files, which are stored in .sfs, these files are simply disk-storable containers for Config Nodes and as such their names and locations are almost entirely insignificant. Each .cfg file will be addressed in depth-first order based on it's position within /GameData/, relative to other .cfg files, and that is the extent of the value that a file's name has.

It is entirely possible to merge all of the top level config nodes of a given add-on pack into a single file, but this is likely to make working with that file much more difficult. It's generally accepted that the best practice is to have a single top level config node per file, or put a small number of closely related parts in a single file. For example, if you have a command pod you could have the PART{}, INTERNAL{}, any custom PROP{}s and any custom RESOURCE_DEFINITION{}s in a single file, but as far as KSP is concerned, having a part.cfg, internal.cfg, props.cfg, etc, in one folder is functionally the same thing.

Note that the .cfg file is not loaded into RAM. The config nodes in it are used to build code objects, and the variables are populated into those objects. As such, reducing the total number of files has zero impact on RAM usage.

Model Assets

There are only two model formats which KSP will load without outside forces, .MU, and .DAE

.DAE is a legacy mode option and should not be used for a multitude of reasons, the first is that .DAE is much more complex to set up, and more finicky about what will work. You also don't have a lot of the options that you would have with .mu

þ make 'Unity' and 'PartTools' links, give PartTools it's own page?

.MU is a compiled model format developed by our holy father Mu produced in Unity using PartTools. .MU files permit a large number options to be applied and changed, and stored inside the model itself. These include animations, manipulations to the texture sheets, customized and primative colliders, control over the shaders used on a part, and the inclusion of Transforms.

A Transform is a Unity Game Object in a specific place and with a specific orientation that is referenced by code to achieve many things, the Gimbal Transform is used to move an engine's nozzle mesh, which is a child of the transform, and the Thrust Transform is used as the coordinates and orientation to apply force to a part, RCS thrusters also use transforms for this.

Model assets can be located anywhere within /GameData/ and referenced by their address from .cfg files using MODEL{}, if not using MODEL{} they need to be in the same folder as the .cfg file.

Texture Assets

There are a lot of kinds of textures which can be used in KSP but only 3 formats are currently accepted by the loader, .MBM, .TGA, and .PNG

Once loaded the format you choose Does Not Matter, KSP will convert everything into uncompressed bitmap and store that in RAM.

  • .TGA and .PNG are both editable, .MBM is technically editable, but it is not a format that graphics editing software will know what to do with, and you'll have to edit some stuff by hand before it can be opened.
  • .MBM is uncompressed, and .TGA has very little compression but is a lossy format.
  • .PNG is a very well compressed lossless format.

To repeat, the format of your files does not matter in game, it only impacts the amount of Data On Disk and the time it takes to read that data off the disk.

Sound Assets

Sound assets appear to be broken at the moment.

Config Nodes

(Note to plugin developers, this document only pertains to .cfgs) Starting in KSP 0.15 a .cfg structure known as Config Nodes was introduced, and later in KSP 0.20.0 alongside the game database system and /GameData/ directory structure. Config Nodes, generally seen as any string of upper case letters, numbers[confirmation needed] and underscores followed by an opening curly bracket ( { ) and later a closing one are a means of having more complexly organized data inside a part's configuration.

Prior to KSP 0.20.0 all parts had to exist by themselves in a file specifically named 'part.cfg', limiting any one folder to containing only one part, and due to restrictions on addressing assets, every part had to have it's own textures and models.

Following the release of KSP 0.20.0 parts must exist inside a .cfg file with any name, and must be wrapped in a PART{} config node. You are permitted to have multiple PART{}s in any given file, and the means of addressing assets has changed to be relative, treating /KSP/GameData/ as the root of any address.

Between the curly brackets of a config node you are able to define variables, their values, and other config nodes so long as they exist in that context. For an example:

PART{
    name = Example
    title = Superfly
    description = These are variables, they should be in lower case, and you can set any variable you want, but the code in game is only going to use what it needs
    banana = is a fully valid variable, that will not be used by anything in KSP

    RESOURCE{
        name = LiquidFuel
        amount = 400
    }
    MODULE{
        name = etc
    }
}

It is important to note that everything in KSP is Case Sensitive, from the variables and values in a .cfg file, to the names of asset files and folders.

Proper tabulation in .cfg files is not necessary, but extremely useful in maintaining readability of complex configurations and will help to make sure all your config nodes are closed properly.

Stock Config Nodes

þ make this a table

Top Level Config Nodes

Node Used For
PART{} Defines a new part
RESOURCE_DEFINITION{} Defines a new resource to be used in and by PART{}s
INTERNAL{} Defines an internal space which can be used by PART{}s
PROP{} Defines an prop, a functional self contained element, which can be used in INTERNALS{}

þ Not sure if GAME{} matters enough to bother with

GAME{} Defines a persistence, probably shouldn't mess with this one.


PART{} Config Nodes

RESOURCE{} Sets a resource and quantity of resource for a part to contain

MODEL{} Alternate to mesh and texture variables, gives much better control but has some bugs

ATTACH{} Alternate to node_ definitions, very buggy, generally not used because of problems

MODULE{} Used to associate functionality with a part by linking a partModule to the PART{} instance

Part Modules

This section is grossly inadequate and outdated, as partModules are the primary way of attaching functionality to a part now

þ Merge into Config Nodes -> Stock Config Nodes -> PART{MODULE{}} þ Several available partModules deserve their own pages, explaining them sufficiently in this page would be unnecessary clutter.


PART{} Parameters:

module is depreciated except for a small number of modules which have not yet been replaced with a partModule
I, Greys, Don't give any shits about the accepted "order" of defining variables, it is baseless, pointless, places related variables distant to each other, doesn't make sense, and does not serve to increase accessibility, as such I will be writing this page without that order.

The order of keys in a .cfg file is completely unimportant. All config nodes and keys are loaded in one solid step, before any other code is given the chance to access the data, as such all of the information in a .cfg file is available to the code immediately. It will not occur that one thing doesn't load right because some piece of information has not been loaded yet. Organize your configurations as you see fit.

What does matter is the kinds of information that the code expects a key to contain. Also, Capitalization Always Matters. In both Keys and Values, if it's not capitalized the right way, it won't do what you want. This becomes problematic because KSP's capitalization scheme is rather inconsistent.

þ This table will likely need multiple revisions to achieve an optimal representation of the truth in a form that conveys the information adequately.

Data Type Something Example
Integer A Number without decimal values and without any formatting 40008
Float A number with decimal values but still no formatting 40.008
Text Plain text Hi, my name is Guacamole, and I'm stealing your car right now.
String A set of letters and numbers, capital or lower case, without spaces or punctuation (exceptions...) SmallGearBay
Address An address relative to /KSP/GameData/ (always use /, never \) /Squad/Parts/Engine/liquidEngine2-2/
List A set of comma separated values, usually integers or floats 0.00, 0.147, 0.00, 0.0, 1.0, 0.0, 1


þ This also can be tablized

name
This is just that, a name. It can be anything, but notice that it's NOT commented out. This is what KSP will refer to the part as internally. It's good form to keep it all one word. Don't worry, you won't see it called this in game, so it can honestly be anything. Must be unique and cannot contain the underscore.
Ø or spaces
module
Now this is slightly more difficult. Each part can be one of several different types of parts, defined by what comes after module. What type the part is defines how it works - for example, a solid rocket booster behaves differently from a liquid rocket motor. See Valid Part Modules for values you can use here.
author
Put your name here, you're the author!
Whoever wrote this section has some rather severe misunderstandings about the functionality and purpose of scale/rescale. Also texture is depreciated

This section defines the assets of our module - it provides us with links to our model and to our texture file, as well as giving us some extra settings to play around with. þ Table basic variables, add Depreciated tickmark column þ Define PART{MODEL} here

mesh
Ø mesh is depreciated and does not need to be used if MODEL{} is used, or only one .mu is present in the folder with the .cfg
scale
Ø If scale is not 1, you have failed to properly configure your modeller and should correct this before moving forwards, as it does significantly complicate things
texture
Ø texture is depreciated
Ø The name of the texture to be used is included in the .mu file, and does not need to be explicitly stated unless it differs, and you would not use this variable to do so
specPower
The specular reflectivity of your part. It's best to leave it as it is.
rimFalloff
This defines the strength of the highlight effect in game. Higher values lead to a more pronounced effect near the edges.
alphaCutoff
This number defines the threshold for transparency on the part's texture. If your texture has an alpha channel (transparency), you can adjust this number to make sure your part is transparent or opaque where it should be. A value of 0 means nothing in the texture is considered to be transparent. A value of 1 means a completely transparent part.
rescaleFactor
Ø rescale factor should be explicitly set to eliminate complications

There, that's everything under asset parameters covered. Let's continue building our dummy part file.

þ Add subsection about MODEL{scale}, scale, rescaleFactor glitch and best practices

cost = 450 :Ø Cost must be an integer, no commas or periods; and it might need to be greater than 0. non-integer values will cause this part and every scheduled to be loaded after it to not be loaded.
category = Propulsion
subcategory = 0
title = 
manufacturer =
description = 
cost
This hasn't really been implemented yet, but when it is it sets the cost for spaceship parts. You can set this to anything for now, it's entirely up to you.
category
There are seven categories:

Pods Propulsion Control Structural Aero Utility Science

subcategory
No use yet. Set it to 0
title
What do you want your part to be called in the rocket editor?
manufacturer
Who built your part?
description
Describe your part here. (Do not use linebreaks. KSP breaks lines automatically in the part's tooltip. A linebreak will cause your description to appear truncated)


þ table that


mass - How much does your part weigh? (Or, for parts that also specify a dryMass parameter, how much does it weigh when full?)

dragModelType - Leave this as default.

maximum_drag - What's the maximum amount of drag on your part? (Usually under 1.) Generally drag when part's direction of travel is along its y-axis.

minimum_drag - The minimum amount of drag your part will encounter. (Usually under 1 and lower than maximum_drag) (this value is unused if dragModelType is set to default) Generally drag when the part's direction of travel is perpendicular to its y-axis.

angularDrag - how much angular drag is there/resistance to turning? (Also usually under 1.)

crashTolerance - How good is your part at surviving crashes? The higher the number the more durable. Numbers are approximately maximum impact speed in m/s.

breakingForce - The amount of linear force at which the joint will fail. This variable does not impact the stiffness of the joint.

breakingTorque - The amount of rotational force at which the joint will fail. This variable does not impact the stiffness of the joint.

maxTemp - The maximum temperature your part can experience before exploding.

stageOffset and childStageOffset - Can be 0, 1, etc. defines whether this part will create a new stage before or after itself, or both (as do decouplers). This only applies for the automatically generated staging sequence. These replace stageBefore and stageAfter.

fuelCrossFeed - Will the part crossfeed fuel between parts attached to it?

NoCrossFeedNodeKey - if set to bottom will keep fuel from flowing FROM bottom nodes (avoiding some stack imbalances and partially mitigating the 0.15 bug of engines generating fuel). Used with parts with multiple bottom nodes, such as the TVR-1180C Mk1 Stack Tri-Coupler.

Node_s

Does not mention ATTACH{}, and ang_ notation can be confusing, should refer to rotation instead of angle

Another fairly easy section, this defines where we attach our part to other parts. You can have as many as you want, for example, tricouplers have four, three bottom and one top, while most parts simply have two, and a few parts have only one.

node_stack_bottom = x, y, z, angx, angy, angz, size
node_stack_top    = x, y, z, angx, angy, angz, size
node_attach       = x, y, z, angx, angy, angz, size

There's three example nodes. There are three different kinds, but only two are useful to us at the moment. We have node_stack and node_attach. Node stack is for defining where the part stacks vertically together with other parts, and node attach is used for defining where on the surface of your part other parts attach - so horizontal attachment.

All node attachment values are given with respect to an object's origin, and their values correspond to a model's units and scaling factors. A node_stack_bottom with x, y, and z values of (2.5, 5.0, 3.0) will have an attachment node 2.5 units to the right, 5.0 units up, and 3.0 units forward. The next three values refer to the orientation that a particular node will accept other attachments, on a scale of -1.0 to 1.0. These represent the vector that a part will orient itself on when attaching to the node. For example, a fuel tank with a node_stack_bottom will have angx, angy, and angz values of (0.0, -1.0, 0.0). This represents a vector downward relative to the part model, in the negative y direction. A value of (0.0, -1.0, 1.0) would represent a diagonal vector downward and forward, while a value of (1.0, 1.0, 1.0) would represent a vector to the right, up, and forward.

Generally, most parts will have angx, angy, and angz values of either (0.0, -1.0, 0.0) for a node_stack_bottom and (0.0, 1.0, 0.0) for a node_stack_top.

The last value indication the visual size of an attachment node. Values may be either 0 (small half-meter node), 1 (normal), or 2 (large). This parameter is optional and will default to 1 if nothing is specified. Keep in mind, naming conventions (_stack_bottom, _stack_top) for nodes only apply to node_attach; they are only helpful in identifying a node's position.

Attachment rules:

þ table This defines how your part attaches to other parts.

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

The rules correspond to the numbers below - 1 is allow, 0 is prevent. The tags are:

stack - Can your part be stacked on others?

SrfAttach - Can your part be placed onto a surface?

allowStack - Will you allow other parts to be stacked on your part?

allowSrfAttach Can other parts be placed on the surface of yours?

allowCollision - A special one: Can your part be placed if part of it is intersecting another part?


Note that you can also force parts attached to this part to attach in a specific symmetry.

  • // symmetry rules: 0=1x, 1=2x, 2=3x, 3=4x and so on...
  • stackSymmetry = 3

FX definitions:

More definitions! But this time, you're positioning the flame coming out the back of the rocket.

fx_exhaustFlame_yellow = x, y, z, angx, angy, angz, active
fx_exhaustLight_yellow = x, y, z, angx, angy, angz, active
fx_smokeTrail_medium   = x, y, z, angx, angy, angz, active

Okay, looks pretty similar to node_definitions, right?

You'll notice, just like node definitions, there are separate parts to each effect. You have fx_exhaustFlame, fx_exhaustLight, and fx_smokeTrail.

There are exactly what they sound like, the flame, the light, and the smoke trail.

There are variations on flame color, blue is also an option. To get a blue flame, you would use fx_exhaustFlame_blue. You would do the same for the exhaustLight.

The 'active' switch on the end is used to define when this effect will be visible. See the FX Groups listing to know which effect groups are available, and when they are used. It's also possible to assign an effect to more than just one FX Group. If for instance, you want a smoke effect to be visible both when the part activates and also when it deactivates itself, you can do this:

fx_gasBurst_white = x, y ,z, angx, angy, angz, activate, deactivate

This is particularly useful if you're defining a lot of effects, like the gas discharges on an RCS module


Easy enough, right? Adding to dummy file and continuing.

Modules

Nearly all modules have been depreciated and replaced with partModules which offer more control

So what part types can you have? þ Reorder rows based on frequency of use: Part, Winglet ControlSurface, HLandingLeg, FuelLine, Strut

Part Name Description
ControlSurface Movable wing-like surface. Can act as a rudder, aileron, elevator, canard or other aerodynamic control surface - function depends on placement on a ship.
Winglet A lift producing part. Not movable.
StrutConnector Used for making struts (the space ducttape kind)
FuelLine Allows for transfer of fuel.
HLandingLeg A moving landing leg, using .cfg parameters to move.
Part This module should be used for all parts except for a few specific instances where the module has not yet been replaced with a partModule


There is nothing special about module Part.


Module Settings

þ merge with Modules section We're almost finished, a complete part is almost at our hands and you should know almost everything you need to create a part.cfg file. However, remember back when we were setting types? Well each type has an individual set of specific part parameters that change depending on what type of part it is.

You cannot mix and match parameters from different module types - it doesn't work.

These specific parameters are actually public variables defined in the Part classes themselves. The standard parameters are declared in the Part base class, and the specific ones in each Part extension (i.e., Modules)

Time to go through and see what special parameters each module can have.

Winglets

þ Make this a table

dragCoeff - The drag co-efficiency of the wings.

deflectionLiftCoeff - How much lift the wings generate.

Control Surfaces

þ Make this a table

ctrlSurfaceRange - How far off centre the control surface (rudder / aileron etc) can move under control

ctrlSurfaceArea - The effective surface area of the control surface - the bigger the surface, the bigger the surface area must be set to