Elumtools Detached vs non-Detached model.

[mlibby724014]

We have been using the Elumtools lighting plugin for Revit, for the past several months. Due to concerns of model corruption, in earlier versions of Elumtools, we have been running the plugin only in detached models.

Of course this has the disadvantage of having to update the fixture layouts, etc, manually in the main Revit model.

• I am wondering, with the newer versions of Elumtools 2015+, is model corruption caused by still an issue that we should be [really] concerned with?
• Are there users out there who have experience (good luck, bad luck, lessons learned) with not detaching the model to run Elumtools?

I just want to start weighing the risk vs reward of running Elumtools without detaching.

Thank You
Mike

[BenSammis]

This issue has only ever cropped up for us when a new version of Revit is released, but before any service packs are distributed. It's basically an error in the Revit API (that I think they finally fixed in 2015), which refuses to allow ElumTools to write to the Project Info. If you do run into this problem, open a non-corrupted model in the same Revit session as your corrupt model and transfer project standards>project info to fix it. The error we get is always in reference to item #76675, which is the Project Info in your model.