Issue with Sending Adaptive Generic Families from a revit file to another revit file using speckle

Help
1

Hi Speckle Community,

I’m encountering an issue when trying to send adaptive generic families from one Revit file to another using Speckle. Here’s the problem:

When sending adaptive generic families, they are not being transferred correctly.

The elements are received as generic models, losing their adaptive properties, type, and parameters.

What I’ve Tried:

Sending the families via Speckle – didn’t work. they are receved as generic models

Manually loading the families into the destination file – still didn’t resolve the issue.

Expected Behavior:

Adaptive generic families should retain their adaptive properties, type, and parameters when sent via Speckle.

inside speckle everything seems great

image
image1825×1009 153 KB

but when receving again inside revit i receive a generic model, and sometimes i was receving all the elements placed at the same coordinate

Questions:

Is this a known limitation of the Speckle-Revit connector?

Are there specific settings or workflows to ensure adaptive families are sent correctly?

Are there any workarounds or plans to address this?

Any guidance would be greatly appreciated!

Thanks,

2

Hey @rebalj ,

It seems that you’re using our Next Gen Revit Connector - in this version of the Connector all the geometry is received as a Direct Shape.

You can use our previous connectors (v2) if you want to generate native Revit elements, please note that the family needs to be loaded in the Revit document for this to work.

image
image1526×1124 61.6 KB

1 Like
3

Hi Matteo,

Thank you for your response. I was eager to try the Beta version and proceeded to test Version 2. However, while attempting to transfer data between Revit files, I encountered the following error:

image
image387×655 20.9 KB

• a Error!
stem.AccessViolationException - Attempted to
read or write protected memory. This is often an
indication that other memory is corrupt.

Could you please advise on how to resolve this issue? i saw in another post that it might be a bug

Best regards
Rebal

4

Hey Rebal, sorry about this!

Could you share with us a minimal reproducible Revit file so we can investigate further? Google Drive / Dropbox etc

6

hey Matteo,

I shared with you the files
many thanks

Rebal

1 Like
7

Yes we got them, our team is looking into it!

1 Like