attachTo

1.001.501.000.50

GAGlobalGEGlobal

Hover & click on the images for description

Description

Description:

Attaches an object to another object.

• The offset is applied to the object center unless a memory point is provided, in which case the offset will be applied to the memory point position.
• If no offset is specified, the current offset between the two objects will be used.

ⓘ

• All direction commands, such as setDir, setVectorDirAndUp, etc. for an attached object should be used relative to the reference object's direction (i.e. in model space), e.g _attachedObj setDir 0 will make it face the same direction as the reference object, 90 face to the right, 180 face to the back, etc.
  
• Attached triggers only follow the direction of the object to which they are attached, not pitch or roll.

Multiplayer:

Use _attachedObj setPosWorld getPosWorld _attachedObj after setDir to synchronise set direction over the network (see setDir's page for its MP behaviour).

Groups:

Object Manipulation

Syntax

Syntax:

object1 attachTo [object2, offset, memPoint, followBoneRotation]

Parameters:

object1: Object - object to attach

object2: Object - object to attach to

offset: Array - (Optional) format PositionRelative

memPoint: String - (Optional) see ArmA: Selection Translations for czech selections names

since 2.02

followBoneRotation: Boolean - (Optional) follows the memory point's rotation (if attached to one)

Return Value:

Nothing

Examples

Example 1:

player attachTo [car, [0, 0, 1]];

Example 2:

player attachTo [tank, [0, -1, 0], "Usti hlavne"];

Example 3:

Automatic offset:

ammoCrate attachTo [player];

Example 4:

To set orientation of attached object use setVectorDirAndUp command:

_expl1 = "DemoCharge_Remote_Ammo" createVehicle position player; _expl1 attachTo [player, [-0.1, 0.1, 0.15], "Pelvis"]; _expl1 setVectorDirAndUp [[0.5, 0.5, 0], [-0.5, 0.5, 0]]; _expl2 = "DemoCharge_Remote_Ammo" createVehicle position player; _expl2 attachTo [player, [0, 0.15, 0.15], "Pelvis"]; _expl2 setVectorDirAndUp [[1, 0, 0], [0, 1, 0]]; _expl3 = "DemoCharge_Remote_Ammo" createVehicle position player; _expl3 attachTo [player, [0.1, 0.1, 0.15], "Pelvis"]; _expl3 setVectorDirAndUp [[0.5, -0.5, 0], [0.5, 0.5, 0]];

Example 5:

_drill attachTo [_worker, [0.0595885,-0.00950365,-0.13495], "RightForeArmRoll", true]; _drill setVectorDirAndUp [[0.536966,-0.00438141,-0.843605],[0.345872,0.913231,0.215406]]; _radio attachTo [_worker, [-0.100003,0.069064,0.153719], "Spine3", true]; _radio setVectorDirAndUp [[-0.144569,-0.48725,0.861354],[0.039712,0.866938,0.497072]];

Additional Information

See also:

attachedTo attachedObjects detach getRelPos attachObject attachedObject waypointAttachVehicle waypointAttachedVehicle lightAttachObject triggerAttachVehicle setVectorDir setVectorUp setVectorDirAndUp modelToWorld BIS_fnc_transformVectorDirAndUp

Notes

Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note

TeaCup - c

Posted on Sep 17, 2011 - 19:20 (UTC)

Some objects you cannot attach anything to. To be more precise, you can attach objects to them, but the behaviour is unexpected. For instance:

SuitcaseObject attachTo [FoldingTableObject, [0,0,0]];

You would expect the suitcase to jump to the pivot point of the table, and stick to it.
Instead, the suitcase will freeze in it is original position. Even if the table is moved, the suitcase will be unaffected: it will not follow the table, it will not even respond to actions it reacted to prior to being attached: pushing, being shot at, etc.. It's just an object frozen in space. In MP it is even weirder, the suitcase would turn invisible.
Dodgy objects when it comes to attaching things to them: most in Objects (small), Objects (signs), all of Objects (helpers) categories, etc.

Pixinger77 - c

Posted on Mar 28, 2014 - 16:22 (UTC)

If you attach an explosive charge to an object (e.g. ammobox), the charge will not detonate when you simply set the damage to 1. You must detach it before.

private _target = myAmmoBox; // create and attach charge private _charge = "DemoCharge_Remote_Ammo_Scripted" createVehicle position player; _charge attachTo [_target, [0, 0, 0.2]]; _charge setVectorDirAndUp [[0.5,0.5,0], [-0.5,0.5,0]]; // now detonate charge detach _charge; // Important! _charge setDamage 1;

ffur2007slx2_5 - c

Posted on Jun 01, 2014 - 23:00 (UTC)

1.20

attachTo overwrites setVectorDirAndUp if attached obj was changed to attach another one.

_obj attachTo [_logic,[0, 0, 0]]; _obj setVectorDirAndUp [[0, 1, 0], [0, 0, -1]]; _obj attachTo [_logic, [0, 0, 2]]; // vector no changes _obj attachTo [_anotherOne, [0, 0, 0]]; // vector changes to default

ondrejkuzel - c

Posted on Sep 25, 2014 - 10:00 (UTC)

Attaching an object does not update the accessibility of a place for the AI. The command should not be used for positioning large static objects - the AI will simply walk through such objects.

Demellion - c

Posted on Sep 01, 2016 - 17:54 (UTC)

Using attachTo with objects that have ragdoll physics (such as ammo boxes, containers, etc.) may cause unexpected behaviour. When you do so, if the attached object intersect origin object, origin object may gain some enormous collision properties even if the collision model for the attached object is not present localy to origin object, until detached. Vehicles may start flipping with no mass calculation (ie tank might fly), player object might gain infinite Z-vector velocity on any interaction with terrain relief and other objects.

R3vo - c

Posted on Aug 13, 2019 - 12:55 (UTC)

When attaching an unit which is playing an animation to a static object, the animation becomes laggy. Presumably because the update frequency of the static object is used.