Preview version: 2.6

  • 3dhouse , which resolution did you use? Can you share a screenshot?

    Thomas Willberger


    I rendered 2K and 4k images with 1% outlines. Both showed thick outlines at 1%, and definitely not what is seen in the realtime preview.


    Was this addressed in the latest preview? Do you have a internal screenshots that show a different experience in testing?


    I rolled back so i cannot easily create more and did not label my output when testing... perhaps 3dhouse can help.


    Thank you

  • I can not find the settings anymore (Enscape-Setup-2.6.0-preview.1+7184)

    who can help


    I suppose so it was some work to create the graphic for the question. I hope the question will not be overseen. Or did I have overseen the answer?


    Also I think it's not so useful to split the settings over two independent UI. Looks like a problem is created where no problem was. At Rhino you will have four or five Enscape windows to handle: Options1, Options2, Rhino material editor, Enscape material editor and the output window. And so it will be no fun for beginners to deal with all the windows to get the work done.

  • Also I think it's not so useful to split the settings over two independent UI. Looks like a problem is created where no problem was.

    Regarding settings, I understood the most common user requests were:

    (may have missed some, these are just the ones I saw requested several times)


    1. allow settings to be saved within each "scene" or "view" of the host package

    2. remain with the file.... so that when collaborating others get the settings used ...or when going back to a project, the settings are still accessible.

    3. when reopening a model, automatically use the settings saved with the model scene selected ...as opposed to the last settings used on that machine.

    4. scene settings to be used when batch rendering


    Does anyone know if 2.6 is attempting to achieve any of these?

  • "Individual settings per project and view" is on the roadmap. I do hope these settings are going to be saved IN the project file and not in a separate xml file or something.

  • Thanks for reporting the broken loading screen customization


    Regarding DOF: We changed some logic to restore to defaults at some points. It was intentional, but we might reconsider at some time.


    Atmosphere tab: We are evaluating multiple options right now. We weren't happy with the popping in/out depending on some checkboxes because this made it more difficult to follow - even had some bugreports about some options not working together when in fact they were only jumping around


    Text input (and a visual redesign) is on the agenda, but first we want to tackle the more risky parts. I hope that we get it done for 2.6, but we have so much more planned right now.

    I can not find the settings anymore

    who can help

    We heard that it's difficult to share settings and that the number of settings explodes quickly if working in multiple projects, so we wanted to switch from the file-based solution to a more integrated solution: Store settings inside the CAD project file, ideally even linked to a view. [We're working on it right now]


    The user interface that is currently available is kind of a preliminary UI because we needed some place to put it, but probably it won't stay this way. And hopefully you won't need the functionality to open/save a settings file that often.


    Another comment regarding your picture: Once you understood how the load/save worked in the old UI you could operate it pretty quick. But we heard from many users that it's difficult to understand in the first place.

    • I feel that Automatic Resolution is not really an image setting but more a 'general settings' thing (it's a performance setting)
    • I think it would be easier if you gather all settings that affect 'lighting/brightness' in one place. These settings are spread out right now over 3 tabs, making it harder for non advanced users. Perhaps rename atmosphere to 'lighting and sky' ? At the top you could have Exposure + Ambient brightness, followed by the Skybox settings, followed by the illumination settings. I would put horizon, clouds and fog underneath that.
    • For some settings, it would help if we could type in an exact value
    • the 'auto hide' of certain sliders doesn't seem to work yet? (for example: the contrast sliders when you turn auto contrast on, or the rotation of the skybox when you don't have a custom sky)
    • You could make some of these dialogs more compact by adding more 'auto hide'. For example with clouds you could just have a checkbox 'customize clouds', which would show all these extra sliders. We generally don't change any of these settings and leave it at default. Same with Fog. Also, if white background is on, you can hide all the settings for clouds.

    Automatic Resolution: We'll reconsider. What you can see right now is our first draft, but I must admit we had some internal discussion about the proper separation.

    Lighting/Brightness: Thanks for your input

    Type exact value: As already explained, it's on the agenda.

    Auto hide: As already explained, we removed the auto hide because of controls jumping around. We'll definitely try to find a solution so that you don't have to scroll in the atmosphere tab.

    Also I think it's not so useful to split the settings over two independent UI. Looks like a problem is created where no problem was. At Rhino you will have four or five Enscape windows to handle: Options1, Options2, Rhino material editor, Enscape material editor and the output window. And so it will be no fun for beginners to deal with all the windows to get the work done.

    The separation of general settings and visual settings is intended to make things easier and to provide a specialized UI for separate use cases.

    Use case 1: Configure the Enscape plugin → general settings

    Use case 2: Adjust the visual output → visual settings

    The idea is that you won't need the general settings to tweak your picture. If you do, you better tell us which general settings you need to adjust and we'll try to move them to the visual settings.

    The load/save UI in the general settings is preliminary as explained before.

  • 1. We're implementing the step before that right now (save in the project) - save in the view/scene is currently being designed, we try to squeeze it into 2.6 but no promise here.

    2. Probably achieved by 1) without any further change - alternatively you can save your settings on a net share now, in a directory structure that is to your liking

    3. We don't have this on the agenda explicitly, how is it different than saving settings in the view/scene?

    4. On our radar because it's the natural extrapolation of 1). But this alone isn't always enough, there's more: scenes might have different geometry and supporting this would be a huge effort for us. Still some uncertainty here.

  • 4. On our radar because it's the natural extrapolation of 1). But this alone isn't always enough, there's more: scenes might have different geometry and supporting this would be a huge effort for us. Still some uncertainty here.

    Thanks for the reply...


    #3 probably will be handled by #1... I was just listing the various issues people seem to have identified separately.


    To clarify, #4 has two parts... the most immediate should be handled by #1 IF these settings are persistent while batch rendering Note: varying geometry / layers is a separate function... #4 does not need to wait for geometry / layer states to be useful. The main point here is that I almost ALWAYS adjust exposure, HDR settings, etc for each viewpoint / path / etc. Currently there is no efficient way to batch render multiple scenes if these types of adjustments are made between scenes. If you accomplish #1 AND make that persistent during batch, that should accomplish 1-4 of the list above (IMO)

  • Atmosphere tab: We are evaluating multiple options right now. We weren't happy with the popping in/out depending on some checkboxes because this made it more difficult to follow - even had some bugreports about some options not working together when in fact they were only jumping around

    I hope you will find an elegant solution for this. I personally liked that features where hidden when not applicable (why show the skybox rotation if no skybox is applied).


    I fear that I will have to deal more with users being confused now ("I am adjusting the sky brightness slider and nothing happens!!! (-> because there is no custom skybox applied).


    It also makes the dialogs look more intimidating because you have all these sliders, of which 30% don't really apply.

  • The user interface that is currently available is kind of a preliminary UI because we needed some place to put it, but probably it won't stay this way. And hopefully you won't need the functionality to open/save a settings file that often.

    The question is - how can previous project setups loaded again? Are they lost?

  • Thomas Willberger


    I rendered 2K and 4k images with 1% outlines. Both showed thick outlines at 1%, and definitely not what is seen in the realtime preview.


    Was this addressed in the latest preview? Do you have a internal screenshots that show a different experience in testing?

    I think I understand your problem. One major complaint was that some outlines were missing and that the outlines do not scale proportionally to the screen resolution (Same outline amount with 4K downsized to 720p should result in similar image as if done in 720p). Independant from what you mean, I see that even with 1% they are not super thin on 4Ks. We will fix that.

  • Hello,
    I tried the new preview version to see how you improved reflections but there's something wrong.
    I downloaded latest drivers. I run the test on a gtx 1080ti 11gb
    The better image is made with the latest stable version, the one with the messed up textures is made with the preview version.

  • I think I understand your problem. One major complaint was that some outlines were missing and that the outlines do not scale proportionally to the screen resolution (Same outline amount with 4K downsized to 720p should result in similar image as if done in 720p). Independant from what you mean, I see that even with 1% they are not super thin on 4Ks. We will fix that.

    Thanks for your consideration... I believe 1% should be almost imperceptible at any resolution.

  • Hello,
    I tried the new preview version to see how you improved reflections but there's something wrong.
    I downloaded latest drivers. I run the test on a gtx 1080ti 11gb
    The better image is made with the latest stable version, the one with the messed up textures is made with the preview version.[attach='8164','none','true'][/at

    what is exact number of that drivers ?

  • Renderwiz: "4. scene settings to be used when batch rendering"

    4. On our radar because it's the natural extrapolation of 1). But this alone isn't always enough, there's more: scenes might have different geometry and supporting this would be a huge effort for us. Still some uncertainty here.

    Initially, if camera and lighting settings were saved per scene, then batch rendering should atutomagically change to reflect these.

    On the issue of changing geometry - if you can send a command to the native application to change the scene, then does this not take most of the 'heavy lifting' out of the geometry changes required to display in Enscape? (This would obviously require Enscape to 'lock out' the instance of the native application while batching - may be a problem for users, but I doubt it.)


    Personally I think that rendering is so quick that only huge images, panoramas and high quality animations should be queued for batch rendering.