@fsalla Yes exactly. I’ve done some new tests and some properties like width and depth don’t work properly. I attached a screenshot.
The back panel and the side panels don’t move.
@fsalla Yes exactly. I’ve done some new tests and some properties like width and depth don’t work properly. I attached a screenshot.
The back panel and the side panels don’t move.
Is that the new wardrobe style? can you share that 3dm file?
@fsalla yes the wardorobe that have properties problem is the new one. Tomorrow i will send you the file by wetransfer.
Hi @Alessandro_Barbisan I could open your file, and after running the vaUpdate on that wardrobe, it’s generated properly. Does that work in your case?

@fsalla oh wow, I hadn’t tried the vaupdate command! Anyway, it works for me too. Thank you!
@fsalla I’ve done some more tests with the new wardrobe, and if you change the alignment, something goes wrong.
Hi @Alessandro_Barbisan I’m trying to reproduce this behavior, but changing the alignment works as expected.

Is that the new wardrobe or the other one?
If you run the vaUpdate command on those, do they regenerate properly? If they don’t, please send me that file again.
@fsalla The bug is not caused by changing the alignment after the object has been inserted, but rather while adding the items. I would like to specify that this happens the second time you try to insert the cabinet. The first time you insert it, everything works correctly (you can change the alignment to center, right, or left). However, the second time, while inserting it and changing the alignment, the error occurs.
Hello @fsalla ,
this time with 3.7 val file wardrobes are updated without any scattered parts, even without updating to VA newest version, but still using v. 3.6.
Best thing would be if such val update did not reset all the values of every instance of the objects, because we have to redraw and set again for every wardrobe the number of leaves, their dimensions etc.
This has to do with the previous comment, settings are reverted to defaults, so if i had set the wardrobe to projection only, after the update it reverts to default projection with overhead.
The 3.7 val file resolved somehow this problem too. Now i dont see in the ground floor wardrobes that are designed in the 1st floor.
Thank you,
alex
I have also an issue with element, after 3.7 install, the list of elements are very limited - with 3.6 i had more objects to choose from.
The list of objects in VisualARQ templates is the same in version 3.6 than in version 3.7. You need to start a document from a :VisualARQ template to see them all.
The .val I’ve attached in this topic is only a fix for the 2 wardrobe furniture styles existing in VisualARQ templates.
I agree. We will see if this is feasible.
@ng5_Alex I cannot reproduce this. I’m seeing that updating a VisualARQ object from a new style imported from a .val resets its dimensions to default, but the Plan Visibility status remains the same.
If you can share an example of it, I’ll try to reproduce it.
@fsalla i am sorry and i stand corrected, after redoing the va style import, projection setting does not seem to change or revert to default.
@fsalla hi Francesc, any news about that? Did you reproduce the alignment bug?
I can’t reproduce this issue. I may require a gif, video or detailed explanation of how are you doing this in order to reproduce it exactly the same steps.
@fsalla Here you can see the bug:
Hi @Alessandro_Barbisan thanks for the video. This is weird. I’m repeating exactly the same steps as you do, but everything works as expected. I’ll investigate about this a little bit more. Can you share the file just like it is when you see that error?
@fsalla here you can download the file.
ARMADIO.3dm (5.1 MB)
Hi @Alessandro_Barbisan, watch this:

If you reopen the file and update the wardrobes, do they fix?
I have no idea why the wardrobes are not generated properly in your case. Do you have other Grasshopper add-ons that may be interfering here? You can try to disable them just for testing.