ArmA: Armed Assault: How to animate a model - Revision history

Lou Montana: Text replacement - " ( class [a-zA-Z0-9_]+): ([a-zA-Z0-9_]+ *) " to " $1 : $2 "

2023-12-06T09:58:23Z

Text replacement - " ( *class [a-zA-Z0-9_]+): *([a-zA-Z0-9_]+ *) " to " $1 : $2 "

← Older revision		Revision as of 11:58, 6 December 2023
Line 332:		Line 332:
	};		};
	};		};
	class OFPEC_TAG_MyPinkElephant:SomeBaseClass		class OFPEC_TAG_MyPinkElephant : SomeBaseClass
	{		{
	// ...		// ...
Line 356:		Line 356:
	statement = "this animate [""OFPEC_TAG_MyPinkElephant_SlidingDoor"", 1]; this say ""OFPEC_TAG_ElephantOpenSound""";		statement = "this animate [""OFPEC_TAG_MyPinkElephant_SlidingDoor"", 1]; this say ""OFPEC_TAG_ElephantOpenSound""";
	};		};
	class OFPEC_TAG_CloseDoor1:OFPEC_TAG_OpenDoor1		class OFPEC_TAG_CloseDoor1 : OFPEC_TAG_OpenDoor1
	{		{
	displayName = "Close Sliding door";		displayName = "Close Sliding door";

Lou Montana: Text replacement - "[[Image:" to "[[File:"

2023-11-20T22:11:53Z

Text replacement - "[[Image:" to "[[File:"

← Older revision		Revision as of 00:11, 21 November 2023
Line 250:		Line 250:

	As a short example, the wheels would need "rotationX" as animation type.		As a short example, the wheels would need "rotationX" as animation type.
	\| [[~~Image~~:Howtoanimmodel axes.jpg]]		\| [[File:Howtoanimmodel axes.jpg]]
	\|}		\|}

Lou Montana: Some wiki formatting

2023-03-10T10:17:52Z

Some wiki formatting

Show changes

Lou Montana: Some wiki formatting

2022-07-27T17:37:37Z

Some wiki formatting

Show changes

Lou Montana: Text replacement - "" to ""

2021-06-19T14:25:38Z

Text replacement - "<syntaxhighlight lang=cpp>" to "<syntaxhighlight lang="cpp">"

