Model Group - Recalculation and Deleted Geometry

Hi,

After using the Create Group Type component, I proceed to place model groups using the Add Model Group component.

If I recalculate and/or disable the component, the model group does not disappear and is unpinned. If I delete the model groups and rerun the component, it now creates a “deleted revit group”.

I cannot further manipulate this group, but it exists in the Revit model.

Does anyone know what I am doing wrong?

Also, placing these groups is incredibly slow, yet faster to interact than Revit Links.

Thank you

I’m not seeing these behaviors in the way you described the workflow.

It sounds like you may need to reset the element tracking.

https://www.rhino3d.com/inside/revit/1.0/guides/rir-grasshopper#element-tracking

Hi Japhy,

If you link up an set element parameter to the model group, (in my case it was to set an offset from level) then you will see the behaviour.

Setting Element tracking to replace solved this issue but I’m wondering if it has a performance cost compared to update.

Also, recalculating with update creates a duplicate model group.

I’m seeing the issue once a the parameter is set on the instances. Thanks for reporting.

No problem Japhy.

Could you please explain the behaviour of the element parameter node?

It seems once I set it, Revit remembers the value even if I delete/update the Model Group.

Furthermore, when I create walls using a curve, it comes in at a seemingly arbitary offset from the specified level. I have to manually create element parameters for all walls created this way just to place it on the level.

Thank you!

Where are the Curves in Rhino in relation your expected location in Revit? A small example might be needed.

When you create a group in Revit and set an instance parameter, say Comments. Then place a new instance of that group the comment will be already set. You can then change the instance parameter on the newly placed group, but placing an original one sticks with the original.

This is different than placing a Family Component Instance.

Make sure your custom parameters are set to your workflow expectations.

Thanks for the tip!