Synchronize with CENTRAL file causes views in Active document to go missing.

nickw · Feb 26th 2018

Good Morning

When we had the enscape view window up, then close the enscape window and then we sync with the CENTRAL Model. The pull down for the 3d view selections, some of the views say (Deleted) any one have this issue (See image 1)? then when i open the pulldown again for the 3d views, all views are gone expect for one (See image2).

Thoughts? We are also on the newest version as of 2018-02-26

Thanks

Pieter · Feb 26th 2018

we've seen the same issue. We thought it might be because there were members of the team that were still on the old version.

nickw · Feb 28th 2018

hmmm, not sure about that. i am the one who is doing the updates/service paks on all workstations and they should be all on the same version. I think this happens in 2016 and 2018.2 of revit. ill keep a eye out on other projects and workstations that this might be causing this issue.

Pieter · Feb 28th 2018

Yeah we never really confirmed that was really the cause.

We had everyone on the same revit version, but the team was using different enscape versions sometime.

nickw · Mar 2nd 2018

oh ok, hmm let me look into that. thanks

mattendler · Mar 5th 2018

I've had this issue before when syncing and also when CTRL-TABBING to another project open in the same instance of Revit. It should be flagged for the developer's to fix.

geistwolke · Mar 6th 2018

can confirm that many of us at my company are experiencing the exact same issue since the update. I have asked the team to close the Enscape app before the next syncs to see if re-opening without reloading the model will preserve the view list. This is what we had to do last year on our 2016 version of Revit sometime around last spring. It was very time consuming when half a dozen persons are rendering for a deadline. But a bit less than completely closing the project.

Demian Gutberlet · Mar 12th 2018

Thank you for the reports! We're actually aware of this issue and we'll implement a fix as soon as possible.

robinchs · Jul 2nd 2018

Quote from Demian Gutberlet

Thank you for the reports! We're actually aware of this issue and we'll implement a fix as soon as possible.

Anyone know if this issue has been resolved in 2.3.0? I'm currently on 2.1.3 and this happens all the time....

EDIT:

Had IT update my Enscape to the latest and it's fixed now.