← Older revision		Revision as of 16:25, 19 June 2021
Line 58:		Line 58:

	===== Example =====		===== Example =====
	<syntaxhighlight lang=cpp>skeletonBones[]=		<syntaxhighlight lang="cpp">skeletonBones[]=
	{		{
	"bone1","", //defines bone1		"bone1","", //defines bone1
Line 72:		Line 72:

	===== Example =====		===== Example =====
	<syntaxhighlight lang=cpp>skeletonBones[]=		<syntaxhighlight lang="cpp">skeletonBones[]=
	{		{
	"turret_x","", // defines bone turret_x		"turret_x","", // defines bone turret_x
Line 82:		Line 82:
	You can not link more than two bones in a row!<br>		You can not link more than two bones in a row!<br>
	If you do something like		If you do something like
	<syntaxhighlight lang=cpp> "bone1","bone2","bone3"</syntaxhighlight>		<syntaxhighlight lang="cpp"> "bone1","bone2","bone3"</syntaxhighlight>
	this will result in an error, as Armed Assault interprets this as		this will result in an error, as Armed Assault interprets this as
	*defining "bone1" which is linked to "bone2"		*defining "bone1" which is linked to "bone2"
Line 88:		Line 88:

	However, it should be possible to use a syntax like this (not tested yet):		However, it should be possible to use a syntax like this (not tested yet):
	<syntaxhighlight lang=cpp>skeletonBones[]=		<syntaxhighlight lang="cpp">skeletonBones[]=
	{		{
	"bone1","bone2", // defines bone "bone1" and makes it linked to "bone2"		"bone1","bone2", // defines bone "bone1" and makes it linked to "bone2"
Line 100:		Line 100:

	=== cfgSkeletons Example ===		=== cfgSkeletons Example ===
	<syntaxhighlight lang=cpp>class cfgSkeletons		<syntaxhighlight lang="cpp">class cfgSkeletons
	{		{
	class BWMod_Tiger_Skeleton		class BWMod_Tiger_Skeleton
Line 151:		Line 151:

	==== Example ====		==== Example ====
	<syntaxhighlight lang=cpp>sections[]=		<syntaxhighlight lang="cpp">sections[]=
	{		{
	"mainRotor","mainRotor_static","mainRotor_blur","mainRotor_dive",		"mainRotor","mainRotor_static","mainRotor_blur","mainRotor_dive",
Line 216:		Line 216:

	==== Example ====		==== Example ====
	<syntaxhighlight lang=cpp>class mainRotor		<syntaxhighlight lang="cpp">class mainRotor
	{		{
	type="rotationY"; //rotation around the Y axis		type="rotationY"; //rotation around the Y axis
Line 250:		Line 250:
	*Similar to any other classes in any standard config.cpp of any pbo, it is possible, albeit less likely, to have same class(es) over declared in multiple folders. This is typical if you are running more than one project on the p: drive. Far better, you always use an OFPEC_TAG name		*Similar to any other classes in any standard config.cpp of any pbo, it is possible, albeit less likely, to have same class(es) over declared in multiple folders. This is typical if you are running more than one project on the p: drive. Far better, you always use an OFPEC_TAG name

	<syntaxhighlight lang=cpp>class OFPEC_TAG_MyModelSkeleton</syntaxhighlight>		<syntaxhighlight lang="cpp">class OFPEC_TAG_MyModelSkeleton</syntaxhighlight>


Line 272:		Line 272:

	This is very prevalent, very common, and very 'ok' when you have a generalised base class that deals with four standard doors, only one of which appears in a specific model.		This is very prevalent, very common, and very 'ok' when you have a generalised base class that deals with four standard doors, only one of which appears in a specific model.
	<syntaxhighlight lang=cpp>		<syntaxhighlight lang="cpp">
	class WideDoor{...		class WideDoor{...
	class FrontDoor{...		class FrontDoor{...

Lou Montana: Text replacement - "};" to "}; "

2021-05-25T09:02:31Z

Text replacement - "};</syntaxhighlight>" to "}; </syntaxhighlight>"

← Older revision		Revision as of 11:02, 25 May 2021
Line 62:		Line 62:
	"bone1","", //defines bone1		"bone1","", //defines bone1
	"bone2","" //defines bone2		"bone2","" //defines bone2
	};</syntaxhighlight>		};
			</syntaxhighlight>

	==== Linked bones ====		==== Linked bones ====
Line 75:		Line 76:
	"turret_x","", // defines bone turret_x		"turret_x","", // defines bone turret_x
	"turret_y","turret_x" // defines bone turret_y and makes it linked to bone turret_x		"turret_y","turret_x" // defines bone turret_y and makes it linked to bone turret_x
	};</syntaxhighlight>		};
			</syntaxhighlight>

	'''Attention:'''<br>		'''Attention:'''<br>
Line 91:		Line 93:
	"bone2","bone3", // defines bone "bone2" and makes it linked to "bone3"		"bone2","bone3", // defines bone "bone2" and makes it linked to "bone3"
	"bone3","" // defines bone "bone3".		"bone3","" // defines bone "bone3".
	};</syntaxhighlight>		};
			</syntaxhighlight>

	In conclusion, "bone1" is linked to "bone2", which is linked to "bone3".<br>		In conclusion, "bone1" is linked to "bone2", which is linked to "bone3".<br>
Line 116:		Line 119:
	};		};
	};		};
	};</syntaxhighlight>		};
			</syntaxhighlight>

	== cfgModels ==		== cfgModels ==
Line 153:		Line 157:

	"turret_RMK_x","turret_RMK_y"		"turret_RMK_x","turret_RMK_y"
	};</syntaxhighlight>		};
			</syntaxhighlight>

	=== Animations ===		=== Animations ===
Line 223:		Line 228:
	angle0=0;		angle0=0;
	angle1="rad -360";		angle1="rad -360";
	};</syntaxhighlight>		};
			</syntaxhighlight>

	==== Axes ====		==== Axes ====

Lou Montana: spaces → tab

2021-04-25T19:24:18Z

spaces → tab

Show changes

Lou Montana: Text replacement - "^=+ * " to ""

2021-01-31T18:55:15Z

Text replacement - "^=+ * " to ""

← Older revision		Revision as of 20:55, 31 January 2021
Line 1:		Line 1:
	=
	'''Attention:'''		'''Attention:'''
	This article is a tutorial on how to animate parts of your model (e.g. wheels, rotors, etc.).		This article is a tutorial on how to animate parts of your model (e.g. wheels, rotors, etc.).

Lou Montana: Text replacement - "^=+ [Ii]ntroduction =+ * *" to ""

2021-01-31T18:48:37Z

Text replacement - "^=+ *[Ii]ntroduction *=+ * *" to ""

← Older revision		Revision as of 20:48, 31 January 2021
Line 1:		Line 1:
	~~==Introduction=~~=		=
	'''Attention:'''		'''Attention:'''
	This article is a tutorial on how to animate parts of your model (e.g. wheels, rotors, etc.).		This article is a tutorial on how to animate parts of your model (e.g. wheels, rotors, etc.).

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "

2021-01-31T17:31:13Z

Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

