2009

3. Click the Tasks tab, and check the static package tasks are displayed, and at least one animation
scene has been linked to one of the TimeLiner tasks.
4. Click the Configure tab, and check the task types have been added to match the static packages.
5. Click the Simulation tab, and play the simulation. Check that the static and dynamic packages are
shown in the correct location and over the correct periods of time.
6. If the Clash Detective window is not already open, select Tools > Clash Detective from the menu
bar.
7. Click the Select tab.
8. In the Left and Right panes, select the objects you want to test.
9. In the Link drop-down box, select TimeLiner.
10. In the Step field, enter the Interval Size to use when looking for clashes in animation scenes.
11. Click the Start button. Clash Detective will check at each interval in the project to see if there are
any clashes present. The number of found clashes is displayed in the Found field.
Note:
If the TimeLiner project is large in size, running this type of clash test will invariably take more
time to complete than a normal clash run.
You can now review the found clashes.
Running a Clash Test
To run an individual clash test:
1. If the Clash Detective window is not already open, select Tools > Clash Detective from the menu
bar.
2. Click the Batch tab, and select the test you want to run.
3. Click the Select tab, and select the required test options.
4. Once the left and right sets are selected and the clash type and tolerance defined, click the Start
button to start the test running.
The Found box shows how many clashes have been found so far during this test.
Note:
The progress bar shows how far through the test Clash Detective has got. If you wish to stop the
test at any time, press the Cancel button and all clashes found up until the interrupt will be
reported and the test will be saved with a Partial status.
Selecting Items for Testing
518