Freestanding wardrobe

Would it be possible to have the option to choose the type of wardrobe to include in the project? Currently, the wardrobe is designed as a built-in unit. I would also like to have the possibility to use a freestanding wardrobe, with a back panel and side uprights. Thank you.

Hi @Alessandro_Barbisan the fact the wardrobe is generated only with some faces is due to an error in the Grasshopper definition used in that style, that has been fixed in VisualARQ 3.4. From your other post I’ve seen you have already installed the new version and updated the wardrobe objects.

1 Like

Hi @fsalla I’m still having the same problem when I start a new project using my personalized template. I tried deleting all the elements that have the issue and pasting them from a new project where they work fine, but when I import them, the faces disappear again. I cant’ make a new template from a new VisualArq template because i have a lot of personalized item and layers. I’ve done some tests and i thinks is a visualarq bug because i’ve done a new project from a native visualarq templates, after i saved and reopen it the panels disappear again. Thanks

Hi @fsalla There are a lot of problems with most pieces of furniture, like wardrobes, and with some elements such as the WC. Every time I add some elements or furniture, some parts disappear.

Hi @fsalla i recorded a video so you can see what happened

Hi @Alessandro_Barbisan,

Thank you for sharing the video, it was very helpful to understand exactly what was happening.
I also tested it on my computer and had the same result.
As you mentioned, it seems to be a bug.
I’ll report this issue in our bug tracker and keep you updated once it has been fixed.

Best,
Melissa

1 Like

Thank you @MCosta i appreciated it!

1 Like

Well the 3.4 fix must have broken other things.

It might be possible they dont disappear, but they move to a far distant place.

Like in my case, suddenly all wardrobes (default style) have parts scattered all around.

Hi @ng5_Alex

I tested it on my computer with the latest version of VisualARQ (3.7 RC1) and I can confirm that this issue is happening as well, especially with wardrobes, wall cabinets, and similar furniture elements.
The issue has already been reported, and I’ve added your vote to it.
I will get back to you as soon as possible once we fix this error and the previous one.
Best,
Melissa

My vote on a bug? That’s a first…

At the moment i am not able to deliver anything for today’s deadline to clients, because most of the furniture suddenly is broken, with parts floating in drawings and rendered views, side parts missing in cabinets.

Hi @ng5_Alex can you import the two wardrobe styles from the .val attached, and see if the issue of the spread parts of the wardrobe object is fixed? Select the objects involved and run the vaUpdate command to ensure the objects update.

Furniture and Elements NEW - meters.val (1.6 MB)

PD: If you cannot delete a style from the corresponding styles dialog, it means there is an instance in use in the model, or that style is still the “current” one, which means it was the last style chosen in the insert dialog of the corresponding object type command.

1 Like

Yes there was one item i had not seen.

When i open a new drawing with the visualarq meter template the wardrobes and cabinets are working as they should.

So after deleting the offending styles from my working file, i tried copy-pasting the working template wardrobe to my working file and stiil scattered parts..

Somehow my working file is corrupted.

I will try the val file and will report back.

thank you

alexandros

Imported the va file, vaupdated everything and all items reverted back to their original properties (both style and object).

Also after the update for all updated items plan visibility is reverted to projection with overhead, making 1st level wardrobes appear in ground floor plans, which should not happen and was not happening with previous versions.

Regarding the geometry, cabinets seem ok, wardrobes although reset and upadated still have scattered parts.

I insist that maybe something is also wrong with my working file, because if i open an earlier working file (i do incremental saves) everything is working as it should.

Left is working file and right is previous version

and the wardrobe style afte vastyleimport and vaupdate

audit gives this back

i have only one block, which is a bunch of dimensions. the other must be arq.

Document Manifest:
Texture Mapping: 1085 active, 1 system.
Material: 83914 active, 2 system.
Line Pattern: 8 active, 3 system.
Layer: 40 active, 1 system.
Group: none.
TextStyle: none.
Annotation Style: 4 active, 12 system.
Light: none.
Hatch Pattern: 14 active, 9 system.
InstanceDefinition[375] “*EmptyDefinition” deleted component has non-empty name.
Block: Error: differences between model table[375] and manifest information.
Block: Error: 1 errors found. Model: 375 active, 0 deleted. Manifest: 375 active, 1 deleted.
Model Geometry: 24914 active.

Error: 110354 model components (0 deleted). 28 system components. 110383 manifest items

InstanceDefinition[375] "*EmptyDefinition" deleted component has non-empty name.

m_instance_definition_table[268]->ObjectCount() = 0.
m_instance_definition_table[341]->ObjectCount() = 0.
m_instance_definition_table[342]->ObjectCount() = 0.
m_instance_definition_table[343]->ObjectCount() = 0.
m_instance_definition_table[375]->ObjectCount() = 0.
Audit Summary:
0 object errors detected.
0 linetype table errors detected.
0 layer table errors detected.
5 block table errors detected.
0 font table errors detected.
0 annotation style table errors detected.
Table tally:
40 layers
375 instance definitions
4 annotation styles
0 fonts
8 linetypes
83914 rendering materials
Object tally:
682 normal objects
0 locked objects
0 hidden objects
0 deleted objects (in undo buffer)
24232 block definition objects
0 reference normal objects
0 reference locked objects
0 reference hidden objects
0 reference block definition objects
Audit found problems.

Hi @fsalla I tried importing this library into a new Rhino file template, and it worked fine after saving and reopening it. The same happens if I import the library into a project file that has the issue — I still get the old object with the problem instead of the updated one. The only difference is that the new objects are named in English, while the corrupted ones are named in Italian.

Hi @ng5_Alex once the new .val is imported, the object styles in the model with the same name as those in the .val should be overriten by them.
I’m providing you with an updated version of the wardrobes, in this .val:
Wardrobes VisualARQ 3.7.val (237.5 KB)

(@Alessandro_Barbisan please try your wardrobes with that new .val as well. If you have any problems, send me the 3dm file.)

We will revise why the “Plan visibility” changes when refreshing these styles from the new .val, but it shouldn’t.

This should not happen if those objects are in a different level. Can you share a 3dm file, so we can inspect this issue?
I recommend using the last VisualARQ 3.6 update (we have published a new one today: Update - VisualARQ), or the 3.7 RC2: VisualARQ 3 - Version 3.7 RC2 released

Hi @fsalla I tested the new .val file you attached, and with VisualARQ 3.6.1 these two pieces of furniture work well, but the other ones are still corrupted. However, the 2D representation is not correct, it shows a solid black hatch.

@Alessandro_Barbisan which other ones?

This is a new change added to that furniture style, so that the wardrobe’s 2D representation hides/masks any objects underneath it (like a Hatch), in plan views. You can just change the print and display color of that Hatch component to White (or delete it, if you want that Wardrobe to work as in previous versions):

@fsalla the old ones that are inside the template of new version.

Ok i will test it. Thank you

Ah, of course. The old ones will remain if they have a different name as those you have imported from that new .val file. You will need to change the wardrobe objects from the former style to the new one.