Can I still create Revit/ArchiCAD objects with Python in v3?

General discussion Speckle Jobs
, , ,
1

I am interested to understand if the workflow at the beginning of this thread is still achievable in the nextgen v3 version of connectors.

I have been resurrecting a previous project to pass basic measured survey objects (levels, walls) thorough Speckle and out to a varienty of platforms.

Before I re-engage with trying what I was doing before I thought I would ask what the best way to do things is:

a) push objects to speckle as native revit, archicad objects and then pull to revit/archicad with the connector

b) push more raw data to speckle and then pull to revit/archicad with dynamo or a plug-in which I will author

Any steer on which approach I should use would be appreciated.

2

I’m not sure I understand the question fully, but the connector workflow for sending data to and from different software via speckle is still the same.

Send something from revit ->push it to speckle->Receive it in archicad.

3

Apologies I wasn’t clear. I am not using this for interop between the two. I am creating native walls for Revit or ArchiCAD from digitised data using SpecklePy and then pulling the models into the native platform.

This worked with the v2 connectors, as documented in the linked discussion thread, but I am not clear if it is no longer possible in the v3 connectors.

4

Shortest answer: Presently V3 Connectors for Revit no longer generate native Revit objects on receive.

What can be done in current interop lite behaviour is that any object you create can be allocated a category

5

Thank you. So that sounds like generating speckle objects for Revit with python like the beams and walls in the thread I linked to is still possible, but as before the Revit file that the objects are pulled to, needs to have appropriate families.