How it works

Rhino2Blender is two programs that talk over a TCP socket.

The Blender add-on is the server. It opens a port and waits. The Rhino plugin is the client. It connects out, indexes the open document, sends it once in full, and then streams every subsequent document change as an incremental update.

Stage

Rhino plugin (client, dockable panel)

Blender add-on (server, View3D sidebar)

1. Handshake

Connects to Blender's port

→

Asks you to allow the connection

←

Replies with its version and the textures it already has

2. Full sync

Indexes the document, tessellates it on background threads and fingerprints every object

→

Builds collections, meshes, materials, lights and cameras

3. Incremental updates

Sends only what changed, as compressed binary buffers

→

Updates those objects and nothing else

Back to Rhino

Creates the objects it receives

←

Send to Rhino pushes the selected objects

Both applications must be running. There is no intermediate file, and nothing is written to disk except a texture cache.

The connection carries a source_name, taken from the Rhino document filename. Everything the add-on builds is namespaced by that name, which is what allows several Rhino documents to share one Blender scene without colliding.