Rhino to Blender: Keep NURBS Precision and Your Blender Scene
Rhino is precise. Blender is expressive. The gap between them is a mesh conversion nobody wants to babysit.
NURBS Do Not Travel Well
Rhino works in NURBS surfaces. Blender works in polygons. Somewhere between the two, every Rhino to Blender workflow has to make a decision about meshing, and the default answer is usually wrong in one direction or the other.
Export too coarse and a curved façade becomes visibly faceted in the render. Export too fine and a single stair core turns into two million triangles that make the Blender viewport unusable.
Blocks are the second casualty. A Rhino model that uses blocks for windows, furniture or repeated structural elements normally arrives in Blender fully exploded, with every instance carrying its own copy of the geometry.
Meshing You Control, Layers That Survive
CAD Bridger lets you set the meshing level as part of the sync rules rather than discovering it after the import. You can send the site context coarse and the detailed façade fine, in the same operation.
Rhino layers map to Blender collections, so the organisation you already built stays useful. Blocks come through as instances. Named objects keep their names, which matters when you want to select something specific inside a large scene.
Materials assigned in Rhino arrive as Blender materials with sensible node setups you can then take further in Cycles.
Change the Model, Keep the Render
Architectural projects change until the deadline. That is the real reason Rhino to Blender workflows fall apart — not the first export, but the fifteenth.
CAD Bridger tracks objects between the two applications, so resending an updated Rhino model updates matching objects in Blender instead of dumping a second copy of the building next to the first. Your Blender materials, lighting, cameras, modifiers and asset library additions stay where you put them.
Grasshopper users get the same benefit for definitions that regenerate geometry constantly.
Availability
The Rhino connector is available now. If you want the longer story behind why this exists, read the write-up on live sync and moving away from V-Ray.
Frequently asked questions
How does CAD Bridger handle NURBS meshing?
Meshing density is part of the sync rules you set before sending, so you choose how finely curved surfaces are tessellated per layer or object rather than accepting a single global export setting.
Do Rhino blocks stay as instances in Blender?
Yes. Blocks come across as instances rather than exploded copies, which keeps repeated elements like windows and furniture light.
Can I keep working in Rhino while the Blender scene is set up?
Yes. That is the point of the connector — you keep modelling in Rhino and resend, and the Blender scene updates in place.