OSArch Community

IfcElementAssembly in the BlenderBIM add-on

  1. C

    Related to this comment by @bruno_perdigao.

    I am using the latest development release of the BlenderBIM add-on.

    How do I recreate what you are doing in your .gif from your post?

    This is my attempt, I just have one IfcElementAssembly with two beams, but copy pasting the IfcElementAssembly didn't copy all the related items in the IfcElementAssembly

    It seems to be merged as I read here:

    https://github.com/IfcOpenShell/IfcOpenShell/pull/3328

  2. T

    did you select the aggregate's empty, and crtl + shift + d?

  3. C

    @theoryshaw

    I tried several buttons, but nothing seems to happen.

  4. T

    hmm.. not sure.

  5. T

    could it be this?...

  6. C

    @theoryshaw

    I indeed didn't check that, but now it "copies" only the empty.

    But for you it works as intended?

  7. T

    yes.

    Did you make sure to use crtl + shift + d?

  8. C

    @theoryshaw said:

    yes.

    Did you make sure to use crtl + shift + d?

    Yes, I did. :(. I am doing something wrong...

    Are you on the latest stable release?

  9. T

    Are you on the latest stable release?

    yes.

    Are you holding ctrl and shift down at the same time, and then hitting d :)

  10. T

    are you on windows/mac/linux?

  11. C

    @theoryshaw

    I'm on Windows 11 with Blender 3.5 and BlenderBIM latest stable release installed:

    I created three IfcBeams from the IFC4 Demo library and made them into an IfcElementAssembly using the IFC aggregates tab

    I selected the Selectable/Selectable, no ide what this does.

    I made the BIM tool active and now select the IfcElementAssembly/Assembly empty, then I press ctrl shift D, only the empty appears, same when having the Select Box active.

  12. C

    Just to be sure, I expected when duplicating the empty of the IfcElementAssembly the entire related IFC elements would be copied with it. or is that not intended behaviour? I can make this work but then i just dumb copying the IfcElementAssemblies.

  13. T

    PR was pulled only 4 days ago. Sorry, when you said stable release, i thought you meant the latest release.

  14. T
  15. B

    Yes, it was recently merged. I hope it works now

  16. B

    For anyone willing to try this feature, a few warnings about it:

    • It's still experimental and may change in the future.

    • The refresh operator deletes and recreates all duplicates. So it can become very slow if you have a lot of objects.

    • If there is any issue that you think it's related to this, please tag me here or in an issue on BlenderBIM's GitHub repo.

  17. C

    @bruno_perdigao

    Nice feature!

    Is it possible to update/replace/modify one IFC element in each of the assemblies?

  18. B

    Can one of the IFCElementAssemblys also be rotated relative to the ground plane? ( I struggle in Revit which won't allow this transform).

  19. C

    @Bedson

    Can one of the IFCElementAssemblys also be rotated relative to the ground plane? ( I struggle in Revit which won't allow this transform).

    Don't really understand your question, you want to rotate an assembly? If so, is the Select Parts an option?

  20. B

    Is it possible to update/replace/modify one IFC element in each of the assemblies?

    I don't know if I fully understand, but for now, any changes you want to make have to be done in the parent IfcElementAssembly. Then, if you use the refresh operator, the changes will reflect on the duplicate.

    There are a few things that I want to implement to make things easier: a button to select the parent (right now you have to know where it is) and a button to unlink the duplicate if you want to make it independent.

    Can one of the IFCElementAssemblys also be rotated relative to the ground plane? ( I struggle in Revit which won't allow this transform).

    Yes. Not the best demo, but the GIF in this comment shows a little bit of how it works

  21. C

    @bruno_perdigao

    Then, if you use the refresh operator

    Where is this refresh operator button hidden? ?

  22. T

    For a future roadmap, i do like the idea of being to edit any of the assemblies instances throughout the project, and then they all update.

  23. C

    @theoryshaw said:

    For a future roadmap, i do like the idea of being to edit any of the assemblies instances throughout the project, and then they all update.

    And I would like to add the possibility to array assemblies.

  24. T

    Dumb question, why not use Blender's collection instances for these typed assemblies? There might be some performance advantages.

  25. C

    @theoryshaw said:

    Dumb question, why not use Blender's collection instances for these typed assemblies? There might be some performance advantages.

    A blender collection won't survive an IFC roundtrip?

  1. Page 1
  2. 2

Login or Register to reply.