Posts by Simon Weinberger

    There is a problem with the shadows in 2.6. When changing the Time of Day in Enscape, only the zenith changes, the azimuth doesn't react to the Time of Day change. When changing the time in SketchUp the zenith and azimuth changes correctly.

    GWD This is already fixed and will be included in the next preview.

    Hello everyone,,

    Did anyone have an issue intalling this on sketchup 2019? it loads on 2018 and archicad but not sketchup 2019. There is an account of enscape in the warehouse management but no options for enscape tools or drop down menu. it was working before but when i updated in the last release everything disappeared. i unistalled and reinstalled with older version and rebooted. no change.


    Thanks!

    I know this behaviour happens when you have Enscape installed both per-machine and per-user. If you see Enscape both in "%AppData%\SketchUp\SketchUp 2019\SketchUp\Plugins" and "%ProgramData%\SketchUp\SketchUp 2019\SketchUp\Plugins" then this is your problem. Uninstall every version of Enscape and do one fresh installation.

    "Install for all users of this machine" worked for me. Thanks

    kirkPJS   tandem.design


    I don't believe your issue has to do with install per-user vs per-machine. Instead it's an issue to have the exe installer (up to 2.6-preview.4) installed in one mode, and the msi installer (from 2.6-preview.5) installed in the other mode. This leads to SketchUp (2019+) knowing both Enscape versions and getting mixed up, somehow SketchUp 2018 can handle this better.


    For the clean experience, please try to uninstall all Enscape versions (Windows / Settings / Apps & Features) and after that perform an installation of the MSI in the mode of your choice.

    In the morning, I updated the fifth version of preview version 2.6. After clicking the render, the software could not start and reported an error. I have sent the feedback. I have an idea for specular reflection, can be compatible with the speed and quality, whether can develop a material alone, is used to specify to the mirror, can reflect more close most of the objects, rather than each material has the property of such, then add must face to this material number limit, for example, a scene not more than 10?

    Thanks for reporting. I've found the feedback you sent and linked everything together. We'll take a closer look soon.

    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.