Tried with restarting blender as well as doing a system restart between.
Double checked and after uninstalling 2.17 and 2.18 there were not leftover files I could find for speckle or connector labels of any kind in the addons. 2.15 still showing the bpy_speckle issue.
I think I have to wait like others for hopefully 2.19 to fix the issue. Learning blender and speckle has been put on hold for me.
Just posting an update. Updated to Blender 2.20.3 and Revit 2.20.6. Running on Revit 2024.
Still does not work in replacing the items and makes new ones (doesnāt remove old ones). Also tested out this time by sending via āeverythingā as well as a āviewā and both arenāt working. Still hoping this gets resolved so I can ditch Vray
Any news on the update functionality? This feature is super important in archviz workflow! Are you even working on it?
After a couple years of tracking this post, Iām also eager to hear if thereās a planned release date for the new Blender connector. I know it has been deemed a lower priority since one of the Speckle developers mentioned Revit-to-Blender as a less common workflow, but in my experience, itās because of this exact issue. Blender is often overlooked by large architecture firms because Revit data is updated frequently and thereās currently no reliable method for reimporting Revit content within Blender.
For those of us in the arch viz industry, thereās huge upside to abandoning the Revit-to-Max pipeline ā geometry nodes, real-time viewport rendering, compositing, better procedural shading tools, the Flamenco plugin for a local render farm, the built-in asset browser, a modern/responsive UI, + open source, etc.
I appreciate the mission of the Speckle team and the apps/next-gen connectors youāve created thus far. Itās an amazing product and Iām looking forward to using it again when this new pipeline is established.
@mseawell Itās coming- very soon. Weāre prioritizing receiving in Blender first, to support archviz workflows. It is actually one of the most popular connectors, and we historically, regrettably, have not been able to dedicate much attention to it despite this fact.
@dogukan can tell you more re: concrete timelines!
Because next gen Revit isnāt currently supporting sending objects as instances, weāre aware this will probably strongly impact the workflow in Blender. If youāre open to it, weād love to get some feedback from you once Blender is in a good shape
@clrkng - thank you for providing more information and timing for the Blender connector! And yes, support of instances coming from Revit would be critical, especially when receiving large data sets with many identical objects, e.g. mullions, curtain panels/glass, doors, etc.
I would be happy to connect and provide feedback when itās ready to test!
Hi @mseawell,
Weāll release the alpha version of Next-Gen Blender Connector within next week. Iāll ping this channel once itās published
Itāll be a load only connector for now, the send functionality is in progress. Weād love to hear your feedback on that!