Skip to content

Reference

Use this page when you need a quick answer while working: where a command lives, what a field is called, which defaults BlenderSync uses, and what behavior to expect. For step-by-step guidance, use the main manual pages.

Ribbon layout

In Revit, the ribbon tab is named BlenderSync.

It contains three panels:

  • Settings
  • Sync
  • LiveSync

The commands are arranged like this:

  • Settings: License, Setup
  • Sync: Changes, Selected, Capture
  • LiveSync: Start or Stop

When LiveSync is running, Start changes to Stop.

Setup fields

The Setup dialog includes these fields:

  • Revit View
  • Display Name
  • Server
  • Port
  • Document ID

Default values

In a standard local setup, BlenderSync uses these defaults:

  • Server: 127.0.0.1
  • Port: 3000

By default, Display Name uses the Revit file name without the file extension.

Document ID is shown for debug purposes.

Setup behavior

Setup is stored per Revit document, and it stays with that document if it is opened on another machine.

Each Revit document has its own BlenderSync setup.

The source view must be a non-template 3D view.

Both orthographic and perspective 3D views are supported.

Section boxes are supported.

Behavior without explicit setup

BlenderSync can still work without an explicit Setup if the document contains a valid 3D view.

In that case, BlenderSync uses:

  • the first available non-template 3D view
  • the Revit file name without extension as Display Name
  • 127.0.0.1 as Server
  • 3000 as Port

If the document contains no 3D views, synchronization cannot occur.

If the configured source view later goes missing, BlenderSync falls back to the first available 3D view and stores that fallback.

Core sync behavior

BlenderSync follows the final visible result of the configured 3D view for model content.

Material assignment is synchronized, but BlenderSync does not claim full Revit material appearance parity.

Both Changes and LiveSync update material assignment and element transforms.

During synchronization:

  • deleted Revit elements are removed from Blender
  • newly visible elements in the configured 3D view are created in Blender
  • existing synchronized elements are updated in Blender when their Revit geometry changes

Multiple open documents

BlenderSync supports multiple open Revit documents.

Each open document has its own setup values and its own LiveSync state.

This means one document can use manual sync while another uses LiveSync.

Special elements

Alongside model content, BlenderSync can also sync a few supporting scene elements that help keep the Blender scene aligned with Revit.

When BlenderSync is running, the Revit camera is synced as a Blender camera. You can view through it just like any other Blender camera.

If the Blender Sun Position add-on is enabled, BlenderSync also syncs the Revit time and location context so Blender sun direction and lighting state can follow Revit more closely.

Synchronized elements are parented to the survey base point so the scene stays positioned relative to that shared reference.

Blender-side context

In Blender, synchronized content is grouped under a document-level parent object.

That parent can be moved in Blender without changing Revit coordinates.

This is Blender-side workflow context only.

Quiet behavior

BlenderSync for Revit is intentionally quiet during normal use.

Successful sync operations complete without a separate success message.

Successful Capture operations also complete without a separate success message.

BlenderSync for Revit does not provide:

  • a progress indicator
  • a synchronization status indicator
  • user-facing connection errors for normal sync failures
  • user-facing logs
  • user-facing debug output beyond Document ID in Setup