3.5 is extremely unstable and very difficult to use

REMINDER! If you encounter any issues with Enscape (e.g. crashes, installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Support button as detailed HERE! Thank you for your understanding.
    • Official Post

    At this point, im not even sure why im surprised. The integrated GPU is disabled.


    I can only understand the frustration caused by all of this at this point of course, but it would still be great if you could actually send in that report via the second prompt dialogue "Send Report" as the name says, since the main issue you're experiencing should be resolved with 3.5.2 now, and we'd of course like to look into this new behavior here at hand.


    If you could also let me know once the report with logs has been sent in that would be rather ideal as I can then also directly forward all the information to our developers for further investigation.

    • Official Post

    Thanks for the update. Unfortunately the issue is still here, just the same as people have being complained for 2 months in this thread. I'm sorry but it's unbelievable.

    That is of course not good to hear or see - As per my post it would be ideal if you could also send in a report with logs after you updated to 3.5.2 now and still experience this: https://learn.enscape3d.com/bl…eedback-button-win-rhino/


    In this case it would also be great if you could let me know once submitted.


    Thanks a lot. I've already forwarded everything accordingly.

  • That is of course not good to hear or see - As per my post it would be ideal if you could also send in a report with logs after you updated to 3.5.2 now and still experience this: https://learn.enscape3d.com/bl…eedback-button-win-rhino/


    In this case it would also be great if you could let me know once submitted.


    Thanks a lot. I've already forwarded everything accordingly.

    I just did. The request id is #136942.

  • Thanks for the update. Unfortunately the issue is still here, just the same as people have being complained for 2 months in this thread. I'm sorry but it's unbelievable.

    Any news On this? Still experiencing the same issue.

    Working with the lastest version (Enscape 3.5.2+)

    Found it especially difficult for when editing blocks or invert lock objects in rhino. This updating from version x to x issue consistently appear as long as the safe frame was opened. Make navigating within rhino impossible.....

    • Official Post

    Any news On this? Still experiencing the same issue.

    Working with the lastest version (Enscape 3.5.2+)

    Found it especially difficult for when editing blocks or invert lock objects in rhino. This updating from version x to x issue consistently appear as long as the safe frame was opened. Make navigating within rhino impossible.....

    We're currently still investigating with the help of other users projects and reports (including logs). Meanwhile as it cannot hurt, would you perhaps also be able to share your scene with us just so I can forward it to our developers? (Via a direct message if confidential and you could use wetransfer.com for uploading)



  • After it was a desaster to work with 3.5 and 3.5.1, I gave the 3.5.2 update a try today.

    It has been lasting for about 5 minutes and I deinstalled it another time to went back to 3.4.4. This seems the only Version, which is working properly.


    The reasons:

    - opening a massive project file, took way more long than with 3.4.4 (doublechecked it, now with 3.4.4 again, it takes less than 1 minute)

    -after waiting for that, hiding a layer with a lot of elements was not working (ok, perhaps it would have worked after hours....) Now with 3.4.4 it takes 1 second doing this....

    - still using rhino blocks is not funny with 3.5.2; program windows disappearing and crashing frequently.


    So this Version still works very slow, very unstable and is not really useful unfortunately.

    Would be great to get a REAL WORKING update soon.... Or will enscpae not being developed seriousely, since there is something called vantage?

    • Official Post

    We've very sorry that there are still ongoing issues using 3.5 and Rhino. While we were able to resolve some already with the help of customers and further projects, the following has already been identified internally and will be added as a fix with an upcoming update as soon as possible:

    -after waiting for that, hiding a layer with a lot of elements was not working (ok, perhaps it would have worked after hours....) Now with 3.4.4 it takes 1 second doing this....


    They have not fixed anything and to be honest, it doesnt seem that they care.

    Regarding the other specific issue you've shared, we've gotten back to you with further questions prior but via e-mail through the feedback report you've submitted. If you could check those out and get back to me (via the case) I'd appreciate it.

  • We're in the same boat here, it's pretty disheartening to go back and read all of the comments that have the hope of "wait for 3.5.2!" but I'm here after running into issues that I didn't really get roped into until 3.5.2 was a thing.


    I have models that either


    1) take forever to open in 3.5.1 but open fine in 3.4.4 - I can't actually tell you how long they take to open as I've been trying to open a test file and we're at over 30 minutes, so who knows... took 3 minutes to open in 3.4.4.


    2) get extremely slow and unworkable when you make changes in the model in Rhino (turning layers on and off, etc). This generally culminates in Rhino crashing.


    I've been working with our reseller, so these example should be getting into the Enscape developers/support pipeline that way, but I haven't seen software this flaky in decades. It would be appreciated if we can get an idea as to if these features are even fixable or if we should start looking into other products.


    As some others have mentioned, there are issues with 3.4.4 which upgrading to 3.5.x has been a fix for. For us this is mainly the AMD driver shadow issue, which took a very long time to get a released resolution for. The workaround for that was to install May 2022 vintage AMD driver which was also old enough that it could cause some other problems with other things.


    We definitely need to get to a point where we can at least have a 'known good' version of Enscape. Maybe there needs to be a fork of 3.4.x where bug fixes like the AMD driver issues are incorporated but whatever major changes that happened that broke Rhino integration are not included.

    • Official Post

    cmdonnell , welcome to our Forum.


    Right away, if you also still experience 1) with 3.5.3, is there any chance you could perhaps send us the project at hand with which this occurs? So far our developers would still like to receive additional projects for troubleshooting but most were not able to share any files due to confidential reasons. If possible, let me know and depending on the size you can use wetransfer.com or I'll provide you a confidential upload link instead.


    Also, in case you wish to use 3.4.4 for the time being, the AMD driver shadow issues should be resolvable even in that previous release if you install the corresponding drivers (version 23.3.1) as detailed here.


    Further, even though I wish I had more positive news in that regard, at the moment we advice not turning off/on layers in the first place as that is known to cause major slowdowns. We're already working on a fix for this, but it may take some time until this will be added due to technical reasons.


    I'd appreciate it and thanks a lot in advance.

  • Hi Demian Gutberlet ,

    we also experienced issues (delays, material editor hangs, switching layers) in Enscape for Rhino after updating from 3.4.4 to 3.5.2. We were updating because the "license invalid" issue should be fixed in 3.5.2. So it was recommended. In your post #55 the preview version of 3.5.3 is mentioned, can we use this version as workaround?

  • Been nearly 4 months since this debacle, no solution in sight. extremely disappointed by the response from the enscape team. If this was a product that appealed to more than just architecture, ie, unreal engine, vray etc, maybe this would be less disappointing. However, knowing our industry and the ridiculous deadlines we deal with, shipping an unstable product is simply unacceptable. furthermore, 4 months of delays in resolution is worse.

  • Experiencing same issue with


    2023.08.31 19:55:00.163 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:00.199 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:00.231 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:00.267 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:02.233 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.283 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.316 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.350 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.382 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.414 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.449 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.483 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.515 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.551 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.582 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.620 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.651 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.684 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.715 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.747 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.781 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.814 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.847 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.878 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.910 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.945 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:04.980 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.013 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.047 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.078 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.109 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.142 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.172 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.207 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.237 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.272 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.304 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.338 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.369 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.404 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.435 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.464 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.497 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.523 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.559 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.591 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.628 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.659 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.694 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.725 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.760 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.791 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.825 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.860 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.893 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.927 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.959 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:05.994 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.028 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.062 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.095 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.131 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.164 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.200 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.231 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.266 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.299 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.330 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.363 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.393 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.425 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.455 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.492 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.526 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.561 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.592 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.624 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.656 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.684 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.718 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.748 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.782 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.813 -03:00 [1] | INFO | Updating "ASDFASDFASDFA" from version 3 to 4.

    2023.08.31 19:55:06.845 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.866 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.899 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.921 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.

    2023.08.31 19:55:06.965 -03:00 [1] | INFO | Updating "Glass 02, Embossed" from version 3 to 4.


    Fix this.

  • This also happens to me. The updating from version 3 to 4 error.

    It completely freezez if you have a project in Rhino where you use blocks. If you go into a block and edit a little thing. Enscape goes crazy and want to update the whole project somehow.. It doesnt make sense to provide the team with a project example. It happens as soon as you start working with a lot of blocks. No matter what project you work on.. You have to close down enscape everytime you want to work with a block in a bigger project. SOLUTION PLS!