Posts by mark8848

    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.


    Specs:

    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

    Update:

    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.


    Thanks!

    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.


    Thanks!

    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.

    Just curious, how far is "too far" away from the origin? 10m? 50m? 100m?

    Our office standard units is millimetres, is there a significant change between mm and cm? As opposed to mm and metres?

    This is good to know when setting up future projects, thanks!

    Hi Enscape team,


    I seem to have an issue with self-illuminated materials. I have applied them to large surfaces on the floor and ceiling of a gym for even lighting in addition to light fixtures. When I move around, the surfaces flicker. This is not a z-fighting issue as I have checked for any interference and there is none, the surfaces are far from other surfaces in the z-direction. The problem gets even worse when seeing the ceiling surface from the outside through glass into the room. Once I turn off self-illumination in the enscape materials, this behavior stops. The ceiling surface is quite large but the floor is broken up into several pieces and it happens on both. Are there limitations on self-illuminated surfaces that would cause this? Have you run into this before? I'm using Enscape 2.7.1.20866 and Rhino 6.


    Thanks,
    Mark

    Hi Enscape Team,


    I'm noticing some issues with reflections in Rhino 6, I'm using version 2.7.1+20886.

    I have a fairly large and complex model full of Escape asset trees. When I view a glass wall and move around, the reflections of nearby trees and objects disappear and reappear seemingly at random. Moving closer to the wall seems to get rid of many reflections of nearby trees. When moving around, reflections pop in and out. This is also not solved in videos, the same behavior is also visible. I have a powerful workstation so it's not a hardware limitation (RTX5000, 8core 4GHz processor). Is my model too big? Are the model extents too far? Is the model too far away from 0,0,0? I tried reducing the model with clipping planes but this did not help. Any suggestions are welcome as well as any previous builds that I can try with more stable reflections.

    Thanks!