somewhat new to Speckle but working towards creating some workflows for our users to start taking advantage of the data transfers.
I’m trying to work with Grids in both Etabs and Revit - I’m noticing that
When I moved grids in etabs sent to speckle and received in Revit (update) - the grid shifts did not translate to Revit
Then when I moved grids in Revit sent to speckle and received in Etabs (update) it created new grids in Etabs with the same name (at the right place) but now there are two grids with the same name.
I have the logs but as a new user, it didn’t want to let me attach files.
this was a basic group of orthogonal grids in revit 24 - and Etabs 21.1
Thanks in advance
Example: Help us reproduce the issue by attaching sample files, giving a step-by-step reproduction guide and screenshots/videos if available
Logs: If the issue regards our desktop connectors, please share the relevant logs you find under: %appdata%/Speckle/Logs
Hi @mdsweeney, welcome to Speckle, and thank you for the report.
Sorry, it’s a little slow around here; we’ve all left it a little late to take a break from the coalface simultaneously, having had such a busy year.
My colleague @bjorn squeezed in some of the last v2 connector updates that specifically handled grids with Revity and ETABS that should have made it into the latest version of the connectors. If you already use these, I will have to defer to him if this is a supported workflow or a deficiency.
That said, if it isn’t currently supported, all our engineering efforts are now with the Next Gen v3 connectors, for which ETABS and Revit are both candidates already started. With that comes a rough timeline for when or if roundtrip workflows between the two applications will be supported. We know from v2 that Grid exchange is one of the key interop workflows, but I will have to defer to colleagues on the roadmap.
Thank @jonathon , I’m using the most recent Etabs connector. I did not use the beta of the V3 Revit connector though. I used the latest of the V2 Revit connectors. The issue seems to be with the etabs side, I think?
It is sort of a critical workflow. I’m curious if others have seen this? or if I’m missing something, or maybe just not supported yet. Anyhow, getting back into the swing of things from the holidays now. So hopefully we can figure it out.
Thanks for your patience on this. As @jonathon mentioned, we had made some enhancements to the v2 Connector to enable more advanced grid exchanges (including angled grid support). This means you can now send your Revit grid system to Etabs or vice versa (as you’ve already seen).
The version of the v2 connector, however, focuses on initial grid exchange between platforms only, as this aligns with typical project workflows where grid systems are established early in the design phase (with minimal ensuing updates). While we’re working within certain technical constraints of the Etabs API, we can keep this in mind for future releases, particularly as part of our Next-Gen development.
thanks, that’s really helpful to know that it is working as designed and I’m not missing something.
For us, and I would think a lot of teams. Grid adjustments along the way are pretty common. Early on we’re close, but then things get refined, design assumptions get clarified, and we have to adjust. So it’s a very common workflow to start, get some basic design set up and done, then have to make some adjustments.
Knowing that we need to make sure and manage these adjustments certainly clears up confusion.
We’re excited to keep pushing on this, Thanks for the feedback.
We’re excited that you’re excited to keep pushing . Let us know if anything else comes up. @dogukan and I are also always here to chat about structural engineering workflows
. Let us know if anything else comes up. 