← Older revision		Revision as of 19:31, 31 January 2021
Line 19:		Line 19:
	If you encounter a bug when your weapon bones fall apart after you dropp it to the ground the reason might be lack of Geometry or View - pilot LODs.		If you encounter a bug when your weapon bones fall apart after you dropp it to the ground the reason might be lack of Geometry or View - pilot LODs.

	==model.cfg==		== model.cfg ==

	According to the article about [[Model Config]], the cfgSkeletons and cfgModels class should be part of a model.cfg file which is located in the addon pbo file.<br>		According to the article about [[Model Config]], the cfgSkeletons and cfgModels class should be part of a model.cfg file which is located in the addon pbo file.<br>
Line 27:		Line 27:
	However, the first method is prefered and should always be used when releasing your addon.		However, the first method is prefered and should always be used when releasing your addon.

	==cfgSkeletons==		== cfgSkeletons ==
	The ''cfgSkeletons'' class defines, as mentioned before, the bones (<nowiki>=</nowiki> animated selections) of a vehicle.		The ''cfgSkeletons'' class defines, as mentioned before, the bones (<nowiki>=</nowiki> animated selections) of a vehicle.

Line 47:		Line 47:
	\|}		\|}

	===Defining a bone===		=== Defining a bone ===
	Bones are defined in the skeletonBones[]-array which is made of a list of unsorted bones. Each bone is the name of a selection you want to animate.		Bones are defined in the skeletonBones[]-array which is made of a list of unsorted bones. Each bone is the name of a selection you want to animate.

	====A single bone====		==== A single bone ====
	A bone is defined by using two strings:		A bone is defined by using two strings:
	:"bone",""		:"bone",""
