3.0 Update: Revit stops responding to most commands after a short time

JohnB · Mar 5th 2021

Hello forum,

I updated to Enscape 3.0 and I have to say it looks great. Unfortunately I had several run-ins with it. It seemed as though Revit would - after say 10-15 minutes - stop responding to most commands. I could save the project but that was about it? Couldn't execute and commands, draw anything, switch/open/close views. Basically my only option was to save and force quit. I repeated this several times, same results. It hadn't 'frozen' completely, could still click buttons and everything, it was just unresponsive... more or less the same thing right?

I've reverted to V2.9.1 and might wait until the next update before I try again. Things are running otherwise normal now I've reverted.

Has anyone else experienced this?

Cheers,

John

Demian Gutberlet · Mar 5th 2021

JohnB , thanks a lot for your report - this is the first time we hear about such behavior with 3.0, so it would be great to receive both log files and machine information from your PC via a dedicated feedback report:

https://enscape3d.com/communit…sing-the-feedback-button/

In the submission form, please include a link to this thread for reference so that it can be assigned to me, or that our support team generally knows what the problem is!

Bartosz 3Y · Mar 5th 2021

Hi,

Same problem.

Demian Gutberlet · Mar 5th 2021

Quote from Bartosz 3Y

Hi,

Same problem.

Thanks for the report. Can you please also send in a feedback report? Thank you!

JohnB · Mar 7th 2021

Thanks Demian Gutberlet

Have submitted log files and message describing the issue via the feedback button.

John

Demian Gutberlet · Mar 8th 2021

Quote from JohnB

Thanks Demian Gutberlet

Have submitted log files and message describing the issue via the feedback button.

John

Thanks a lot - that's very helpful!

eyadabusoud · Mar 19th 2021

same problem

Revit 2021.1

JohnB · Mar 19th 2021

Hi there,

I did a clean re-install of 3.0 (including deleting all local user Enscape files), but the problem persists. Can't determine what the pattern is nor can I 'force' it to happen. Will send another feedback report with log files.

Back to 2.9 I go!

Cheers,

John

Tags