Jump to navigation Jump to search
Hover & click on the images for descriptions
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.
_attachedObj setPos getPos _attachedObjafter setDir to synchronise set direction over the network (see setDir's page for its MP behaviour).
- object1 attachTo [object2, offset, memPoint]
- 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
- Return Value:
- 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]];
- See also:
- Posted on September 17, 2011 - 19:20
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's 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's 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.
- Posted on March 28, 2014 - 16:22
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;
- Posted on 1 Jun, 2014 - 2300
(ArmA3 ver 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
- Posted on September 25, 2014 - 10:00
- 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.
- Posted on September 1, 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.
- Posted on August 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.