Difference between revisions of "Camera Commands"

From Catznip
Jump to navigation Jump to search
(Created page with "__NO_TOC__ Camera manipulation commands follow the same concept as {{RLVaCommand|setenv||}} where a single object can exclusively lock control of the camera. '''Important:''...")
 
Line 1: Line 1:
__NO_TOC__
+
__NOTOC__
  
 
Camera manipulation commands follow the same concept as {{RLVaCommand|setenv||}} where a single object can exclusively lock control of the camera.
 
Camera manipulation commands follow the same concept as {{RLVaCommand|setenv||}} where a single object can exclusively lock control of the camera.

Revision as of 15:03, 5 June 2016


Camera manipulation commands follow the same concept as @setenv where a single object can exclusively lock control of the camera.

Important: while existing camera commands that don't fit the setcam_XXX family will currently (silently) translate to their new counterparts this is only a courtesy and these synonyms will be removed in a future release. Please use only @setcam_XXX in any of your products.

While we don't anticipate major changes the final implementation and behaviour of these commands isn't set in stone and subject to your feedback.

@setcam=<n|y>

Only one object can hold this behaviour at a given time (debug output will show "locked" as the failure message on subsequent attempts). When an object holds the lock, all camera commands from all other objects will be ignored; when the object releases the lock all other camera behaviours will be restored.

@setcam_eyeoffset

@setcam_focus

@setcam_focusoffset

@setcam_fov

@setcam_fovmin

@setcam_fovmax

@setcam_unlock