Exporting/Importing Clash Tests

[pauljordan]

Has anyone had any luck exporting and importing clash tests in 2011. I have one I'm trying to use and so far I've gone through the process of saving it to my custom_clash_tests folder as indicated in the NW manual and that way doesn't even allow NW Manage to open up.

I can export it fine but, when I go to import it, I get to fill out a lovely crash report that never gets answered by Autodesk.

The size of the .xml file is 523k and I'm beginning to wonder if it's a size issue..

Is anyone else able to do this and if so, what kind of file size is your clash test?

If anyone would like to share one that works, I'd love to give it a shot, that way I can narrow things down a bit more.

[greenwaldc]

Can you post a screenshot of your clash detective selection tab?

I've found that I need to create search sets first, then create a clash test which clashes one search set vs. another search set. By doing this, I have been able to export an .xml file, and import it to a new file. The import will copy over the search sets as well as the clash tests.

One of my .XML files is about 200kb, and contains 3 dozen clash tests.
FWIW, I was also able to use the .xml file created in NWM 2011 when I upgraded to 2012.

[pauljordan]

Can you post a screenshot of your clash detective selection tab?

I've found that I need to create search sets first, then create a clash test which clashes one search set vs. another search set. By doing this, I have been able to export an .xml file, and import it to a new file. The import will copy over the search sets as well as the clash tests.

One of my .XML files is about 200kb, and contains 3 dozen clash tests.
FWIW, I was also able to use the .xml file created in NWM 2011 when I upgraded to 2012.

I've got both selection sets as well as disciplines (i.e. Architectural, Electrical, etc.) in my select tab.

Currently I have 61 batch tests and 80 various rules I apply to each batch.

[greenwaldc]

How are you using the rules? I've used them in a very limited capacity, as I've found that search sets are more reliable. Then again, that is based on my initial testing from quite some time back.

Back to search sets, most of mine are nested. As an example:

Arch search set looks at all files, and finds the string _ARCH_
Arch windows search set looks only at the Arch search set, and finds all layers which contain _GLAZ_
Arch floors search set looks only at the Arch search set, and finds all layers which contain _FLOOR_

[pauljordan]

We have all of our systems broken down into thier own drawings. Any kind of process piping for example will be it's own drawing. We set our search sets by discipline and they look at the file names (Usually an A in the name or a PL in the name would indicate Arch or Plumb).

Then we've created sets for quite a few things as you can see by my previous post so that we can have rules to ignore those items when they clash with other items.

I know we've spent quite a good bit of time setting up these rules and I've told my users to be on the lookout for reoccuring rules they think might need to be done away with so we can make even more rules to eliminate them from our results.