Line 57:		Line 57:
	'''Attention:''' Do not leave out the second string as this will lead to errors! (see [[ArmA: How to animate a model#Linked Bones\|linked bones]] for more information on the second string argument)		'''Attention:''' Do not leave out the second string as this will lead to errors! (see [[ArmA: How to animate a model#Linked Bones\|linked bones]] for more information on the second string argument)

	=====Example=====		===== Example =====
	<syntaxhighlight lang=cpp>skeletonBones[]=		<syntaxhighlight lang=cpp>skeletonBones[]=
	{		{
Line 64:		Line 64:
	};</syntaxhighlight>		};</syntaxhighlight>

	====Linked bones====		==== Linked bones ====
	The second argument (empty in the example above) is used for linking two bones:<br>		The second argument (empty in the example above) is used for linking two bones:<br>
	:"bone1","bone2"		:"bone1","bone2"
Line 70:		Line 70:
	Linking is used to make the animation of "bone1" depending on the movement of "bone2". If you e.g. have a turret, you have to make use of linking here, because the up and down movement of the turrets weapon is typically influenced by left and right movement of the turret:		Linking is used to make the animation of "bone1" depending on the movement of "bone2". If you e.g. have a turret, you have to make use of linking here, because the up and down movement of the turrets weapon is typically influenced by left and right movement of the turret:

	=====Example=====		===== Example =====
	<syntaxhighlight lang=cpp>skeletonBones[]=		<syntaxhighlight lang=cpp>skeletonBones[]=
	{		{
Line 96:		Line 96:
	So "bone1" should be depending on the movement of both, "bone2" and "bone3".		So "bone1" should be depending on the movement of both, "bone2" and "bone3".

	===cfgSkeletons Example===		=== cfgSkeletons Example ===
	<syntaxhighlight lang=cpp>class cfgSkeletons		<syntaxhighlight lang=cpp>class cfgSkeletons
	{		{
Line 118:		Line 118:
	};</syntaxhighlight>		};</syntaxhighlight>

	==cfgModels==		== cfgModels ==
	The cfgModels class is used to declare the selections of a model you want to animate or access via the setObjectTexture command. Since ArmA, the cfgModels class has been extended an is now used to define all animations of a model.		The cfgModels class is used to declare the selections of a model you want to animate or access via the setObjectTexture command. Since ArmA, the cfgModels class has been extended an is now used to define all animations of a model.

Line 143:		Line 143:
	\|}		\|}

	===Sections===		=== Sections ===
	A section is the same as a selection: a part of the model which may be animated or changed via the setObjectTexture command. To define selections in your modelclass make use of the section[]-array. This array is an unordered list of all selections you want to use in the ways described above.		A section is the same as a selection: a part of the model which may be animated or changed via the setObjectTexture command. To define selections in your modelclass make use of the section[]-array. This array is an unordered list of all selections you want to use in the ways described above.

	====Example====		==== Example ====
	<syntaxhighlight lang=cpp>sections[]=		<syntaxhighlight lang=cpp>sections[]=
	{		{
Line 155:		Line 155:
	};</syntaxhighlight>		};</syntaxhighlight>

	===Animations===		=== Animations ===
	To define animations for your model, you have to make use of the class animations in your modelclass.		To define animations for your model, you have to make use of the class animations in your modelclass.
	Each animation is a subclass in the class animations with a userdefinable name and consists of the following parameters:		Each animation is a subclass in the class animations with a userdefinable name and consists of the following parameters:
Line 201:		Line 201:
	\|}		\|}

	====Attention====		==== Attention ====
	I am assuming that each source is returning a value between 0 and 1 (the ''animationPhase'') which is used to animate your selection. Some may even return a value from -1 to 1:		I am assuming that each source is returning a value between 0 and 1 (the ''animationPhase'') which is used to animate your selection. Some may even return a value from -1 to 1:
	*If using source="speed", the source is returning 0 when the vehicle is not moving and 1 when the vehicle is moving at maximum speed.		*If using source="speed", the source is returning 0 when the vehicle is not moving and 1 when the vehicle is moving at maximum speed.
Line 210:		Line 210:
	The same goes for the mainGun selection.		The same goes for the mainGun selection.

	====Example====		==== Example ====
	<syntaxhighlight lang=cpp>class mainRotor		<syntaxhighlight lang=cpp>class mainRotor
	{		{
Line 225:		Line 225:
	};</syntaxhighlight>		};</syntaxhighlight>

	====Axes====		==== Axes ====
	{\|		{\|
	\|valign="top"\|Since the axes seem a bit messed up when using ''rotationX'', ''rotationY'', ''rotationZ'', ''translationX'', ''translationY'', ''translationZ'', here is a small image of how the axes are arranged.		\|valign="top"\|Since the axes seem a bit messed up when using ''rotationX'', ''rotationY'', ''rotationZ'', ''translationX'', ''translationY'', ''translationZ'', here is a small image of how the axes are arranged.
Line 237:		Line 237:
	\|}		\|}

	===Rules Of Engagement===		=== Rules Of Engagement ===

	====cfgSkeletons====		==== cfgSkeletons ====
	*Binarise gets confused if your cfgSkeletons classname is same as your cfgModels.		*Binarise gets confused if your cfgSkeletons classname is same as your cfgModels.
	**Declare your skeleton class as MyModelSkeleton vs MyModel		**Declare your skeleton class as MyModelSkeleton vs MyModel
Line 255:		Line 255:
	It is 'ok' to format for the general case. The only effect is that this non-existent bone will appear in the binary p3d as part of the skeleton list. No harm done.		It is 'ok' to format for the general case. The only effect is that this non-existent bone will appear in the binary p3d as part of the skeleton list. No harm done.

	====cfgModels====		==== cfgModels ====

	*sections[]= have nothing to do with this document. They are a list of NamedSelections, from which, [[setObjectTexture]] can be used in-game. They are part of hiddenselections[]= and are, confusingly, not related to skeletons and animations. If a non-existent NamedSelection is, in fact, listed in this segment, it is ignored, and not present in the binary model.		*sections[]= have nothing to do with this document. They are a list of NamedSelections, from which, [[setObjectTexture]] can be used in-game. They are part of hiddenselections[]= and are, confusingly, not related to skeletons and animations. If a non-existent NamedSelection is, in fact, listed in this segment, it is ignored, and not present in the binary model.
Line 278:		Line 278:
	If the bone IS declared in the skeleton but doesn't actually exist in the model. The cfgModel class IS binarised (probably not what you want to happen).		If the bone IS declared in the skeleton but doesn't actually exist in the model. The cfgModel class IS binarised (probably not what you want to happen).

	===User Animation===		=== User Animation ===
	<syntaxhighlight lang=cpp>		<syntaxhighlight lang=cpp>
	class Rotation; //very standard, most often defined in the first model.cfg of the p:tree		class Rotation; //very standard, most often defined in the first model.cfg of the p:tree
Line 369:		Line 369:
	</syntaxhighlight>		</syntaxhighlight>

	===cfgModels example===		=== cfgModels example ===
	<syntaxhighlight lang=cpp>class cfgModels		<syntaxhighlight lang=cpp>class cfgModels
	{		{

ArmA: Armed Assault: How to animate a model - Revision history

Lou Montana: Text replacement - " ( *class [a-zA-Z0-9_]+): *([a-zA-Z0-9_]+ *) " to " $1 : $2 "

Lou Montana: Text replacement - "[[Image:" to "[[File:"

Lou Montana: Some wiki formatting

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "" to ""

Lou Montana: Text replacement - "};" to "}; "

Lou Montana: spaces → tab

Lou Montana: Text replacement - "^=+ * " to ""

Lou Montana: Text replacement - "^=+ *[Ii]ntroduction *=+ * *" to ""

Lou Montana: Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

Lou Montana: Text replacement - " ( class [a-zA-Z0-9_]+): ([a-zA-Z0-9_]+ *) " to " $1 : $2 "

Lou Montana: Text replacement - "^=+ [Ii]ntroduction =+ * *" to ""

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "