Too bad that you can’t reproduce it… Maybe some users who experienced similar problems could chime in and try?
@fsalla I suspect I failed at presenting the steps to follow. I can reproduce this bug on two computers and both on Rhino 8 + VA 3 and Rhino 7 + VA 2.
I have a similar problem where sometimes the predefined furniture (in this case “Bed - Single”) disappears, also in the latest update. Probably this is related since the predefined furniture blocks are in fact grasshopper styles?
I’m trying to reproduce the problem by creating a new document with the VisualARQ 3 templates, placing a bed and copying it. Sometimes both beds disappears and sometimes they don’t. It seems to be more likely to happen when the units are not in meters, but it could also be random.
@Czaja @studioselva If you can figure out any patterns or steps to follow to reproduce this behavior, it will be a big help. I’m still trying it but without success, even with the files you people share.
Today I did exactly the same as shown on my video on yet another completely different PC and successfully reproduced the bug. I can reproduce it across multiple Windows, Rhino, and VisualARQ versions.
My video shows the whole procedure and keyboard actions. It is possible that it just works for you, but with each new computer, I suspect even more that the steps I’m making are not reproduced in 100%.
It would be best if you could record your screen with keyboard action and share it, so I can check if you follow my steps correctly.
I’m recording my screen with OBS and use the SwordSoft Mousetrack to show keyboard actions.
@Czaja Thanks for your efforts to discover the reason of this problem. I’ve tried to reproduce carefully the same steps as in your video, with no luck.
To be fair, I should try it exactly with the same files as yours, if you can share them.
Also, I can see you have many Grasshopper add-ons that I don’t have. Perhaps one of them is involved in this problem, and that would explain why I cannot reproduce it. Can you disable all your GH addons and try to reproduce this error? You can just rename the folder “Libraries” where the addons are located (you can find that folder if you go to the GH Menu File > Special Folders > Component Folders.
Hi, thanks for the video. I don’t see you doing that:
You always end up Selecting a Curve, what you need to do is to hit the escape button once you are asked to do that - thus this operation will not be successful.
@Czaja That’s it! thanks!! I could reproduce it after that indication, that I missed before (sorry). That’s a big step forward to fix this problem. I’ll keep you posted.
That’s great! I hope it will lead to resolving this long-standing issue and it will help make VA Styles more robust.
Hi all! I’ve good news to share. We have been able to fix this issue (finally) and we will include it in the VisualARQ 3.2 update we will release next week.
Since you have been “suffering” this problem for so long, I’m sharing here an internal version of the 3.2 so you can test it out:
http://visualarq.s3.amazonaws.com/download/visualarq-3.3.0.19478-rhino8-setup-snapshot.msi
I’d like to thank you all for your patience and collaboration to figure out the reason of this bug, specially to @Czaja who has given the decisive hint.
It’s still acting up, probably because of something else. I made a simple VA GH Style Element with Blocks. After closing and reopening Rhino file for some reason they Elements disappear during any modifications to the Style configuration or moving any instance of a given Style configuration.
Belka Strop 2.3dm (19.4 MB)
VA Belka.gh (12.8 KB)
BTW.
Running Purge command in Rhino will delete Blocks referenced by VA GH Styles which is of course a disaster.
Also, while copying Element that references some Block Definition to the file without that Block, Block Definition is not copied along, so element disappears.
Hi @Czaja, thanks for reporting this. I believe this is all related to that problem. When Rhino purges the Block definitions, it does not consider those that are being used by VisualARQ’s GH Styles. When those objects update, they don’t find the block definition and the geometry is not generated.
We will revise this behavior.
Teh “Purge” issue has been solved in VisualARQ 3.5. RC1 will be published on June 4th.
Enric
