I'm running a test of an electrical underground model against underground structure (piles & caps), plumbing, and site utilities. It's finding some clashes, but not detecting others that I can obviously see in the model. Wehn I click an item that I can see the electrical clashing with and filter, it's returning no clashes.
Any ideas? I've already selected surfaces, lines, AND points on both Selection A and Selection B and it's still not catching the clash. Both models are NWC exports from Revit.
Thank you for your post. Could there be an integrity issue with the exported NWC’s? One quick test would be to create a new NWC from the Revit model to then test. The issue may then be resolved and pick up on the clash data you seek. I have also included a helpful guide below for reference.
Revit to Navisworks: http://bim.wikispaces.com/Revit+to+Navisworks+for+Clash+Detection
I have the same issue. I have already tried creating new nwc files, but it did not help.
These files (fire protection and plumbing) report clashes with other files, just not between each other.
I tried running a clash detection between the two entities that are in conflict, but nothing was reported.
Considering the primanry reason for upgradign to manage is clash detection, this is a problem.
Are both components in the same selection (left vs right) with self-intersect testing turned on?
No, one is on the left, the other on the right.
I tried the self intersecting thing, but no luck there.
I switched the test to "clearance" and it picked them up.
I have the same problem. It can detect clashes between dwg files which I exported from Revit. But if I export NWC, it won't detect a lot of obvious clashes.
Happend the same to me, just realized the rule "items in same layer" was on and that was causing problem... i guess is just some software bug; try unchecking this rule and hope you get the solution.
Cheers
CoordinadorBimAlegra
This worked and you fixed a long time issue that I've had and not been able to fix.
Thanks!
Perk
--------------
>Happened the same to me, just realized the rule "items in same layer" was on and that was causing problem... i guess is just some software bug; try unchecking this rule and hope you get the solution.
Hi Perk.
i am glad my comment could help you fix the problem. will be very pleased to help you anytime.
Cheers.