Revit 2022 support was only added on Enscape 3.0. We use 2.9 up to R2021 as we are not using later versions of Revit for now.
Users having to use/testing 3.0+ are facing the issues described above.
I will double check deployed versions and will test Enscape 2.9 on R2022 and report back.
Enscape 3.0+ are happening regardless of R versions.
Thanks for the replies.
Hi all,
Any solutions on this?
Can you please check these other forum pages:
RE: Enscape 3.0 and Revit Worksharing
Revit sync with central requests constant with Enscape open
We are thinking of upgrading from a stable 2.9 to 3.4. Should we not do this then based on your feedback? Are the new feature worth the trouble?
Cheers,
Goncalo
Hi cholden424,
Can you please let me know what Revit Version you are currently? We are thinking of upgrading from 2.9 (stable) to 3.4. We have some admins using it and it has been unreliable and testing some of the reported bugs are making us unsure of the upgrade.
We haven't starting testing our BIM360 projects yet.
Please see here and let me know your thoughts about the upgrade:
RE: Enscape 3.0 and Revit Worksharing
(created by you)
Revit sync with central requests constant with Enscape open
Cheers,
Goncalo
Hi Jeppo03,
Please see the forum pages below and see if you can relate to those.
We are currently thinking of deploying 3.4, but are having doubts if we should.
Revit sync with central requests constant with Enscape open
RE: Enscape 3.0 and Revit Worksharing
Let me know if these help or are a different issue.
Best regards,
Goncalo
Hi all,
We have reported this earlier this year as well as an issue for Enscape 3.4. We are currently holding on to earlier version 2.9 until we find fixes or workarounds, but we are looking to deploy 3.4 by end of the year.
See earlier thread here:
RE: Enscape 3.0 and Revit Worksharing
Pieter, based on your experience, if you were on our shoes, would you upgrade?
Cheers,
Goncalo
Hi all,
Waiting on Boops reply on this. We are looking to deploy 3.4 across the office by the end of the year and this might be an issue for us as some projects and/or users are using a similar kind of setup.
Status update please!
Cheers,
Goncalo
Hi Pieter,
By reading on what are Data Storage Elements, apparently that is the point. The developers can tap into this API to create bubbles instead of spreading the borrowing across multiple parts of Revit. At least this is my understanding of it.
Have a go at 3.4. The issues are still there, but on our testing but no more crashes for far. If you do test this, let me know of your findings.
Rick Marx
Please also see this thread on issue created on the other thread.
Same thing still on Enscape 3.4, Revit 2020 and Revit 2021.
Thanks
RE: Enscape 3.2 CRASHING MAIN Thread (Please post here)
Hi Rick,
Thanks for your reply.
We starting testing with 3.3 but moved testing to 3.4 because of added improvements.
We are having issues with multiple users using the same Revit file and Enscape at the same time. On changing the view settings from Ortographic to Perspective or 2 Point Perspective, Revit is reserving a Project Standard called Data Storage Elements. In the version currently deployed to the office (3.0) this clash is causing constant crashes to Enscape and Revit thus speeding up testing of new versions.
We have found that with the use of 3.4 there is still the issue of Revit warning of ownership clash of Data Storage Elements, but the files are not crashing and if the user clicks on Cancel instead of Request, Enscape will still change the view settings and allow the user to carry on.
My questions are: Why is Enscape using Data Storage Elements? What changed from 2.x to 3.0 versions regarding the previous question that could be forcing both applications to crash?
Thanks
Gonçalo Pereira
Hi all,
Still having the same issue on Enscape version 3.3.1 and Enscape 3.4.0. Editing the view from Perspective to Two Point or Orthographic.
Also, this is only an issue if there are two users trying to change these settings at the same time. It hasn't caused crashes on our end yet.
Hi all,
Still having the same issue on Enscape version 3.3.1. Editing the view from Perspective to Two Point or Orthographic.
Also, this is only an issue if there are two users trying to change these settings at the same time. It hasn't caused crashes on our end yet.
