Posts by Simon Weinberger

    I trust that archicad will have this functionally in the next release

    The embedded settings work with ArchiCAD right now, and we are developing the reproducible renderings for all CADs at the moment. There might be limitations in how we are able to sync to the native ArchiCAD experience of views, but that's not clear at this point in time.

    It's too early to give you more precise information, but we encountered other limitations for ArchiCAD earlier. For example we only managed to extract geometry from a view if that view is currently visible in ArchiCAD itself. That's why you need to have an open perspective view at the moment to start Enscape. There are still a lot of unknows, we are in early development of this feature.

    If the feature is included in the next release, then it will also be available for ArchiCAD.

    Hi Pieter,

    thanks for your feedback. It's great to hear that we are moving in the right direction, and we are just too slow. We are already working on the ability to allow reproducible renderings, I hope that it will be included in the next release. The logical first step was to embed the settings in the CAD project.

    With that feature you will have a way to manage a list of views, consisting of camera, sun and settings - all embedded in the CAD project. Of course we are also thinking about updating these and syncing/using what the CAD offers natively.

    Micha Light distribution of area lights is different from that of point lights. I don't have any deep insights into why the limitation exists but I'm pretty sure it is a combination of performance and correctness considerations.

    RTX by itself does not allow anything that wasn't possible before, it is just a performance improvement that allows us to do more/better calculations without affecting user experience.

    Will the Archicad Material editor be available soon?

    We started a few days ago with the very first steps. Unfortunately it's still too early to promise anything. It's still not clear whether we will encounter any blocking issues along the way or how long it will take.

    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.

    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.

    See, what's coming in the next version of Enscape!



    The settings are getting a rework. This means for now:

    • Separation into "general" and "visual" settings
    • Most of the "about" dialog has moved to the general settings (e.g. network proxy, license)
    • Load and save visual settings from/to arbitrary files
    • Many smaller improvements

    This is just the beginning. We have much more planned. Stay tuned!

    Texture rotation

    The material editor for SketchUp and Rhino now support texture rotation. If you use this feature in SketchUp you will see differences in the appearance, since it isn't supported natively.

    RTX support

    Starting with this preview version Enscape now makes use of the dedicated RTX technology of Nvidia to accelerate ray tracing computations for indirect lighting and reflections. This allows users with RTX compatible hardware from now on to profit from more detailed geometry in reflections and more accurate indirect lighting calculations without sacrificing performance.

    Please be aware that the RTX implementation is still in the prototype stage and does not represent the full functionality of the next official 2.6 release! Quality and performance are both still a work in progress. There are even a number of temporary limitations compared to the non-RTX ray tracing implementation you should consider before install the preview version:

    • Water does not yet reflect off-screen geometry
    • Artificial light is not visible yet in reflections and has no effect on indirect lighting


    Store settings in CAD project

    You can now store your visual presets in the CAD file itself and load it later. With "Manage presets" you can delete or rename these.

    Please be aware that in some CADs these interactions are included in the the undo/redo stack - in others they aren't.

    These visual presets don't touch your general settings at all. This means you can share visual settings with your team while still having your own preference, e.g. an inverted mouse movement.

    If you have used the last preview to save presets in files, I'm sorry to inform you that these files can no longer be read. The legacy import is still located in the general settings.

    Settings tweaks

    The settings have undergone a few tweaks, I'll list the most important ones here, but there are more little improvements to be found.

    Click the "..." button to reset to default value or open a box for textual input. Double-clicking the thumb still resets to defaults. When the slider has keyboard focus you can also just start typing a value and the textbox pops up.

    The interactive help is now visible in the status bar (with a few exceptions).

    The capture settings have been moved to the visual settings for now. "Auto Resolution" and "Grass Rendering" have been moved to the general settings under a new category "Performance".

    No more scrolling in the "Atmosphere" tab. Skybox is just another option for the horizon.

    Having two setting windows both being sticky at the top led to some usability problems, so both are no longer at the top until we have a better solution.

    Improved sunglare

    The sunglare should look even better now. Especially when the sun is partially occluded the glare's center is no longer occluded.

    Settings in Web Standalone

    Some basic settings are shown in web standalones (those already available in the exe standalone, reduced to fit the web capabilities). This feature is enabled for every web standalone uploaded with 2.6.0-preview.1 or later and applies also to existing ones.

    As always: We're looking forward to your feedback!

    Hi Nuge,

    I appreciate your feedback and understand your disappointment. Let me give you some insights into our development process.

    Version 2.4 was released in October 2018, just like it was planned. Now we are releasing 2.5, containing lots of smaller improvements for all CADs, as well as the material editor for Rhino. We believe that this release brings a lot of value to all our users, even though the material editor in ArchiCAD is still missing.

    Why does the Rhino plugin have the material editor? Because we had to start with one CAD - and the Rhino plugin was released in November 2017 while the ArchiCAD plugin was released only 7 months later.

    We actually did plan to include the material editor for ArchiCAD in the 2.5 release as well, but priorities change over time (some other features become very important suddenly).

    In the end, we were confronted with the decision to either remove the ArchiCAD material editor from the 2.5 release or delay the 2.5 release even longer. We decided to deliver the bugfixes and improvements to you as soon as possible.

    Sorry if my words have been unclear to you in the past. It is scheduled for 2.6. We have planned a scope of features for 2.6 which does include the asset editor for ArchiCAD. However, being scheduled is not the same as being done. I can't promise you when the material editor will be integrated, but we're trying our best to make it happen.



    All good, I guess the only thing is that we cannot use the viewport when the editor is switched on, but I imagine that's just wip?

    This unfortunately is final. We couldn't find a way to track all changes done in Rhino. So we made the material editor block the viewport to prevent Rhino and Enscape from going out-of-sync.


    Is Rhino 5 supported for the new material editor?

    No, the Rhino 5 SDK is lacking a few methods that we need to properly map the materials to their objects.


    I can't find the material options - any ideas?

    In native Rhino you need to switch the materials to the Enscape type, but we decided to not use the integrated UI as it is very limited. Instead you can modify all Enscape materials by opening the material editor window via the toolbar or command "EnscapeOpenMaterialEditorCommand"