Skip to content

Troubleshooting

Server won't start

Symptom: Clicking the start button in the Connection panel does nothing, or shows an error.

Fix: Another process is likely using the configured port. Change the port in the server settings (gear icon ⚙ in Connection panel) and try again. Common culprits: another Blender instance, a previous session that didn't close cleanly, or a firewall rule blocking the port.

Symptom: The server is running but no documents appear after sending from Revit.

Fix: Check that the host and port in Blendersync for Revit match the host and port in the Connection panel. If you changed the port, make sure both sides reflect the same value. Verify the server status shows Running.

Document is stuck as Pending

Symptom: A document appears in the Links panel with a Pending state and scene content is not updating.

Fix: The document needs to be authorized. Select it in the Links panel and click Authorize. Updates will not apply until authorization is granted.

Sync updates are not applying

Symptom: The document is present but scene content is not updating when changes are sent from Revit.

Fix: Check the document's authorization state. If it is Paused, updates are queued but not applied — click Authorize to resume. If it is Denied, updates are blocked entirely.

Override is not showing the expected result

Symptom: A material or viewport appearance override seems to have no effect.

Fix: The most common cause is the Global Override taking precedence over per-material settings. Open the Links panel and check whether Global Override is active for the document — if it is, it affects all materials that haven't opted out. To protect a specific material from it, enable Ignore Global Override in that material's override settings. If a per-material override isn't showing at all, confirm that Global Override isn't masking it.

Preset import shows a name conflict

Symptom: A dialog appears during preset load asking about asset conflicts.

Fix: This is expected behavior, not an error. Choose Reuse existing if the correct assets are already in the scene. Choose Import as copy if you want the preset's assets preserved separately. See Presets → Conflict handling.

Sun toggle does nothing

Symptom: Clicking Toggle Sun in the Links panel shows a warning and does nothing.

Fix: Check two things:

  1. Is Blender's built-in Sun Position add-on enabled? (Edit > Preferences > Add-ons > Sun Position). It must be enabled.
  2. Has a sun been synced for this document yet? If no sun data has arrived from Revit, the toggle will also warn.

Scatter or material override has no visible effect and no error

Symptom: Scatter fields are visible but nothing appears on the geometry, or a material override is configured but doesn't seem to apply — with no error message shown.

Fix: The bundled BSync node groups may not have loaded correctly. Try disabling and re-enabling the add-on in Edit > Preferences > Add-ons, then reopen the file. If the problem persists, use Debug > Tools > Clear Data to remove all BSync data and start fresh — but note that Clear Data is irreversible.

After add-on reload, the server state is unexpected

Symptom: After a script reload or Blender restart, the server does not restart automatically.

Fix: If Auto Start is enabled, the server will start (or re-adopt an existing listener) on file load. If you manually disabled Auto Start, you will need to start the server manually from the Connection panel.