Learn about known issues for Twinmotion and Revit interoperability, with work-arounds.
Symptom: After using the Open in Twinmotion command, and specifying to create a new Twinomotion project file, the Direct Link connection is not automatically established with the active Revit model.
Issue: This issue can occur for Revit models with a file name that contains certain special characters, a period symbol before .RVT, or specific language strings which cannot be translated by Direct Link.
Work-around: Do a save-as of the Revit model to create a copy, and specify a simplified file name that does not include these types of characters. Afterward, Open in Twinmotion should function as expected.
Symptom: After using the Open in Twinmotion command, Revit reports that a compatible version of Twinmotion is not installed.
Issue: If Twinmotion or Twinmotion for Revit was installed by another user, or included in a machine image created by another user, and never opened by the current user, a required registry value may not yet exist.
Work-around: Have the current user manually open Twinmotion or Twinmotion for Revit once, which will write the necessary values to the registry. Afterward, Open in Twinmotion should function as expected.
Symptom: After using the Open in Twinmotion command, or manually creating a new Direct Link connection, it fails with the active Revit model.
Issue: For new Revit models created from a template and not yet saved, a new Revit model created and saved for the first time in the same session and not yet closed, or a Revit model saved with a new file name that has not yet been closed and re-opened, Direct Link will not detect the Revit model.
Work-around: Save and close the Revit model. Then re-open the same Revit model and attempt Open in Twinmotion again, or manually add a new Direct Link connection from Twinmotion to the active Revit model.