If you have just created a 3D object but can't see it on your scene:
The algorithms used to detect surfaces and 3D schools will produce poor results if a variable to which they are applied is linked to an erratic cruise track. If a visual inspection reveals that the cruise track contains jumps, loops or other problems you should apply different processing and smoothing until it more accurately represents the path of the logging vessel. When you have smoothed the cruise track you should detect the schools and/or surfaces again and compare the results.
Note: A cruise track that appears smooth at large scales may contain loops and jumps when viewed at smaller scales.
3D school detection can be very slow (taking hours on even a fast machine) and require large amounts of RAM. This is particularly the case if the minimum 3D size limits are smaller than or near to the size of individual data samples, which means that schools containing a very small number of samples will be considered during the processing. If you find that detection is slow, does not complete in a reasonable amount of time, or reports running out of memory, then consider one or more of the following:
increasing the minimum school dimensions on the Size Criteria page of the Detect 3D schools dialog box
segment the EV file into smaller ping ranges (say 250 pings in each range) and doing separate detections for each range
increasing the physical RAM in your computer to 1Gb or more.
3D display problems
Detect Bottom Surface dialog box
Create 3D Surface From Line dialog box
Detect 3D Schools dialog box