Posts by mark8848

Reminder: If you encounter any issues with Enscape (including installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Feedback button as detailed here. Thank you for your understanding.

    Same issue here!

    Went through multiple support channels with Chaos, our software provider, IT support, no one could figure out why our Chaos login would be reset without any warnings or password reset emails. We have a password manager and can see all the previous passwords and when they were changed. This was quite the frustrating problem.

    Luckily, it occurred to someone that Chaos now owns Enscape so the Enscape password was entered and it worked! The two seperate accounts for Enscape and Chaos shared the same account email address and were merged at some point.

    I'm not sure why we were not made aware of this by neither Enscape nor Chaos. This is a major change and caused frustration for months!

    Enscape 3.5.2 has been released and the problem is still there. 3.5.2+112393 is unusable with rhino

    Rhino viewport runs at around 2fps while Enscape is running. When Enscape is closed, the same view is fast >60fps. (i9-12900k, RTXA4000, both under 15% utilization while panning)

    Hi Demian,

    I'm having the same issue. The screenshots don't match the live view in Rhino. Even though it may seem minor, it is a big deal not being able to rely on the live view for accurate representation of the materials. I won't be able to present the live view and send screenshots that match. Please take a look at this.

    I've attached a screenshot of the issue. Live view left / Export right

    I'm on Enscape 3.4.1 +85781. I have also tried turning DLSS and the Denoiser off with no difference.

    Thank you in advance!

    Also, having this issue in Rhino 7. At first I thought it was a worksession problem (which has been an issue in the past), but the same thing happens in a singular model. It is not consistently white materials though, some do show, either correct colour, transparency, or bump mapping, but most of the material shows as white. I don't have time to troubleshoot or submit a comprehensive error report right now so reverting back to an older version for my deadline.


    Enscape version: 3.3.0+74199

    Rhino 7 SR16 2022-3-8 (Rhino 7, 7.16.22067.13001)

    Windows 10.0.19043 SR0.0 or greater

    (Physical RAM: 80Gb)

    Primary display and OpenGL: NVIDIA Quadro RTX 5000 (NVidia) Memory: 15GB, Driver date: 5-6-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 462.59


    Installing the latest 3.2 preview version corrects the issue. The red glow is now gone and in dark lighting, the videos illuminate the scene with the colour that is being shown in the video. Not sure what happened but whatever is different about version 3.2 seems to have worked.

    Hi team,

    I'm getting this weird glitch that hopefully you have an answer for. When using a video material, I get a red glow coming from the surface. I've tried many different videos with different colour tones and all of them glow red. The glow does fade when you stop moving but then so does the video (restmode).

    I've created a brand new project, with brand new materials, to demonstrate this and make sure it wasn't something in the project. Please see the video and screenshots.

    Any ideas how to fix this? I can't have red shadows/glow showing for renders, videos, or walkthroughs.

    With a video material: (red glow)

    Default Material: (No red tint in the shadow)

    ....also, it is just me or do the video ease in and out as a default? I don't see any options to turn this off. I will now have to create even longer video exports to trim this away creating more work. Please restore the option to turn this off if possible. Thanks!

    edit: Sorry, I feel like a idiot. I had my enscape window in a small window. I saw the option when I maximized the window. Not sure if this is a bug or not, that you can't see all the options unless the window is maximized?

    I'm also having issues with the video editor. I often create videos only using 2-4 keyframes. In the old editor, I was able to change the overall length of the video (and the speed of movement) by adjusting the timestamp of the last keyframe. This now seems to be broken.

    The old way was essential to my workflow. I need to be able to control the overall length of the video only using two keyframes. Please take a look at this and resolve. Thanks!

    Edit: Sorry, just needed to maximize the window to see the additional options.

    Hi Team,

    I updated to Enscape 2.8 last week and it seemed like the updated overwrote my enscape saved settings that were saved to the project I am working on. Luckily I had exported most of them to file so I could reload most of them but I did lose some. Is this a bug or something that will happen when updating? Could you post a warning message to back up settings before updating. I will save all of my important settings to file from now on but ideally it wouldn't be overwritten.


    I'm also experiencing this problem in Rhino 6 (not the right software category I know) but thought I would also chime in. This would be great to have fixed soon as we cannot use this feature because views cannot be reliably reproduced.


    Great job team! Looks great so far and I'm excited to use this moving forward. If I may offer some constructive criticism, it seems that the intensity slider impacts the distance and possibly speed that leaves move at. At lower speeds, this means the leaves are moving short distances but it seems they are still moving quite quickly. This makes it seem like they are almost vibrating back and forth. I'm sure this will be tweaked in the future, my preference would be very slow moving leaves but slightly longer distances at low intensity. It would also be nice to have some jitter to emulate a gust of wind so its not a constant intensity but some variation is given. Something to think about for the future but I'm loving it so far. Thanks for continuing to add these features and listening to the community. Not many developers out there that we can ask for features like this directly to the team and see it implemented!

    Even 100m should still be fine - usually problems occur when the project is really, really far away from the origin.

    Also, what do you mean with "significant change"? Are you referring to Rhino itself or in regards to Enscape? :) But yes, definitely a good idea to set it up to CM initially to avoid any issues.

    Thanks, this is good to know. For the units, I mean for enscape. We can adapt to any units as long as it works better for enscape. We often will build separate models for enscape so we will make sure to start these in cm from now on.