Difference between revisions of "DgBangerData"
(→yada yada) |
m (→Specification - headings) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The ''dgBangerData'' files are used to define collision properties for [[PKG]] objects. These properties define how an object behaves when something collides with it. The format is ASCII-based and made up of tag-value rows grouped in ''blocks'' between ''{'' and ''}'' symbols. | + | The ''dgBangerData'' files are used to define collision properties for [[PKG]] objects. These properties define how an object behaves when something collides with it. |
| + | |||
| + | The file names are derived from the name of the [[PKG]] and the names of the internal parts of it. The syntax is like this for the banger data of the entire object: | ||
| + | /tune/banger/<pkgname>.dgBangerData | ||
| + | |||
| + | and like this for the breakable parts: | ||
| + | /tune/banger/<pkgname>_<partname>.dgBangerData | ||
| + | |||
| + | For example, the banger data for the wooden barricade, ''/geometry/sp_barricadewood_f.pkg'', of SF and London is defined in the following files: | ||
| + | /tune/banger/sp_barricadewood_f.dgBangerData | ||
| + | /tune/banger/sp_barricadewood_f_BREAK01.dgBangerData | ||
| + | /tune/banger/sp_barricadewood_f_BREAK02.dgBangerData | ||
| + | /tune/banger/sp_barricadewood_f_BREAK03.dgBangerData | ||
| + | /tune/banger/sp_barricadewood_f_BREAK04.dgBangerData | ||
| + | |||
| + | ==Specification== | ||
| + | The format is ASCII-based and made up of tag-value rows grouped in ''blocks'' between ''{'' and ''}'' symbols. | ||
The files start with a definition of the type of banger data given. None of the MM2 files use anything but ''type a'', like this: | The files start with a definition of the type of banger data given. None of the MM2 files use anything but ''type a'', like this: | ||
| Line 9: | Line 25: | ||
} | } | ||
| − | ''<tags>'' is replaced by a list of tags from the following table. The order of the tags | + | ''<tags>'' is replaced by a list of tags from the following table. The order of the tags is significant, but some tags may be omitted from the file, in that case the values from ''default.dgBangerData'' is used. |
{| class="wikitable" | {| class="wikitable" | ||
|+ Tags of the dgBangerData block | |+ Tags of the dgBangerData block | ||
| − | ! | + | !Tag!!Format!!Description |
|- | |- | ||
|AudioId||int||Index in a list of sound effects the object makes all the time? | |AudioId||int||Index in a list of sound effects the object makes all the time? | ||
| Line 56: | Line 72: | ||
The image files for particle effects are named ''fxptn.tex'' where ''n'' is an integer. MM2 has files from index one to index 16, excluding index 15. It is uncertain if more files can be added, but, at least 15 might be re-instated for new particle textures. See [[asBirthRule]] for more details. | The image files for particle effects are named ''fxptn.tex'' where ''n'' is an integer. MM2 has files from index one to index 16, excluding index 15. It is uncertain if more files can be added, but, at least 15 might be re-instated for new particle textures. See [[asBirthRule]] for more details. | ||
| + | |||
| + | ''Billboarding'' an object or an image means that it is always rotated so that it faces the camera regardless of the actual orientation of the object. The flags may apply restrictions to this, such as only allowing rotation around the Y-axis, etc. | ||
Latest revision as of 22:45, 6 August 2006
The dgBangerData files are used to define collision properties for PKG objects. These properties define how an object behaves when something collides with it.
The file names are derived from the name of the PKG and the names of the internal parts of it. The syntax is like this for the banger data of the entire object:
/tune/banger/<pkgname>.dgBangerData
and like this for the breakable parts:
/tune/banger/<pkgname>_<partname>.dgBangerData
For example, the banger data for the wooden barricade, /geometry/sp_barricadewood_f.pkg, of SF and London is defined in the following files:
/tune/banger/sp_barricadewood_f.dgBangerData /tune/banger/sp_barricadewood_f_BREAK01.dgBangerData /tune/banger/sp_barricadewood_f_BREAK02.dgBangerData /tune/banger/sp_barricadewood_f_BREAK03.dgBangerData /tune/banger/sp_barricadewood_f_BREAK04.dgBangerData
Specification
The format is ASCII-based and made up of tag-value rows grouped in blocks between { and } symbols.
The files start with a definition of the type of banger data given. None of the MM2 files use anything but type a, like this:
type: a
Next comes the main dgBangerData block:
dgBangerData {
<tags>
}
<tags> is replaced by a list of tags from the following table. The order of the tags is significant, but some tags may be omitted from the file, in that case the values from default.dgBangerData is used.
| Tag | Format | Description |
|---|---|---|
| AudioId | int | Index in a list of sound effects the object makes all the time? |
| Size | float float float | Width, height and depth of the bounding box around the object |
| CG | float float float | Center of gravity, rotation takes place around this point |
| NumGlows | int | Number of image light glow effects listed below using the GlowOffset tag. These effects are only active at night |
| GlowOffset | float float float | Position of a billboarded glow effect image |
| Mass | float | Mass of the object in kilograms, closely related to the objects weight |
| Elasticity | float | Controls the bounciness of the object |
| Friction | float | friction coefficient, determines how much force is required to slide along the surface of the object |
| ImpulseLimit2 | float | Force required to move the object |
| SpinAxis | int | Unknown, always set to 0 in MM2 files |
| Flash | int | Unknown |
| NumParts | int | Number of breakable parts in the object |
| BirthRule | block | Particle effect for collision, see below |
| TexNumber | int | Number of the particle texture map, see below |
| BillFlags | int | Flags controlling billboarding, 0, 64, 128 and 512 are used in MM2 files for unknown effects |
| YRadius | float | Bounding cylinder/sphere radius |
| ColliderId | int | Index in a list of sound effects the object makes when collided with. The list is defined in the file /aud/cardata/player/default_impacts.csv. |
| CollisionPrim | int | Defines the type of object used for collision detection, 0=boundary file, 1=bounding box, 2=cylinder with circular base, height is Y-component of Size and 3=sphere |
| CollisionType | int | Unknown, values 4, 16 and 48 are used in MM2 files |
The BirthRule block is the same as used in the asBirthRule files used to define particle effects caused by player vehicles.
The image files for particle effects are named fxptn.tex where n is an integer. MM2 has files from index one to index 16, excluding index 15. It is uncertain if more files can be added, but, at least 15 might be re-instated for new particle textures. See asBirthRule for more details.
Billboarding an object or an image means that it is always rotated so that it faces the camera regardless of the actual orientation of the object. The flags may apply restrictions to this, such as only allowing rotation around the Y-axis, etc.
