According to BIKI camSetDir requires 0-360 angle parameter. This is false as ArmA 3 complains it needs array. In fact after some experiments I can confirm it indeed requires a vector direction array i.e. [0,0,1] to point up [0,1,0] to point north etc. [0,0,0] points north as well.
Anyway the command requires camCommit. As soon as camCommit executed it starts to spin and oscillation frequency depends on camCommit value which pretty much makes this otherwise very useful command totally unusable.
Open debug console in editor type
_pos = +(position player); _pos set [2, 100]; _cam = "camera" camCreate _pos; _cam cameraEffect ["EXTERNAL", "BACK"]; _cam camSetDir [-1,0,0]; _cam camCommit 0;
after execution the camera point in the correct direction, as soon as you hide debug console it starts spinning.
other values to try
_cam camSetDir [0,0,1];
_cam camSetDir [0,0,-1];
_cam camSetDir [1,1,0];
You can achieve the same result by using camSetTarget instead. Example:
_cam camSetTarget [(_pos select 0) + 1, (_pos select 1), (_pos select 2)];
Problem confirmed. A discuss about here : http://forums.bistudio.com/showthread.php?153979-camSetDir-is-bugged-please-upvote
We can use setVectorDirAndUp (or setVectorDir) for 3D vector.
Or setDir for azimut angle.
Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.
If this issue is still relevant in current dev build, please re-post.
@ceeeb camSetTarget is not the same, as camSetDir works with camCommit and therefore should allow for cam animation. Also camSetTarget [0,0,0] expected to turn camera towards map origin, but instead is ignored; camSetTarget [0,0,1], i.e. quite close but different from [0,0,0] would work though.
I'm reopening this as japapatramtara has recently attempted to fix the command. Will see how it goes.
closing as not fixable. it was broken for a long time and recent attempt to fix it went nowhere
Just found this didn't work. Proposed workarround: http://forums.bistudio.com/showthread.php?191470-Arma-3-camSetDir-workarround&p=2931463#post2931463