Hello,
As already reported for the v2 in this topic : Revit to Blender - Creates Duplicates in Blender
In blender we can’t send the model anymore to Speckle, and imported geometry gets duplicated and materials aren’t preserved. Also the instancing doesn’t work, objects are duplicated instead.
Please make the connector work as it was in the tutorial video
Hey @archimage ,
Can you give more details on the issue? Speckle model urls, screenshots and files for context helps us help you.
3.2 has been released today but no luck it throws this error when trying to enable it : attempted relative import beyond top-level package
Hey @archimage,
A new beta version has been released to fix this - 3.2.0-beta3. Please give it a try and let us know!
Hello yes I can load the plugin now, publish button is present, it loads a new version of the same model.
Is it possible create a model and not only to select one on the same projet ? or to have more options how to separate things in order to import only new things in Revit ?
Currently publishing creates a new version of the same model which is not very handy when importing in Revit.
Thanks for the progress
Hello, I have found that I can upstream a specific set of objects, but model creation has to be done in the web ui, is it possible to add the button to create a model from blender ?
Also I have found that copy/paste from a blender shader node group to revit material shader node works as a replacement, an stays preserved on each update, however i’m losing the UV unwrap work. Is there any work around to this ?
Thanks
Hey,
Yes, creating projects and model inside our Blender UI is on our roadmap, will be available soon. I’d like to hear more about your Revit to Blender workflow so we can make necessary changes. Maybe adding this as a setting could be a solution.
workflow is pretty straightforward, modeling team work on revit until the end of the competition while rendering team is working on blender for archviz, updating the model without breaking the archviz job is crucial
Is there a way to update only a portion of the projet and not the entire project ?
Let’s say some exterior stuff on the project has been added, without any modification on the rest, and we want to preserve the uv mapping stuff and overrides dones , we want to select it on a specific view in revit, and import only things that change only without updating the entire main model ?
Is that possible ?
And is it possible to have a log of what elements have been updated ? Even better, pick what we want to to update or not in a list before applying the load ?
The latter parts of your question and regardless of individual connector functionality is part of the secret source of speckle.
i.e You don’t need to have a one-to-one between a speckle model and the source models at kall you can completely atomise your source model so that you can have: your exterior, your interiors, your structure , facade all as separate speckle models from a single file then on receive you receive what you want.
Then as to seeing what has changed between versions, yes we have you covered Compare Versions - Speckle Docs
I was aware the I could make different models, I’m still on the free plan to test the workflow, so I couldn’t load more than 1 model, maybe that’s why I was struggling to find another way. I didn’t know about this compare versions feature, pretty awesome thanks
EDIT : Question, is it possible to uploard from Blender based on selection options ? Selected, Viewlayers, Scene, Visible/renderable objets or collections, Camera ? Just want to avoid to publish everything back to speckle
I am also on free plan.
You have one project only but you can upload 5 Models.
For now publishing from Blender is selection based only
That is indeed a bit tedious (and error prone for me).
Which has also a bit to do with Blender’s Collections and Selections (I will never get that 1 Active + a bunch of Selected approach)
I always thought that’s the way V3 works in general.
I am not really sure if a “export visible only” would help (?) to allow for partial upload or if would need something like a “Speckle activated” for Collections or even selective (groups of) Collection(s).
There’s an idea, with renderset addon you can create contexts for rendering, each context can have custom visibility per object or per collection, which can ease presets for selection before exporting, maybe in the future this feature can be implemented with speckle, creating selection groups or contexts