The Intersect command is available regardless of selection. However, any database entities selected when the command is entered will automatically be placed in the Group A intersection group and Group B selection will be active. Otherwise, if no database entities are selected, both intersection groups must be defined and Group A selection will be active. At the top of the Intersect panel is a table listing the number of Entities in each Group. Also listed is the number of pending Intersections entities, or Not Run is displayed when intersections have not yet been calculated.
Tip: For best intersecting result, make sure the Model Size tolerance is on the same order of the Grid/DB Length reported in the File, Properties panel.
Select Create, Intersect. Select entities for Group A in the Display window or using the List panel. Change to Group B in the Entity Selection frame, and select the entities for Group B. This command automatically overrides the Mask so that only database curve, plane, and surface entities can be picked. Use the Intersect command to calculate all possible intersections between the two groups’ entities. Click on OK to save all intersections as new database entities.
There are a number of commands available on the Intersect panel which are described here in detail. The Intersect command is the action command for this panel. It is not available until database entities have been assigned to both Group A and Group B intersection groups. Click on Intersect to have the intersections between the two groups calculated.
The Entity Selection frame allows you to choose which group’s entities, Group A or Group B, is currently being selected. Note that this command automatically overrides the Mask so that only database curve, plane, and surface entities can be picked. You can pick entities either graphically in the Display window or using the List panel. An entity cannot be assigned to both groups.
Use the Tolerance frame to adjust the Fit Tolerance used by the Intersect command for those cases where the default tolerance does not produce the expected database intersection. In order to adjust the Fit Tolerance to a custom value, you must first uncheck the Use Default checkbox. Then simply type a new tolerance value into the Fit Tolerance text field. When adjusting the Fit Tolerance fails to produce the desired intersection, examine the model more closely to ensure the two groups indeed physically cross. You may also consider adjusting the Model Size tolerance (refer to the File, Properties section for further information).
Two alternative intersection types are available in the Advanced frame which is closed by default. Click the checkbox adjacent to the label to open this frame. The Actual intersection type is the default and attempts to calculate true physical intersections between the two groups’ entities. The Closest Approach intersection type looks for the closest common points between the two groups’ entities and will create a set of intersections for both groups. The associated Max. Distance text field allows you to limit the distance, between the two groups’ entities, to which this method will search. The Apparent intersection type employs a ray cast approach where your view direction or the screen coordinates Z-axis is the vector along which the rays are cast. Wherever the two groups’ entities appear to intersect along this view direction new intersections will be created for both groups.