Rhino Plugin
Rhino plugin introduction tutorial • Last modified on 7/5/2019 • edit

Opening the plugin

After you've installed speckle, you'll need to initialise speckle inside Rhino by typing SpecklePanel in the command line. Afterwards, click Show and you should see the panel containing the speckle plugin show up:


Creating an account

First off, if you haven't, create an account on the speckle server of your choice. In case you don't have one, and just want to test out speckle, you can use https://hestia.speckle.works/api! Do be advised that this is a test server - use at your own risk. The diagram below explains most of the steps.


Sending & Receiving

You can now create receivers and senders. To create a sender, select some geometry, click the add button and select "add sender". First select your account, then give your stream a name, and voila! With senders, remember you can access some extra options by clicking the big arrow button next to its name, specifically:

  • add & remove objects: you're not limited to your original selection.
  • play & pause: by default, senders automatically send data out, whenever they detect a change. You can change this behaviour by hitting the "pause" button.
  • delete: you can always remove a sender for good.


Receivers can be created by clicking on the big plus button in the lower right hand corner, and selecting "new receiver". First select the server you want to receive a stream from, then search for one or simply directly input the streamId. In rhino, receivers do not "bake" geometry. You need to do that manually! Some things to note:

  • Speckle will try and respect the original sender's layer structure
  • If you bake the stream again, it will replace its previous geometry. In case you want to keep a copy, duplicate the layers first!
  • Too many updates? You can always pause the receiver, and update whenever you want.


Beyond Rhino

Of course, if you send something to speckle, it's going to be available in the wider speckle ecosystem. So you can:


If you have any ytrouble, head over to our forum and buzz, or hit us up on slack. If you think it's a more of a bug rather than a question, report it on github!