![]() I’d suggest simplifying your process so you are testing with a single clash- it is much easier to see what is going on and you should be able to identify the issue. I’m not sure how this works in imperial units. ![]() ![]() In the below examples- I have exported the same model with a single clash using internal vs shared coordinates, run the clash detective, exported the clash report to XML, then brought the points back into Revit using Dynamo.įrom the second screenshot- you can see that in this example, using shared coordinates round trips to the correct position.Īlso note that there may be an issue of units- in the metric world, Navisworks reports in metres, whereas Revit is in mm. Without running through your model and method in detail, it isn’t possible to give a definitive answer- but I can give you a few clues. For example, an image of a bunch of small balloons will work better than one big balloon.As Mostafa
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |