If nested blocks are important to support, we can bump that feature up in priority!
Currently, non-nested blocks should still be received correctly back in Rhino, even if they are not displayed properly in the viewer - let me know if you’re having issues with this.
The transform property for our Speckle block is expecting a 4x4 transform matrix where:
- the 3x3 sub-matrix determines scaling and rotation
- the 4th column’s 1st 3 entries define translation
- the 4th row is an identity row
Does VisualARQ use the same convention for block transforms?