Subtle bump in case anybody may have a possible solution. Again, thanks in advance.

-TZ

What version(s) are you working with?

That would be Navisworks Manage 2017 good sir.

-TZ

Ah ok, never had this with '16, does it happen with evey file or just with this one in partcular?

I had a clash detective problem with one particular file, It crashes on clash reports in Windows 8 for some particular files. ADESK know about it issue in windows 10 & 7 and they knew which services packs would roll back and solve the issue - but not for Windows 8.

As an outside shot, try open your file on a old laptop or PC with different SP's and see if it makes a difference?

So several of the User Defined Clash Test Rules are Set based ("Same Selection Set" and "Specified Selection Sets") so for the Rules to work properly you need the associated Sets.

I run A LOT of Selection Set (technically Search Set) Rules in my Clash Tests to allow me to un-check the "Items in same layer" and "Items in same file" rules. It's really the only way to see if a system is clashing with itself.

Your Clash Test should carry over from week to week - so I'm not sure whats going on there.

You can so a Save-As of your NWF (name it something different than your master file) > Delete your Sets > then Export Clash Tests as a work around.

Hey Mason, thanks for commenting. Let me be a bit more clear with additional details...

First off, I too use Search Sets a lot for clashing. As for my week to week, yes, that doesn't change. The actual Clash Tests themselves, once I've created them in the Clash Detective area, stick with the NWF as I update.

The GC has requested (aka "required") that I break out each NWF file by floor and by tower. So for instance, I have an individual NWF file for Level 9 West Tower, Level 9 South Tower, Level 10 West Tower, Level 10 South Tower, and so on up to Floor 19. This means I do not have a single NWF file for all towers, all floors. What I'm trying to do is export the actual Clash Tests themselves, not the Search Sets, so I can import into each new NWF I'm creating. I just don't want to type "EXIST - HVAC vs PLMB TI" 22 times (11 floors x 2 towers). If I could get the list of the Clashes themselves in each NWF file, it saves me lots of steps.

Hopefully that is more clear. Thanks again for commenting, I feel like you're very skilled at Navisworks and I appreciate you helping me, always.

-TZ

PS: I guess I could have a "template file" in which I get everything loaded for one floor/tower, then add all my clashes, and Copy/Paste the file itself and simply delete the NWC's and re-append the levels/towers I want. I just feel like "Export Clash Test" should do just that.

Gotcha - so you can do the Save-As route I suggested at the end of my post and it should work.

Do a Save-As of your NWF (name it something different than your master file) > Delete your Sets > then Export Clash Tests.

The Clash Tests should then Import without the Sets - I have a Clash Test Import file set-up this way that I use to start new NWFs when a project starts up.

I personally only run three Clash Tests on every project - MEP v MEP, MEP v Structure, and MEP v Ceilings and group by Level. It's a lot of clashes to take in, but it eliminates touching the same clash multiple times.

Take a scenario where a Fire Protection Branch is clashing with a Duct, Conduit, Sanitary line, and Chilled Water line (assuming each of those trades are in separate models) - in the traditional Clash Test method of Trade v Trade you would see that Fire Protection branch in each of the Trade vs Trade Clash Tests - where in the all MEP v MEP Clash test you would see everything that Fire Protection branch is clashing with. Seeing the Fire Protection branch in the context of all of the other trades allows you to make a better decision as to how to solve the clash.

That's just how I do it anyway - saves a lot of time.

Thanks Mason, I will go with the Save-As approach.

I do it this way too and I love it. I did it originally on this job, but... again... the GC and two other trades were a bit overwhelmed... so I broke it back out trade by trade for them. They also wanted to separate the existing core and shell items with the new, so I'm stuck with old-schooling it for now.