When referencing beam objects from Worksession, and then attempting to bake them as beams, Rhino crashes.
Rh8 SR29
VA3 3.9.0.1.14858 (2026/03/19)
Hi Toni, thanks for reporting this issue and the clear steps to reproduce it. I’ll let you know when we fix this.
Hi @Toni_Osterlund we have fixed the crash reported here in the VisualARQ 3.10 RC2 update (VisualARQ 3 - Version 3.10 RC2 released)
However, VisualARQ objects from non active files across workessions can’t be baked from Grasshopper right not. This is something hard to implement, so we leave it for a future version. At least, the program won’t crash because of this.
@fsalla
I tested the RC2 version, but now the beam objects stop at the Orient component with a Solution exception. Is this intended solution?
Edit:
All transformations seem to have stopped working with Worksessioned beams.
I even restarted teh computer, and re-saved the Rhino-file with the new RC2 version.
@fsalla @wim
Ok, this is peculiar.
I reverted to RC1 - no luck
Then I reverted to 3.9 - no luck, the same error persists
I did update to SR30 in between here, so could there be something in SR30 update that broke
the connection between VisualARQ Worksession references and Gh Transformations?
Wim, how could I revert back to SR29 to test this?
Update:
I remembered that I still have SR29 on another computer.
So confirming that the combination of Rhino8-SR29 and VA 3.3.0.19595 works.
Update 2:
I updated to VA RC2 with SR29, and problem appeared.
I’ll try find the latest working VA version, which according to my original post was 3.9.
Ok,
the version 3.9 seems to work. When I earlier said I ‘reverted’ to an earlier version, I did not do it thoroughly enough. I could go back to earlier version, only after Uninstall through Windows.
Then I installed RC1, in connection to SR29, and it seems to work as well.
Then testing with RC2, and there it fails.
So, long story short… RC2 breaks the connection of Worksession objects and Gh Transformations..
@Toni_Osterlund VisualARQ objects in non-active files across worksessions can’t be copied, moved, etc… This has never been possible in VisualARQ 3.9 or in former versions. Supporting this feature is quite challenging, and we will study it for future versions. Once it works in the Rhino model space, it will work with objects referenced in Grasshopper.
When you were referencing these objects in Grasshopper with the 3.9 version, you could apply some transformations, but that was useless, since you could not bake these objects (Rhino crashed, as you experienced). We have fixed this crash in the 3.10 RC2, but this means you cannot apply these transformation on VisualARQ objects in Grasshopper, as it is not possible either in the Model space.
I would not call them useless, as I could still generate Make2D and explode to breps in their Transformed positions.
I am not 100% sure, have I used Transformed VARQ objects, or just breps in the past scripts.
If this is error is by-design, then I need to conform to this new limitation.
That makes sense. However, even though you could move, orient, explode, etc.. referenced objects before, this could lead to crashes (like the baking one) and other unexpected issues, so we have had to limit this functionality until we support cloning objects from non active files.
@Toni_Osterlund we will try to find an intermediate solution where you can still move, orient, explode, etc, objects in Grasshopper but not bake them (until cloning objects from non active files is supported).
That sounds amazing. Thank you.
