Hello, i am trying to put Visualarq object inside a blocks, but it disappeared after I edited something.
Hi @SAMS that’s a bug we are waiting to fix. I’ll let you know when we do it.
Hi @SAMS I’m glad to inform you this error has been fixed in VisualARQ 3.1, which is already available to download: Update - VisualARQ
Adding Elements to Blocks gives unexpected results - looks like Elements are converted to Block Instances.
Creating Blocks by selecting Elements is shown at the start of the video and works as expected.
There is more.
Entering the Block geometry “dumbs-down” the Element to the Block Instance.
Hi @Czaja,
You’re absolutely right.
Unfortunately, this problem cannot be resolved on our side and requires McNeel to address it in Rhino’s code. I’ll report the issue to ensure it gets fixed in Rhino 8 SR15.
Thanks,
Enric
1 Like
Hi @Czaja,
I have good news! I decided to check if this issue was also present in Rhino 7, and to my surprise, adding VisualARQ objects in “Block Edit” worked fine in Rhino 7. So, I investigated what had changed in Rhino 8, and I finally identified the problem.
The issue was related to the same bug that causes VisualARQ objects to disappear when using BlockEdit. I’ve managed to fix it, and the solution will be included in VisualARQ 3.2 RC2, which is scheduled for release on Wednesday, December 18th, 2024.
Thanks again,
Enric
3 Likes
Great!
By the way, do you think it would be possible to change the values ​​of Element parameters while being outside the Block? By example by using Grasshopper. This way we could have an assembly of multiple VA Elements. Groups are not as robust as Blocks.
Hi @Czaja I’m not sure to understand your last request.
Yes, of course! from the properties panel you can change the values of an Element, isn’t it?
I think what Jakub means is: changing the parameters of a VA object that is INSIDE of a block (block in a block). Right?
1 Like
Hi, this is just to confirm the issue of VisualARQ objects missing when editing blocks has been fixed in VisualARQ 3.2 RC2 version. There is actually a newer update available: VisualARQ 3 - Version 3.2 RC3 released
I’m not sure, @Czaja ?. In any case, the parameters assigned to a block inside a block can be edited as well.
Hi Francesc, its been a while and I have just re-entered the Visualarq workflow. I find my VA objects created inside a block disappearing when I save the blockeditor. Im in Rhino7.
Hi @aditya.d.bhatt which VisualARQ version are you using?
Thanks @aditya.d.bhatt can you share a file to test this with? In my tests, the BlockEdit works fine with VisualARQ objects involved.
I thought it’s already resolved but I noticed this bug still persists in the VisualARQ 3.3.0.19535
Clicking on the Element in the Block Edit window just once permanently “dumbs-down” the Element to the regular Rhino Block Instance.
@Czaja VisualARQ objects are blocks. When you run the BlockEdit command on an object, it lets you modify the geometry, but as soon as you exit it, the object gets back to its shape. This behavior is inteded, beacuse VisualARQ objects are not meant to be edited as a regular Rhino block.
On the other hand, if you create a new block with VisualARQ objects in it, you can edit that block, and identify VisualARQ objects as such. If this is not working for you, please share a file we can test.
It’s working for me, I know that I shouldn’t edit these blocks, but I can miss-click easily. Also, it’s very easy to break stuff by some less careful/experienced users and it might go unnoticed for some time.
I don’t know if some warning can be displayed or something to make it a bit more secure.
Yes, we could show some warning when running the BlockEdit command on a VisualARQ object.
To avoid this situation for new users, we already changed the normal “double-click” behavior of a block on a VisualARQ objects, which opens the Properties dialog instead of the block edit mode.