Element/COL: Difference between revisions
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
The [[COL]] class represents a RenderWare Collision File ( | The [[COL]] class represents a RenderWare Collision File (.col) loaded by the client, which can be imported into a custom model to define its collisions. | ||
A .col file can contain one or more collision models. Normally, San Andreas assigns each collision model in a file to a geometry model through the model name that is embedded in the collision model. However in MTA, you can assign any .col file to any model ID; the names are ignored. To prevent loading multiple collision models into one model ID, MTA only loads the first collision model of a .col file and ignores the rest. Therefore, if you have a .col file containing multiple collision models, you will need to split it into multiple files, with one model per file, and then load and import each of those files using the appropriate scripting functions. To split a .col file into multiple files, you can use [http://www.steve-m.com/tags/colleditor2/ CollEditor2]. | |||
Collision data can also be embedded in DFF files. At the moment, vehicle collision replacement works with DFF embedded collisions only. | Collision data can also be embedded in DFF files. At the moment, vehicle collision replacement works with DFF embedded collisions only. | ||
Revision as of 21:42, 20 May 2009
The COL class represents a RenderWare Collision File (.col) loaded by the client, which can be imported into a custom model to define its collisions.
A .col file can contain one or more collision models. Normally, San Andreas assigns each collision model in a file to a geometry model through the model name that is embedded in the collision model. However in MTA, you can assign any .col file to any model ID; the names are ignored. To prevent loading multiple collision models into one model ID, MTA only loads the first collision model of a .col file and ignores the rest. Therefore, if you have a .col file containing multiple collision models, you will need to split it into multiple files, with one model per file, and then load and import each of those files using the appropriate scripting functions. To split a .col file into multiple files, you can use CollEditor2.
Collision data can also be embedded in DFF files. At the moment, vehicle collision replacement works with DFF embedded collisions only.
Related scripting functions
Client
- engineAddImage
- engineApplyShaderToWorldTexture
- engineFreeModel
- engineGetModelFlags
- engineGetModelIDFromName
- engineGetModelLODDistance
- engineGetModelNameFromID
- engineGetModelPhysicalPropertiesGroup
- engineGetModelTextureNames
- engineGetModelTextures
- engineGetModelTXDID
- engineGetModelVisibleTime
- engineGetObjectGroupPhysicalProperty
- engineGetSurfaceProperties
- engineGetVisibleTextureNames
- engineImageGetFilesCount
- engineImageGetFiles
- engineImageGetFile
- engineImageLinkDFF
- engineImageLinkTXD
- engineImportTXD
- engineLoadCOL
- engineLoadDFF
- engineLoadIMG
- engineLoadIFP
- engineLoadTXD
- engineRemoveImage
- engineRemoveShaderFromWorldTexture
- engineReplaceAnimation
- engineReplaceCOL
- engineReplaceModel
- engineRequestModel
- engineResetModelFlags
- engineResetModelLODDistance
- engineResetSurfaceProperties
- engineRestoreAnimation
- engineRestoreCOL
- engineRestoreDFFImage
- engineRestoreModel
- engineRestoreModelPhysicalPropertiesGroup
- engineRestoreObjectGroupPhysicalProperties
- engineRestoreTXDImage
- engineRestreamWorld
- engineSetAsynchronousLoading
- engineSetModelFlag
- engineSetModelFlags
- engineSetModelLODDistance
- engineSetModelPhysicalPropertiesGroup
- engineSetModelVisibleTime
- engineSetObjectGroupPhysicalProperty
- engineSetSurfaceProperties
- engineStreamingFreeUpMemory
- engineStreamingGetUsedMemory