Element/COL - Revision history

EOFIK: Добавление языков

2021-04-14T21:43:15Z

Добавление языков

← Older revision		Revision as of 21:43, 14 April 2021
Line 10:		Line 10:
	{{Engine_functions}}		{{Engine_functions}}

			[[en:Element/COL]]
			[[ru:Element/COL]]
	[[hu:Element/COL]]		[[hu:Element/COL]]

Surge at 20:30, 8 December 2018

2018-12-08T20:30:38Z

← Older revision		Revision as of 20:30, 8 December 2018
Line 9:		Line 9:
	===Client===		===Client===
	{{Engine_functions}}		{{Engine_functions}}

			[[hu:Element/COL]]

Arc at 21:42, 20 May 2009

2009-05-20T21:42:48Z

← Older revision		Revision as of 21:42, 20 May 2009
Line 2:		Line 2:
	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.		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].		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/downloads/tools/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.

Arc at 21:42, 20 May 2009

2009-05-20T21:42:27Z

← Older revision		Revision as of 21:42, 20 May 2009
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	The [[COL]] class represents a RenderWare Collision File (~~COL3~~) loaded by the client, which can be imported into a custom model to define its collisions.		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.

Borov at 16:20, 8 May 2008

2008-05-08T16:20:23Z

← Older revision		Revision as of 16:20, 8 May 2008
Line 7:		Line 7:
	===Client===		===Client===
	{{Engine_functions}}		{{Engine_functions}}
	~~[[Category:Scripting Concepts]]~~

Borov at 16:18, 8 May 2008

2008-05-08T16:18:23Z

← Older revision		Revision as of 16:18, 8 May 2008
Line 7:		Line 7:
	===Client===		===Client===
	{{Engine_functions}}		{{Engine_functions}}
			[[Category:Scripting Concepts]]

Jbeta: COL moved to Element/COL: Now an element

2007-11-21T23:15:05Z

COL moved to Element/COL: Now an element

← Older revision

Revision as of 23:15, 21 November 2007

Jbeta at 22:32, 30 August 2007

2007-08-30T22:32:33Z

← Older revision		Revision as of 22:32, 30 August 2007
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	The [[~~col~~]] class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions.		The [[COL]] class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions.

	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.

Jbeta at 22:32, 30 August 2007

2007-08-30T22:32:17Z

← Older revision		Revision as of 22:32, 30 August 2007
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	The ~~'''~~col~~'''~~ class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions.		The [[col]] class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions.

	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.

Jbeta: New page: NOTOC The '''col''' class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions. Collision data can al...

2007-08-28T15:02:04Z

New page: __NOTOC__ The '''col''' class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions. Collision data can al...

New page

__NOTOC__
The '''col''' class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions.

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===
{{Engine_functions}}

Element/COL - Revision history

EOFIK: Добавление языков

Surge at 20:30, 8 December 2018

Arc at 21:42, 20 May 2009

Arc at 21:42, 20 May 2009

Borov at 16:20, 8 May 2008

Borov at 16:18, 8 May 2008

Jbeta: COL moved to Element/COL: Now an element

Jbeta at 22:32, 30 August 2007

Jbeta at 22:32, 30 August 2007

Jbeta: New page: __NOTOC__ The '''col''' class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions. Collision data can al...

Jbeta: New page: NOTOC The '''col''' class represents a RenderWare Collision File (COL3) loaded by the client, which can be imported into a custom model to define its collisions. Collision data can al...