Feedback for gen 3 rhino/gh connector: Part 1

Hi Speckle team, first up would like to show appreciation for the rapid improvements in the app. However, there are some issues that are preventing me from upgrading to the v3 rhino/gh connectors. I split the feedback into 2 parts, part 1 covering rhino and part 2 covering gh

Rhino feedback

  1. Name in rhino block reflected as name of speckle object but name of brep not reflected?

  1. Properties that are tagged on to a block disappears when pulled back into rhino from speckle
  • Not an issue in legacy connector but is an issue in v3 connector
  • Works fine for breps in v3 connector



Hi @Julius_Ang , thanks for the report - we can definitely fix the missing user strings on blocks.

Can you clarify what you mean about the names on blocks vs brep? Is the screenshot you posted not the expected behavior?

1 Like

@clrkng Thanks for the prompt reply. Perhaps you could help me clarify what the text in blue should represent. As a user, I would expect it to reflect the name of the object I am sending across. So in the case of the block, the value of the parameter “name” is shown in the blue text. However, in the case of the brep, the value of the parameter “name” is not reflected in the blue text.

Hope this is clear. I added the rhino screenshots to clarify what I am pushing to speckle.


Ah I see - the difference in blue text in the viewer may be due to how the viewer parses objects vs instances for selection display (cc @alex to confirm).

On the connector side, the Rhino Name property will always be in the name field on your published object, and this is the field that will be read when you load your model in other connectors

The blue text is the first item that a user sees when clicking on an object. Would be good if it can always display the name since that is the key identifier of an object.

Quick update: receiving user strings on blocks and nested blocks in Rhino should be fixed now with the new 3.3.0 next-gen release