VisualARQ 3.1 - Release Candidate 2 is now available for download.
NOTE: This is a release candidate (RC), which means it is not the final version, but it has been tested internally and we consider it stable enough to be tested by end users. VisualARQ 3.1 is scheduled for release on Wednesday, December 4th, 2024.
This release fixes most of the problems and crashes reported by users. Please report any problems or suggestions here or email us at visualarq@asuni.com.
Here is the list of changes:
Improvements (1)
Template:
#12720: Create a Layer for Guides in VisualARQ templates
Changes (4)
Style:
#11254: Change message when importing a not compatible .val file
Template:
#14551: Remove the “Hidden” linetype assigned to the layer “Guides”
#14361: Changes in VisualARQ templates
#10879: Set the default layer for element object in VA templates
Fixed Errors (12)
Attributes:
#10494: Keep section attributes when exploding VisualARQ objects
Crash:
#14435: Crash when listing Elements created as Grasshopper styles
Display:
#14414: VisualARQ sections and levels don’t respect the “shadows ignore user defined clipping planes” setting
IFC:
#14470: Missing geometry in IFC 4 file
Level:
#14529: Objects disappear in top viewport when activating a cut plane
Object: Plan View:
#14471: Space labels and tags are generated as 2D curves in plan views
Object: Section:
#14507: Jogged section doesn’t work in this file
Object: Slab:
#14339: Slab layer thicknesses change when saving a Rhino 8 file as Rhino 7 file
Object: Table:
#14450: Crash while editing a table
Object: Window:
#14087: Window doesn’t show the overhead representation
#12919: Window geometry is not displayed
Print:
#14473: Print width of Annotation objects are not correct when printing to vector output using Wireframe display
Thank you for your suggestion. While I understand the convenience of consolidating all release updates into a single thread, I believe this approach might create some confusion for users.
For instance, new users visiting the thread might assume the first post contains the latest release, which could lead to misunderstandings if the thread isn’t updated correctly. Additionally, editing the first post to reflect the latest release could make earlier replies appear out of context. I experimented with this format during the VisualARQ 3 Beta updates and found the results less than ideal.
To address your concern, I can post a link to the new release thread in the previous one, ensuring continuity and easy navigation for users. Alternatively, you can track the “VisualARQ > News” category, which will notify you of any new releases.
On a related note, we’re actively working on a new update system for VisualARQ. This system will allow automatic download and installation of updates (with user confirmation), and you’ll also be able to choose between “Stable releases” and “Release candidates,” similar to Rhino’s update channels.
Thank you for your feedback, and please don’t hesitate to share any additional suggestions.
wow thank you @enric for this comprehensive answer and solution!
I thought bc. rhino does the same with its releases it might be good you do it aswell.
Enric, when a wall style has a section hatch pattern assigned, then it seems impossible to change the hatch style from the Object Properties menu. Is there a way to override the generic hatch pattern of wall style for individual wall objects? Is it necessary to create new wall style for the desired hatches?
For instance, I need some walls belonging to a Generic Wall Style of 30cm, to have solid hatch and some others to have single line hatch. Do I need to create two individual 30cm wall styles for each hatch?
VisualARQ objects function similarly to Rhino blocks (in fact, they are blocks). Each part of a VisualARQ object is essentially geometry nested inside the block. The attributes you assign to a style component are applied to the geometry within the block. However, if the geometry inside the block has attributes set to anything other than “By Parent,” those attributes won’t be affected by changes to the main object’s properties.
To address your issue, you have two options:
Create two separate wall styles with the desired attributes.
Use a single wall style with attributes set to “By Parent” or “By Layer,” and then adjust the attributes at the object level.
Let me know if you have any questions or need further clarification!
We are pleased to announce that VisualARQ 3.1 has been released. This update addresses numerous issues and crashes reported by users, enhancing the overall stability and performance of the software. For a detailed list of changes and improvements, please refer to the release notes.
Additionally, we have published VisualARQ 3.2 Release Candidate 1 for those who wish to continue testing new features before their official release.
NOTE: This is a release candidate (RC), which means it is not the final version, but it has been tested internally and we consider it stable enough to be tested by end users. VisualARQ 3.1 is scheduled for release on Wednesday, December 4th, 2024.
