Problem when receiving MEP Fabrication Parts from Speckle Server using Speckle Revit Connector

[duzun]

Hello,

We have tested pushing MEP Fabrication Containment objects from Revit into Speckle Server using Speckle Revit Connector, and pulling them back with no modifications using the Speckle Revit Connector.

These parts are received correctly in Speckle Server, and examining them using the Speckle Viewer validated this - all properties are displaying correctly, and the parts are rendering correctly.

However, when receiving these parts back, Revit is unable to draw them, and hence the parts are not received into Revit.

Below is a screenshot of the error from the Speckle Revit Connector when trying to receive the parts:

We have then decided to try a modified version of the Dynamo script to pull the parts to Revit, which we have saw in the below post:

Meshes from Blender to Revit

I’ve been making some low poly rocks that I can kind of semi-randomly adjust the shape of so that they look more natural for a landscape client, but I am strugglign bringing these meshes into Revit with the connector. Most methods seem to fail, and I can never get to a point that I have anything I can do even simple operations on in Revit, such as adding a material.

Here is a screenshot of the script we have used that we have modified from the original post:

We used this script to change the category field of the fabrication part objects to any regular family object category (e.g. MEP Fabrication Containment changed to Cable Tray, etc). This allowed Revit to draw the meshes correctly and receive the objects. However, after doing this, the properties of these received objects were blank (even though they are displayed correctly on the Speckle Viewer).

We are using Revit 2023, and Speckle Revit Connector version 2.19.3.

Below is a link to a Speckle commit that contains a fabrication part we have created to share with you:
https://app.speckle.systems/projects/4c735dbc75/models/78bdeb2295@2a9767b60f

When we try to receive this part back into Revit, we are faced with the error message from Speckle Revit Connector that is indicated in the screenshot I’ve added earlier in this post.

Below are screenshots of the send and receive options of Speckle Revit Connector we have used to re-create this problem. We have also used all other combinations of options, but none of them have solved our problem.

Has anyone faced a similar issue like this before? If so, how did you solve it? Thanks in advance for your time and help!

[clrkng (Claire Kuang)]

Hi @duzun ,

This is because these MEP Fabrication parts are sent as our generic RevitElement object, which is kind of a fallback object type we use for all Revit elements that do not have their own corresponding Speckle object type and direct conversion between Revit and Speckle.

This means that RevitElements are received in Revit by their displayValue meshes, and our connector will convert these as Direct Shapes instead of their original MEP Fabrication part object.

We don’t plan on supporting more direct conversions of Revit objects without a strong reason to do so, could you describe in more detail your end to end workflow & why you’d like to receive these parts natively with Speckle?