Troubleshooting

If BlenderSync for Revit seems to do nothing, you are usually dealing with one of a few common issues: the license is inactive, Blender or the server is not ready, the source view is not set up as expected, or the command has no valid target.

That experience can be confusing because BlenderSync is intentionally quiet. A missing result does not always mean something failed dramatically. Sometimes it means a requirement is missing. Sometimes it means the configured view is not showing what you expect. And sometimes the command completed normally without a separate success message.

This page starts with the quickest checks, then moves into source-view and command-specific causes.

When nothing appears to happen

One of the most common BlenderSync symptoms is simple: nothing visible appears in Blender, and Revit shows no obvious error.

That can happen when synchronization never starts, when required Blender-side components are missing, when the license is inactive, or when the command runs but has nothing valid to act on.

It is also important to remember that successful sync operations and successful Capture operations do not show a separate success message. A quiet result can therefore mean either "everything worked" or "something required was missing."

Before changing the project or re-running multiple commands, work through the checks below.

Start here

If sync appears to do nothing, check these first:

the machine has an active license or trial
Blender is running
BlenderSync for Blender is installed and enabled
the BlenderSync server is running
the Server and Port values in Setup are correct

These are the most common causes of silent failure.

Check license first

If the current machine is not activated and does not have an active trial, BlenderSync functionality is blocked.

In that state, only License remains available. If Setup, Changes, Selected, Capture, or Start are disabled, open License and confirm the current licensing state.

If needed, use Refresh Status to update the displayed license information.

Check Blender and the server

Blender must be running before Revit can synchronize with it.

BlenderSync for Blender must also be installed and enabled. If it is missing or disabled, synchronization from Revit will not happen.

The BlenderSync server must be running as well. In a normal setup, the server starts automatically when Blender starts. If the server is not running, or if Revit cannot reach it, BlenderSync may appear to do nothing.

If you are using the standard local setup, confirm the following in Setup:

Server: 127.0.0.1
Port: 3000

If either value is wrong, synchronization does not happen.

Check the source view

BlenderSync needs a valid 3D view in order to synchronize model content.

If the document contains no 3D views, there is no view available for synchronization. In that case, sync cannot occur until the project contains a usable 3D view.

Open Setup and confirm which Revit View is currently configured. If the result is unexpected, first make sure the expected source view is actually selected.

If the configured source view was removed from the document, BlenderSync falls back to the first available 3D view and stores that fallback. If the synchronized result suddenly changes in a way that does not make sense, this is one of the first things to verify.

Check what the configured view is showing

BlenderSync follows the configured 3D view. More specifically, it follows the final visible result of that view for model content.

That means content missing in Blender is often not missing because sync failed. It is missing because the configured source view is not currently showing it.

If the result is not what you expected, check the configured source view for:

section box
design options
phasing
Temporary Hide/Isolate
workset visibility
hidden categories
discipline-driven visibility
view templates
Hide in View
detail level

If an element is hidden in the configured source view because of any of those conditions, BlenderSync does not synchronize it as visible content.

A section box limits what is synchronized. If the section box changes, the synchronized result changes with it.

Phasing is followed through the configured 3D view result. If an element is hidden in that view because of the current phase or phase filter, it is not synchronized.

Design options are also followed through the configured view result. Geometry hidden by design option settings in the configured view is not synchronized.

The same logic applies to workset visibility, hidden categories, discipline-driven visibility, and Hide in View. BlenderSync follows the end result of the configured view rather than bypassing those view decisions.

If a view template is applied to the configured 3D view, that template can also affect the synchronized result through the resulting view state.

If Selected appears to do nothing

Selected only works when one or more valid 3D Revit elements are selected.

If you run Selected with no Revit elements selected, nothing happens.

Selected can still push selected elements even if they are hidden in the configured source view. However, elements pushed while hidden remain hidden in Blender. If you expect a hidden selected element to become visibly present in Blender right away, the issue may be the view state rather than the command itself.

If Capture appears to do nothing

Capture depends on selected Blender objects.

The command is run from Revit, but the capture source is the current Blender selection. If no Blender object is selected, running Capture does nothing.

If a capture updates an existing family instead of creating a new one, check whether the Blender object name matches a previously captured object. If a new family appears instead of updating the old one, check whether the Blender object was renamed before capture.

If the result looks different from Revit

Some differences are expected and should not be treated as sync failure.

Family geometry representation follows the detail level of the configured source view.
Phase visibility is followed, but phase graphic appearance is not reproduced.
View filters can affect the synchronized result through graphic overrides, but graphic overrides that only change color or line appearance without filter-based behavior are ignored.
Revit visual style does not carry over as a Blender viewport style.
In perspective views, crop region is ignored.
BlenderSync follows material assignment, but it does not claim full Revit material appearance parity.

If updates are missing or outdated

Both manual sync and LiveSync update material assignment and element transforms in Blender.

If an element is deleted in Revit and then synchronized, it is removed from Blender.
If a new element becomes visible in the configured 3D view and is then synchronized, it is created in Blender.
If an existing synchronized element changes geometry in Revit and is then synchronized, its Blender representation is updated.

If those expected updates are not appearing, return first to the source-view checks and the Blender/server checks. In most cases, the issue is either that the content is not currently visible in the configured view or that Revit is not actually connected to the BlenderSync server.

What BlenderSync does not show

BlenderSync for Revit provides limited user-facing status feedback during normal operation.

It does not show:

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

Because of that, the most reliable troubleshooting order is:

verify license state
verify Blender and server readiness
verify source-view setup
verify command conditions

When to revisit Setup

If the result is inconsistent, missing expected content, or suddenly different from before, reopen Setup and confirm:

the configured Revit View
the Display Name
the Server
the Port

This is especially important if the configured source view may have been deleted, renamed, or replaced in the project.

Next step

If the issue turns out to be configuration-related, return to Project Setup.

If the issue is really about command choice or workflow, return to Commands.