2023.1 Not reliable with Revit. The process of working with Revit + Twinmotion has usually been; 1) Open Revit 2) Sync 3) Close Revit 4) Open Revit 5) Make Changes 6) Sync 7) Close Revit Rinse...

Development Pipeline & Plugins
,
1

2023.1 Not reliable with Revit.

The process of working with Revit + Twinmotion has usually been;

  1. Open Revit
  2. Sync
  3. Close Revit
  4. Open Revit
  5. Make Changes
  6. Sync
  7. Close Revit

Rinse and repeat. :frowning:

Every second "sync", this message comes up

Screenshot 2023-02-02 094029

2

To add, Revit is in viewer mode, perhaps it can't write out to where it's needed?

3

Unfortunately the new version crashes 100% of the time for us. It's better to revert back and face the error messages rather than the crash.

I send in a crash report everytime, so hopefully it helps

4

I think I had this similar issue once before. What happened is something in the view was causing a conflict. I turned off each workset in my model off one-by-one until I found the one that was causing the issue. I exported and it worked. Turned on the "bad"workset again and it worked the rest of the time.

5

It was a family on our "Interiors" workset which is mostly comprised of interior building elements like furniture, casework, walls, stairs, and railings. I couldn't locate a specific ID element causing the issue. I ran a check for anything corrupt within the model but everything was fine. Often times, some of our interior families are a little more complex in their geometry and are sometimes imported from CAD files or a product manufacture's website with more parameters built in. My guess would be it was one of the more complex families.

6

Hello ,

Thank you for posting in the community and there does seem like an issue potentially with the 3D view open or initially used to synchronize having issue. Make sure you are using the Datasmith Exporter plugin for Revit 5.0.3v2 in order to work with Twinmotion 2023.1.

Please contact us and report a bug so we can best investigate if the problem is still on-going by following this link:

https://twinmotionhelp.epicgames.com/s/case-community-page

Kind regards,

Vincent B.

7

Hello ,

Thank you for sending the crash reports as those are very helpful and recommend you also report a bug via the contact us button from the home page or this link: https://twinmotionhelp.epicgames.com/s/case-community-page

This will make sure we can fully investigate the problem at hand as it could be related to the workflow and viewer mode you are on.

Kind regards,

Vincent B.

8

Hello ,

Thank you for the follow-up and glad to hear you were able to find the issue with a specific workset. If you have any feedback on what the "bad" workset was that would help so we can look further into this.

Kind regards,

Vincent B.

9

Hello ,

Thank you for the follow-up and added details. We are looking further into this issue but if you have some typical websites you get those families as an example to share it would be helpful so I can look at those parts.

Best regards,

Vincent B.