Revit to Blender - Creates Duplicates in Blender

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.

2 Likes

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 :crossed_fingers:

4 Likes

Any news on the update functionality? This feature is super important in archviz workflow! Are you even working on it?

1 Like

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.

3 Likes

@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

3 Likes

@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 :slight_smile:

It’ll be a load only connector for now, the send functionality is in progress. We’d love to hear your feedback on that!

4 Likes

Hi, still no update on this issue ?

The Next Gen connector for Blender is now the default. There will be no further development of the v2.2x connector.

It is our understanding that the issue has been resolved.

1 Like

I don’t understand, the current connector still gives me duplicates, no material preservation, and objects come duplicated and not instanced, is this normal ? sounds like a huge regression in the workflow

there’s no send function anymore… why no further development ?

Could you confirm which version of the Blender connector you are using? We are in transition from v2 to v3, so you could have the ā€œlatestā€ of either.

In v3 terms, publishing is on the roadmap but not yet fully implemented. So, for the time being, it is an endpoint for your workflow.

Only the v2 life of the Blender connector is halted. v3 continues at pace.

I’m using 3.1.0. I hope the features in the tutorial will be recovered soon : preservation and instancing they are amazing and definitely a game changer for using blender in an production workflow with other team members

Great. I recommend raising a separate topic if you have features and fixes in mind for the v3 connector, as this original message was related to an issue with the legacy v2 connector.

Welcome to Speckle community :partying_spockle:

1 Like

Done here : Blender connector 3.1.0 - Regressions

Is there maybe a Speckle shared demo workspace that contains a model with all V3 bells and whistles, so that I could see what comes in into Blender ?

Nothing that isn’t already public - we are pushing out as frequently as new functionality exists.

Thanks, do you have any links ?