I wonder whether to continue with VisualArq because despite the improvements in the new versions, it is still extremely slow. I love working in rhino and varq is full of qualities but it really takes up too much of my time…
I’m an architect, and we work on medium to large projects. As soon as the models exceed 200MB (for a building of 50 housing units, this happens as soon as the joinery and railings are designed), it becomes impossible to work on them without waiting several minutes for each order…
I’m going to order a new PC to give it a final try. Could you tell me what to prioritize? - CPU type, graphics card type. Do I need a quadro type pro card? thank you in advance (for information, today I am working on a bi xeon silver 4114 + quadro P4000 + 64 GB of RAM but that is not enough).
Hi Guillaume,
We have recently identified some significant performance issues in VisualARQ 3, particularly when used in large models, as probably this kind of document was tested by a few users, including ourselves, during the beta phase.
This week, I have been working specifically to pinpoint the main challenges, and I believe I’ve identified key areas affecting performance:
- Automatic intersections between objects (such as walls, slabs, stairs, columns, beams, and roofs)
- Automatic removal of tangent lines between components sharing the same section hatch
- Regeneration of multiple objects, which seems to be limited to a single thread when objects interfere with each other
Currently, I am focusing on implementing fixes, optimizations, and, in certain cases, disabling or making these features optional to enhance model editing speed.
If possible, it would be extremely beneficial if you could share one of these complex models with us to test these improvements. While I can create sample models, they often lack the complexity of real-world applications. Additionally, I can help identify any errors or issues in the file that might need attention on your end. You can send the model to visualarq@asuni.com.
Thank you for your collaboration.
Best regards,
Enric
Hello Enric, Thank you for your quick answer
Indeed, I have the impression that VARQ is trying to manage intersections in real time, which requires a lot of resources. Couldn’t we have less frequent updates of intersections (or at adjustable intervals)?. The same goes for the display, because when building a complex element like a guardrail or a curtain wall, rhino has a lot of trouble remaining fluid because it calculates the distribution of the elements in real time… The display could not be in “degraded” mode during editing and updated at the end?
I will send you a test file by email.
Sincerely
Guillaume
PS:
below is the screenshot of my command line after moving objects
small clarification, the problem gets worse when you work on the file for a long time…
I am having similar issues with VisualArq 3… I’m noticing that in particular opening up objects like windows or doors to customize sizes can take several minutes. I’m not sure why that function is so resource heavy. I am using a powerful Lenovo Vantage with a GEForce RTX 4090 so I shouldn’t be having any issues… the files is around 800MB.
Hi @avatarlucas can you share a file to test this slow performance? you can send it to visualarq@asuni.com
A plan view on one model is taking 10 minutes to process and over 5 minutes just to save… I’m really not clear what’s going on with this
Hi @avatarlucas we need the 3dm file to figure out what’s happening.
I’m afraid the file is over 400MB, and the other one 800MB. How can I send that? I was awaiting some kind of dropbox link from you. Thanks
You can use https://wetransfer.com/ for those file sizes.