LiveSync — Connecting Rhino and Lumion
LiveSync is a live bridge between your Rhino model and Lumion. Changes in Rhino update in Lumion in real time.
You are working with Lumion Education, not Lumion Professional. Some features, material libraries, and object content differ from the professional version. These cards reflect the Education version specifically.
Why this matters
Without LiveSync, you would export your Rhino model, import it into Lumion, assign materials, realize you need to fix the model, re-export, re-import, and lose your material assignments. LiveSync eliminates that cycle — Rhino and Lumion stay connected, and model changes in Rhino propagate to Lumion automatically without disrupting the materials, entourage, and camera positions you've already set up. This is the professional workflow for real-time rendering in design practice.
Setup and activation
| Step | What to do |
|---|---|
| 1. Verify the plugin | The Lumion LiveSync plugin for Rhino can be installed by dragging the livesync install file from the class folder into an active Rhino file. It adds a LiveSync panel to the Rhino interface. If you don't see it, go to Rhino Panels → Lumion LiveSync. |
| 2. Open both applications | Have Rhino and Lumion open simultaneously. They communicate via a local connection — both must be running. |
| 3. Start LiveSync in Lumion | In Lumion Build Mode, click Import → LiveSync. Select Rhino from the application list. Lumion will wait for Rhino to initiate. |
| 4. Start LiveSync in Rhino | In the Lumion LiveSync panel in Rhino, click Start LiveSync. The panel should show "Connected" and your model should appear in Lumion. |
| 5. Verify layer materials | Before making any material assignments in Lumion, verify that each Rhino layer arrived as a distinct material. In Lumion, click any surface — the material picker should show the unique color you assigned in Rhino as the current material. |
What LiveSync transfers and what it doesn't
| Transfers with LiveSync | Does not transfer with LiveSync |
|---|---|
| Surface geometry (NURBS and mesh) | Lumion material assignments (these are Lumion-side only) |
| Rhino layer structure as material groups | Entourage objects placed in Lumion |
| Model changes made in Rhino | Camera positions saved in Photo/Video Mode |
| Added or removed geometry | Image FX settings |
| Layer visibility changes (with delay) | Weather and lighting settings |
Workflow rhythm with LiveSync
The most efficient approach: model in Rhino, assign materials in Lumion, model more in Rhino, refine materials. The two applications are designed to be used simultaneously in this iterative way. You don't need to finish the model before starting Lumion work — seeing the model in Lumion while modeling often reveals spatial problems that are invisible in Rhino's wireframe or shaded modes.
That said: complete the core terrain and hardscape modeling before starting material work. Materials assigned to surfaces that are later split or replaced in Rhino will need to be reassigned. Get the geometry right first, then invest time in materials.
Try this
With LiveSync active, make a visible change in Rhino — move an object, change a layer color, add a simple extruded form. Watch Lumion update. Then make a material assignment in Lumion and switch back to Rhino to make another model change. Verify that the Lumion material assignment survived the model update. Understanding exactly what transfers and what is preserved in Lumion-only is the key to working efficiently across both applications.
What breaks
Surfaces losing materials after Rhino edits — if you delete a surface in Rhino and replace it, the new surface is a new object and won't carry the Lumion material from the deleted one. Minimize geometry replacement after material work begins. Fix modeling problems before investing in Lumion materials.
LiveSync not connecting — if the connection fails, close both applications and restart Lumion first, then Rhino. Try initiating the connection from Lumion before clicking Start in Rhino. Both applications need to be running as the same user without conflicting firewall settings blocking local communication.