Scripting G-Force
G-Force has scripting services that allow you to repeat G-Force performances and allow you to synchronize G-Force events to a timeline or "timecode". A short example script is already included to demonstrate G-Force scripts, and you can start it by pressing CTRL and the '4' key. The example script causes the text "The End" to appear right before it ends, so you'll know when it's over. If you find the folder named "Scripts" and open the file "4 Key" using a text editor, you'll notice how time indexes are on the left and keystrokes and config names are on the right. Once a script is started/called, the commands on the right are executed along the timeline on the left.
There's two ways to start a script. The first way is to name a script "X Key" and press CTRL and the X key (or whatever key you want). The other way to start a script is to call it by name from inside another script.
The format of command lines (ie, the lines that appear to the right of the time indexes) are keystrokes or config names separated by semicolons. In other words, whatever is between semicolons is one of two things: a single character (as if you typed it in from the keyboard) or the filename of a config or script. Whenever G-Force encounters a config or script name in a command line, then it will run it accordingly. A trailing '*' after a WaveShape, ColorMap, or DeltaField will make G-Force transition/morph from the present config to what you've specified (as opposed to instantly switching to what you've specified). A trailing '&' after a DeltaField makes G-Force begin precomputing that DeltaField (used to avoid a ugly pause caused when G-Force switches to a field it hasn't calculated yet). Understand that a trailing '&' after a DeltaField will not result in a DeltaField switch (only using the field name, with an optional trailing '*', will result in a DeltaField switch).
The following are the contents of some of the included scripts found in the "Scripts" folder. They're designed to give you a basic understanding how scripting works.
(The text file "1 Key": Pressing '1' switches to the given deltafield, colormap,
and waveshape. Since there's no '*' after TimeWarp, we expereince a pause while
GF calculates it on demand. 2 seconds later we cause the "Warp Me Away"
particle to start).
0:00 TimeWarp;Mystery Unveiled;Particle Pulse
0:02 Warp Me Away
(The text file "2 Key". Pressing '2' transitions/morphs to the given waveshape
to Rotating Arcs and a to randomly chosen colormap. Press 'H' to see why using
'E' will change colormaps.)
0:00 E;rotating arcs*
(The text file "3 Key". Pressing '3' turns off the text console, displays the
track text, transitions/morphs to a random colormap, and starts two new particles.)
0:00 \;E;Y;Y
(The text file "4 Key". Pressing '4' looks for the given items to run. In this
case, My Cool Particle is a particle config and Example Script is a script (because
a text file resides in the "Scripts" folder). If you open "Example
Script" and press 4, you'll be better able to follow what's happening. )
0:00 My Cool Particle;Example Script
(The text file "5 Key". Pressing '5' looks for a config, particle, or script
named "Comet Animation" to run. In this case, it's a sprite and happens to be
a movie file (vs. a text or image file). Since "Comet Animation.mpg" doesn't
have a particle config defined in the non-auto folder, it's already in the particle
slideshow. Because it doesn't have a particle config in the auto or non-auto
folder, it inherits the behavior of "Default Sprite".)
0:00 Comet Animation
(The text file "6 Key". Pressing '6' stops all slideshows, and switches to
a waveshape, and starts two particles. Right after, it starts computing the
given field so that when we call it 15 secs later, it's ready for use. We end
by turning all slideshows back on.)
0:00 F;Starburst;Parkening Power;DT - November Rain;Sparkling Table Water
0:01 Scattered Flow Out&
0:12 DT - November Rain;Sparkling Table Water
0:15 Scattered Flow Out*;Big & Banded
0:25 G
Sometimes, you'll want G-Force to automatically to start a script when a certain audio track starts. Whenever a new audio file is played in your audio player, G-Force will look for a script or config with a matching name to start. If the audio file is an mp3 file and internally defines the track name (ex, ID tag data), then G-Force will use that instead. For example, suppose you have a script that's made to go with a file named "Andy sings opera.wav", and it's written so that 0:00 corresponds to the start of the music file. Rename your script to "Andy sings opera" (remember: extensions are ignored in G-Force), restart G-Force, and play your audio file.