I found out the following is only with the BlockEditNew plugin (which is extremely useful)
When I block together several VA objects (wall and doors into an ‘apartment block’, to copy multiple times into a building) - it ‘breaks’ the va objects into rhinoblocks with a name like "*Wall{e198… etc.. If I explode the parent block (the apartment), all the VA objects are still ‘dumb’ rhino blocks..
Any clue whether this compatibility could be resolved? Thank you!
@florisd
If you put VisualARQ objects inside a block, you cannot create a unique copy of that block with Rhino commands. Because VisualARQ objects are in essence blocks, Rhino copies them “dumb” without the intelligence.
Workaround is to open a new Rhino instance, copy/paste the block there, change the name, and copy/paste it back.
@Sebastian_Wimmer We are still pending to help the BlockEdit developer to make it work properly with VisualARQ objects. There has been no progress so far in this interoperability.
@Sebastian_Wimmer I confirm we have been able to fix the compatibility issues between VisualARQ and the BlockEditNew plug-in and they will work fine in the upcoming VisualARQ 3.10 update. We will publish a Release Candidate version of it next Wednesday in the Forum.
thank you - until now, everything seemed to work, I once managed to crash it, and then some elements got converted to blocks - but was not able to reproduce that. I will update, if I encounter some issues again.