Includes:
Field of View (fov)/Timescale: specifies if the game commands used to define the Fov and the Timescale of each point will be included in the scripts generation. If you uncheck it, ct3d will include only the fov/ts of the first control point one time at beginning of the script. All others will be ignored.
Messages:
specifies if the progression of the script read will be printed in the game console.
Camera mode:
Allows you to specify what method the game uses to define the camera view angles. In ‘Free’ mode, the values defined in the data grid will be used. The ‘LookPlayer’ mode allows you to specify a player ID that the camera must look at (in this case the specified angle values are ignored).
Pause:
Allows you to pause the execution of the curve in the game. In effect, the game engine doesn’t allow you to stop the execution of a script. With this option, you can. It avoids to wait the end of the execution if the curve is not suitable. Choose a key that you will use to resume the execution.
Script to execute:
before:script that will be executed before that the camera starts. after: script that will be executed after that the camera stops.
AutoStart (EtPro only):
This feature allows to execute your camera script at specific time (exploit the 'exec_at_time' ETpro command).
checkbox:
If checked, your camera script will be executed at the specified time. That is, you load a demo and type “exec cam\cam.cfg” in the game console. When the time is reached,
the camera will start (If you change the frame value, regenerate the script by clicking on the “create” button). If it’s unchecked, when you execute cam\cam.cfg, the camera will start immediately.
textfield:
Use this field to insert the value in millisecond that define when your camera will start. Insert a value that you obtained from the in-game frame counter. To show this counter in the game, type 'show_framecounter 1' in the console or 'show_framecounter 2' to freeze it. note: the highest value accepted by the game is 2147483647ms. h:m:s.ms: This time representation don't correspond to the in-game timer, because the frames counter don’t starts at 0 when the demo begin. So don't compare the in-game round timer (cg_drawRoundTimer 1) to those values.. Just use those fields to easily adjust the number of milliseconds that you inserted.
Create:
Allows you to generate ‘cfg’ scripts that will be executed in the game. Choose a location and a name for your script. By default, use the cam folder (“etpro\cam\” for RTCW ET or “defrag\cam\” for Quake 3) and name it “cam”. Then, you simply type “exec cam\cam” in the game console and the camera script will be executed. Note : given that the game engine limits the size of ‘cfg’ script to 16ko, ct3D will generates several scripts, but only the first must be executed.