Envision Live Link | Revit item with Same Key?

Hello Everyone,

We’ve been running into the issue of receiving the following errors (see images) when we try to utilize Envision Live Link with Revit 2025

We’re trying to understand:

  1. What this error means
  2. How we can fix it (if it’s an issue with a rogue object or material, we just need to know how we can track down and fix/remove what is causing the issue)

These errors occur with Autodesk Revit Cloud projects, and we’ve seen this issue with multiple projects.

We’re utilizing Envision 1.6

Hi, this is a known bug and it is usually related to light objects. Unfortunately it is very hard (or impossible) to find out which specific objects are causing this without developer superpowers.

You can contact us here and attach your original Revit project: https://support.chaos.com/hc/en-us/requests/new

We will then do our best to find the problematic objects for you ASAP.

Alternatively, you can wait a bit as this bug is already fixed internally and the fix will be a part of the upcoming version of Envision. If all goes according to the plan, it will be released very soon.

Thanks Maru, we look forward to the update :+1:

Thank you for your understanding. We are working to have this issue resolved and shipped as soon as possible. Internal (EC-3416).

I have some updates to share:

  • The root cause of this error message is a bug in Enscape, which leads to incorrect exports of Revit families that include multiple light sources.

  • This bug has been fixed internally, and a new version of Enscape containing this fix will be released soon. If everything goes according to plan, the release should occur within the next two weeks. Once it’s available, the solution will be to simply install the latest version of Enscape.

  • In the meantime, a workaround is to avoid using families with multiple light sources (nested lights). Possible options include:

    • Removing those objects completely,
    • Replacing them with families that contain only a single light source, or
    • Editing the families in question to manually reduce the number of lights to one.

We understand that the workarounds provided may not be ideal and could be unfeasible in some cases. However, these are currently the only options available. We hope that waiting for the upcoming Enscape release is a suitable solution for you. Rest assured that once it is available, you will be able to work without interruptions caused by this bug.