Model Editor - Validation Error

Revit Plugin
1

Hi,

I completed a model using the editor, it validated inside the editor, but when I brought it into to Rhino the model had errors. Also, the solve adjacencies did not properly solve inside the model editor.

Here is the hbjson for reference:

hbjson.zip (37.2 KB)

Is it possible to view the boundary conditions of the walls inside the model editor?

2

Thank you for sharing the output HBJSON file. Can you also share the input DFJSON file so we can try to recreate the issue on our end. You can export the model as a DFJSON using the right bottom menu. Click on the Pollination logo and then go to File > Save as....

image

You can use the 3D Preview to check the interior walls after removing walls and other layers from the preview.

image
image1261Ă—760 60.9 KB

3

@smarentette, I had a quick look and I wonder if you had intersect set to true?

image

The errors that I can see are the result of not intersecting the faces.

@chriswmackey, should these cases raise validation error in Model Editor too? Or is it something that we can only catch in the HBJSON model?

5

Here is the dfjson:

dfjson.zip (14.8 KB)

I think I did have that setting on. What is the purpose of it?

6

Thank you for uploading the DFJSON model. After solving the adjacencies with the intersect option the result is a valid model.

image
image1914Ă—622 152 KB

There are few tolerance issues in shade faces but they get fixed automatically during the import to Rhino. Here is the HBJSON file that is exported from the model editor after selecting all the rooms and running these commands:

  1. Join co-planar faces
  2. Reset adjacencies
  3. Solve adjacencies

Model 1.hbjson (726.7 KB)

8

Yea, we can add an extra check for this. Right now, we only check for cases of Missing Adjacencies in Dragonfly and not whether those Adjacencies have matching areas. But the areas are important too.

I’ll put it on my agenda and get to it eventually.

1 Like
9

I’m just making a note here for @smarentette that we decided to take out the “intersect” option from the “Solve Adjacency” command because there really isn’t a case where you want to forgo intersection as part of adjacency solving. The only argument we had for keeping this option is that maybe you might not want to run the intersection to save time on a large model if you had already run intersection previously. But the intersection calculation is so fast in dragonfly’s 2D world that you can’t even tell whether the intersection process is run or not on a large model.

Long story short, now that we removed this option and we always run the intersection, it should not be possible to get this type of validation error in the future using the model editor. So I’m going to hold off on adding any extra validation check for it at this time.

1 Like