Hi, thank you very much for updating the VisualARQ version. It has greatly improved my work efficiency.
I encountered an issue while using VisualARQ 3 Beta: the Box mapping in Rhino 8 doesn’t work for VisualARQ objects such as walls, and the Match mapping feature also doesn’t work. However, these functions work fine in Rhino 7.
Do you have any tips or tricks to solve this issue?
Sincere thanks, looking forward to your reply.
Hi @jiang_wu you are right, it seems something is broken with the assignment of texture mappings on VisualARQ objects. We will take a look at this problem and get back to you when we fix it.
Meantime, try to use a material that integrates the WCS mapping on the material.
Thank you very much for your response. I look forward to the fixed version, and I will try as you suggested. Currently, this bug also affects texture mappings in Enscape.
Hi @jiang_wu we have fixed this error in the next Beta. I’ll let you know when we publish it.
Thank you, looking forward to your good news.
Hi @jiang_wu you can already download the new Beta version that fixes this issue with texture mappings: Rhinoceros 8 - VisualARQ
Dear friend, I couldn’t wait to try out the new version, and it has successfully addressed many issues. However, I’ve noticed a bug with the Box mapping on column objects, causing all four sides of the column to lack texture ,as shown in the demo below. Is this issue addressed in the new release? Thank you very much, looking forward to your reply.
Hi @jiang_wu I cannot reproduce this behavior with a Rhino textured material. Can you try it instead of the Enscape material, and check if it works?
Also, try to use textured materials that include the WCS mapping. It helps to keep the size of the texture on the object regardless of the object dimensions:
Hi, dear friend,
After testing, I found that mapping assigned material to the column behaves differently in different software, as shown in the image below. On the left is Enscape, which appears abnormal in the Rhino viewport but renders correctly; on the right is Rhino’s custom material, which appears normal in the viewport but abnormal when rendered in Enscape. Since Enscape material can render correctly, my problem is solved. I sincerely thank you for your support and help.
Additionally, I have encountered another issue where the file display occasionally switches to wireframe mode, but it returns to normal upon reopening.such as the third image.
Thank you very much, looking forward to your reply.
Hi! I may require the file to see if I can reproduce this behavior.
Hi dear friend,due to the limited upload capacity, I selected a portion of the file. It takes some time to operate in wireframe mode, and I’m not sure if the incomplete file can be reproduced. Looking forward to your reply.
1.part1.rar (19 MB)
1.part2.rar (8.0 MB)
HI, I’m not able to reproduce this display issue. It looks fine on my end. Perhaps it fails with the full model…
Hi, dear friend, do you have an email? I can send you all the models.
Sure: visualarq@asuni.com
Hello dear friend, the document has been sent to your email. The filename is: N16-3900-8.3dm. Looking forward to your reply.
I got it, but I couldn’t reproduce the error. Try to update Rhino 8 to the latest SR, just in case. Or disable other third-party plug-ins just to double-check if the problem persists.
Thank you very much, I will give it a try.
I am having similar issues with box mapping. The mapping is not working at all for VRay in Rhino 8. I have to explode the object for it to work. There is also no option for WCS/OCS on VRay.
Do you mean on VisualARQ objects?
It should work. If you have any sample files where this doesn’t work, please share them so we can take a look.
(Texture mapping can’t be applied to each component of a VisualARQ object style, but it should work for the whole object.)
Yes @fsalla I mean on a slab specifically. For some reason after returning to it though I don’t seem to be able to recreate the issue. One thing though, I’ve noticed that if the mapping is changed on the visualarq object then it immediately deletes all material as well and you need to reapply it. Is this by design or a flaw? That doesn’t happen with normal Rhino objects.
Can I ask also why VArq doesn’t enable mapping for each component. This is def something that should be reconsidered… did you ever release the updated Beta by the way? The curtain wall issue really impacted my work unfortunately and now the deadline has passed.