This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
arma:howto_animate_model [2009-04-17 12:01] snakeman added animate cargo door tips. |
arma:howto_animate_model [2017-10-06 22:08] snakeman http to https switch. |
||
---|---|---|---|
Line 15: | Line 15: | ||
Besides adding selections (same as in OFP but in ArmA bone selections should never overlap) you also need to add a following named property to your first resolution LOD (press **ALT-P** to open named properties window): | Besides adding selections (same as in OFP but in ArmA bone selections should never overlap) you also need to add a following named property to your first resolution LOD (press **ALT-P** to open named properties window): | ||
- | <code> | + | <code cpp> |
property name: autocenter | property name: autocenter | ||
value: 0 | value: 0 | ||
Line 47: | Line 47: | ||
A bone is defined by using two strings: | A bone is defined by using two strings: | ||
- | <code> | + | <code cpp> |
:"bone","" | :"bone","" | ||
</code> | </code> | ||
Line 57: | Line 57: | ||
**Example** | **Example** | ||
- | <code> | + | <code cpp> |
skeletonBones[]= | skeletonBones[]= | ||
{ | { | ||
Line 69: | Line 69: | ||
The second argument (empty in the example above) is used for linking two bones: | The second argument (empty in the example above) is used for linking two bones: | ||
- | <code> | + | <code cpp> |
:"bone1","bone2" | :"bone1","bone2" | ||
</code> | </code> | ||
Line 77: | Line 77: | ||
**Example** | **Example** | ||
- | <code> | + | <code cpp> |
skeletonBones[]= | skeletonBones[]= | ||
{ | { | ||
Line 89: | Line 89: | ||
You can not link more than two bones in a row! If you do something like | You can not link more than two bones in a row! If you do something like | ||
- | <code> | + | <code cpp> |
"bone1","bone2","bone3" | "bone1","bone2","bone3" | ||
</code> | </code> | ||
Line 99: | Line 99: | ||
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): | ||
- | <code> | + | <code cpp> |
skeletonBones[]= | skeletonBones[]= | ||
{ | { | ||
Line 112: | Line 112: | ||
**cfgSkeletons Example** | **cfgSkeletons Example** | ||
- | <code> | + | <code cpp> |
class cfgSkeletons | class cfgSkeletons | ||
{ | { | ||
Line 155: | Line 155: | ||
**Example** | **Example** | ||
- | <code> | + | <code cpp> |
sections[]= | sections[]= | ||
{ | { | ||
Line 195: | Line 195: | ||
**Example** | **Example** | ||
- | <code> | + | <code cpp> |
class mainRotor | class mainRotor | ||
{ | { | ||
Line 219: | Line 219: | ||
As a short example, the wheels would need "rotationX" as animation type. | As a short example, the wheels would need "rotationX" as animation type. | ||
- | {{http://tactical.nekromantix.com/images/wiki/howtoanimmodel_axes.jpg}} | + | {{https://pmc.editing.wiki/images/howtoanimmodel_axes.jpg}} |
**cfgModels example** | **cfgModels example** | ||
- | <code> | + | <code cpp> |
class cfgModels | class cfgModels | ||
{ | { |