Difference between revisions of "FX Groups"
From Kerbal Space Program Wiki
m (Reverted edits by Rocketing Rudolph (talk) to last revision by Kerbas ad astra) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
# For parts which use ModuleEngines (e.g. most stock rocket engines, older mod engines), an FX definition has a position and orientation, and can be "attached" to various engine events (e.g. engage, running, disengage, flameout). See the [[Parts/Engine/solidBoosterRT-5/solidBoosterRT-5.cfg|RT-5 booster configuration]] for an example of this kind of usage. | # For parts which use ModuleEngines (e.g. most stock rocket engines, older mod engines), an FX definition has a position and orientation, and can be "attached" to various engine events (e.g. engage, running, disengage, flameout). See the [[Parts/Engine/solidBoosterRT-5/solidBoosterRT-5.cfg|RT-5 booster configuration]] for an example of this kind of usage. | ||
# For parts which use ModuleEnginesFX (e.g. most stock jet engines, newer mod engines), an EFFECTS{} node has sub-nodes for those engine events, and those sub-nodes in turn may have PREFAB_PARTICLE{} nodes which include a "prefabName" from from the following list (as well as orientation, speed, and other control parameters). See the [[Parts/Engine/MassiveSRB/part.cfg|Kickback booster configuration]] for an example of this type of usage. | # For parts which use ModuleEnginesFX (e.g. most stock jet engines, newer mod engines), an EFFECTS{} node has sub-nodes for those engine events, and those sub-nodes in turn may have PREFAB_PARTICLE{} nodes which include a "prefabName" from from the following list (as well as orientation, speed, and other control parameters). See the [[Parts/Engine/MassiveSRB/part.cfg|Kickback booster configuration]] for an example of this type of usage. | ||
| + | |||
| + | The predefined FX names are: | ||
* fx_exhaustFlame_blue | * fx_exhaustFlame_blue | ||
Latest revision as of 18:34, 17 March 2017
This is a list of predefined FX definitions for use in part.cfg files. They can be used in two ways:
- For parts which use ModuleEngines (e.g. most stock rocket engines, older mod engines), an FX definition has a position and orientation, and can be "attached" to various engine events (e.g. engage, running, disengage, flameout). See the RT-5 booster configuration for an example of this kind of usage.
- For parts which use ModuleEnginesFX (e.g. most stock jet engines, newer mod engines), an EFFECTS{} node has sub-nodes for those engine events, and those sub-nodes in turn may have PREFAB_PARTICLE{} nodes which include a "prefabName" from from the following list (as well as orientation, speed, and other control parameters). See the Kickback booster configuration for an example of this type of usage.
The predefined FX names are:
- fx_exhaustFlame_blue
- fx_exhaustFlame_blue_small
- fx_exhaustFlame_white_tiny
- fx_exhaustFlame_yellow
- fx_exhaustFlame_yellow_small
- fx_exhaustFlame_yellow_tiny
- fx_exhaustLight_blue
- fx_exhaustLight_yellow
- fx_exhaustSparks_flameout
- fx_exhaustSparks_yellow
- fx_gasBurst_white
- fx_gasJet_tiny
- fx_gasJet_white
- fx_smokeTrail_light
- fx_smokeTrail_medium
