When I send a Revit model / receive a Revit model, all the received objects become generic models? Is there a way to preserve that or am I missing something / doing something wrong?
Hey @katherine.c,
The Next-Gen Revit connector currently does not support receiving native objects — they are only received as generic models. If native object support is essential, you can still use the V2 connector.
Thanks Nikos.
Related to the above, and using V2 connectors, we are sending an ArchiCAD model to Speckle. Walls are correctly picked up in Speckle but when loading the model to Revit, they become Generic models. Is there a way of mapping these correctly, or any workaround…? Thanks!
Hey @Luis.Ese,
Can you please tell us the version of the connectors you are using? Is it 2.21.5? And what Revit, Archicad version are you sending from?
It will be good to share with me the Model url to have a look. You can send me a direct message if you want with the URL.
Archicad 27
Revit 2023
Speckle 2.21.5 in both computers
I have pm the url.
Any forecasts when we could expect mapping for the next-gen connectors? It was super cool feature and really useful.
1 Like
We’re not yet into planning/scoping this as our first objective is consistency, stability and performance across the range of the first suite of next-gen connectors.
The rewrite has allowed for rapid tackling of several legacy feature requests/bug fixes, so we believe that when we come to tackle it, it will be in a good place to get rapid feedback. Watch this space, but consider the first half of this year unlikely.
Ahh, understood.
The new connectors seems really cool, but we’ll miss the mapping features, I guess that will keep us on previous version in parallel.
This is precisely what we recommend for any existing workflow that is critical for you until or if parity is reached.
The only thing to watch out for is that mix&match behaviours sending/receiving from/to v2/v3 are undefined or known not to be possible - we are not testing for this to be guaranteed to work.