Previous Release / Preview Threads Merged

Please cast your votes in our two ongoing feedback polls here and here!
    Quote from comcasa

    I'm wondering whether Enscape Materials for Revit is going to support only Legacy Generic type materials? Or is it planned to support the new PBR shaders?


    I ask this because we want to migrate to Enscape Material Editor and all of our materials were created with Revit PBR Shaders (not the legacy ones) and for now Enscape seems to support only generic legacy materials.

    Wondering same thing, also using Revit PBR Shaders, using Enscape for rendering and VR but also Vray, Unreal and Twinmotion and sometimes even Revit itself. Revit PBR Shaders works quite nicely with Vray and with Unreal Datasmith PBR's transferring quite nicely to Twinmotion and Unreal too. Now just waiting Enscape starts to support better those Revit PBR Shaders in Enscape Material Editor.

    Thanks for a great update team. I just have a few questions / comments.


    1. The glass shaders seem to all be frosted or textured? Can we have clear glass?

    2. If there is a way to still be able to click on the model whilst the Inscape material library window is open like the Enscape material editor.


    Thanks

    Hola! Tengo la licencia educativa, y quería saber si igual podía actualizar mi Enscape descargándome esta última versión. De ser así, cómo haría para que no se crucen las dos versiones del programa?

    Hi Majo_1909


    Welcome to our forum!


    Please communicate on the forum in English or use a translator if necessary :)


    Quote

    Hola! Tengo la licencia educativa, y quería saber si igual podía actualizar mi Enscape descargándome esta última versión. De ser así, cómo haría para que no se crucen las dos versiones del programa?


    -------


    Hi there! I have the educational license, and I wanted to know if I could still update my Enscape by downloading this latest version. If so, how would you prevent the two versions of the program from crossing over?


    You can of course update to our latest version, no limitation there.


    You can simply install the latest release, and this will replace the older version, so no issues there.

    Hi @10F1DESIGN

    Quote from 1OF1DESIGN

    1. The glass shaders seem to all be frosted or textured? Can we have clear glass?

    Thanks for the request. I take it into account. You can already use these physical glass parameters:
    Acrylic glass: #D2D2D2, Roughness: 0.0%, Opacity: 0.0%, Refraction Index: 1.490
    Glass: #D2D2D2, Roughness: 0.0%, Opacity: 0.0%, Refraction Index: 1.500

    Quote from 1OF1DESIGN

    2. If there is a way to still be able to click on the model whilst the Inscape material library window is open like the Enscape material editor.

    That doesn't work. Technically you pick and download these materials beforehand from our Material Library and then use them in your favourite CAD. I forward this to UI/UX to take this into consideration.

    Hello! My firm is very slow to roll out updates, so I will likely not be able to test this for some time.

    However, I just wanted to say bravo and well done, an excellent slew of new and meaningful features!!!


    Though, I have to sneak in a nag as well, I will keep waiting for better reflections.

    Even if it was a checkbox in a material to say this material is special and deserves the extra processing and memory allocation required.

    It makes a big difference for glassy facades to see even a low resolution reflection of the model context, not just an empty skyline.


    Awesome work yall, keep the great updates coming :)

    Always happy to hear such positive feedback. Thanks for the input. :) I'll forward your feedback about our reflections as well to our product management team. I appreciate it and hope you get to try 3.1 or any upcoming preview soon!

    ag3086 , I'm afraid Revit 2018 does not support the Material Library or Editor. In that regard, we recommend using any version which came after 2018. Hopefully, this is a possibility for you.

    Here's the Release Notes for the latest Enscape v3.2 Preview - Version 1.

    Please refer to this article for instructions on how to download the Preview version.

    Note: Preview versions are not production proven, so make sure to observe the Known Issues in the attached .pdf document and please report any other issues back to us either on this thread or via the normal support channels.


    What’s included:


    • Batch Panorama Export
      The Batch Export menu item has been reworked to become a top level toolbar entry in its own right. You can now export Panoramas (both mono and stereo) in the same manner as you could previously export a set of single images to Batch Rendering. Clicking on any of the items in the drop-down will begin the export process.


    • Visual Settings Presets - Usability Improvements
      After some reports regarding the Visual Settings Presets expansion panel (via the chevron button) and its direction of expansion, we've reworked that expansion panel direction to reveal the Presets list so that it better aligns with user expectations. Additionally, we reworked the implementation of the Visual Presets Create and Rename process. You can now confirm creation of a Visual Setting Preset as before by using the [ENTER] key. Or, you can use the explicit User Interface (UI) elements to confirm or discard your changes.


    • License Model Changes
      In this Preview version we have adjusted how license seats for Enscape are handled. A seat will now be occupied when any of the Enscape key features are in use, specifically: Enscape Renderer, Material Library, Material Editor, Asset Library, and Enscape Objects (SketchUp only). This change is to reflect the value these key features bring to the end user as well as the investment we are making to constantly improve and develop Enscape.


    • Archicad 25
      Support for the most recent Archicad version has been added.



    A full list of Bug Fixes and Known Issues can, as always, be found in the attached document. Please refer to the bug's / issue's associated ID number when contacting Enscape Support in relation to any of these listed items.


    If you run into any issues while using this Preview version, please do not hesitate to contact Enscape Support, ideally by submitting feedback with logs attached (via the Enscape Feedback button) which allows us to help and resolve issues or make adjustments to new features as quickly and effectively as we can.

    Re Batch Rendering:

    In 3.1 (and I assume 3.0) when selecting multiple images to bach render I can no longer click on the 1st one and then [SHIFT] Click on the last one, I have to select each one individually.

    Can something be done about this? Having to manually select 20+ images to batch render and then manually deselect them so I can manually select another 10 that are different is now very tiresome.


    Oh yea ..... BATCH RENDERING PANOS!!!!!!!!!!!!! ..... I'll wait for a later beta or the release but this is going to be a killer feature for me. :)

    Quote from Pete Chamberlain
    • Visual Settings Presets - Usability Improvements
      After some reports regarding the Visual Settings Presets expansion panel (via the chevron button) and its direction of expansion, we've reworked that expansion panel direction to reveal the Presets list so that it better aligns with user expectations. Additionally, we reworked the implementation of the Visual Presets Create and Rename process. You can now confirm creation of a Visual Setting Preset as before by using the [ENTER] key. Or, you can use the explicit User Interface (UI) elements to confirm or discard your changes.

    These are good changes, but what I still miss the most since the introduction of the new presets: why does "create new preset" always resets the settings? I find myself finetuning a view with the perfect settings, and then be like "oh this looks nice, lets save this out as a preset", and then when you hit new preset you lose all the settings... this doesn't make any sense to me.


    If the users wants a clean default, they can always create a new preset -> right click -> reset to defaults. But the default behavior of "create a new preset" should be to keep the current settings.


    (I know one can duplicate the current setting, but it's unintuitive so people forget and use the "new preset" button instead, which erases their current setup.

    3.1 is way too visually glitchy for me. Going back to 3.

    Couldn't even run with DLSS turned on because of the ghosting (already reported), and very odd effects on my PNG background edges (especially trees) whenever I'd start moving.


    No matter what the settings combo, there's massive flickering that occurs on glass reflections from light fixture sources when inside a space. For instance, rows of linear light lenses within an office space (white with some self illumination) flicker madly on the exterior glass when moving around the space.

    My NVIDIA driver is current.

    Quote from Pieter

    These are good changes, but what I still miss the most since the introduction of the new presets: why does "create new preset" always resets the settings? I find myself finetuning a view with the perfect settings, and then be like "oh this looks nice, lets save this out as a preset", and then when you hit new preset you lose all the settings... this doesn't make any sense to me.


    If the users wants a clean default, they can always create a new preset -> right click -> reset to defaults. But the default behavior of "create a new preset" should be to keep the current settings.


    (I know one can duplicate the current setting, but it's unintuitive so people forget and use the "new preset" button instead, which erases their current setup.

    I know "the user is never wrong" but I think the mental model does not quite match. Your changes are always immediately persisted in the preset so after tweaking it you already end up with your perfect preset. The preset you just tweaked holds this exact state now if you create a new one you start fresh and if you want to start based on another preset you can just right-click and duplicate.


    EDIT: Nonetheless I'll note this down on the UX side :)

    Quote from Paul Russam

    Re Batch Rendering:

    In 3.1 (and I assume 3.0) when selecting multiple images to bach render I can no longer click on the 1st one and then [SHIFT] Click on the last one, I have to select each one individually.

    Can something be done about this? Having to manually select 20+ images to batch render and then manually deselect them so I can manually select another 10 that are different is now very tiresome.


    Oh yea ..... BATCH RENDERING PANOS!!!!!!!!!!!!! ..... I'll wait for a later beta or the release but this is going to be a killer feature for me. :)

    Hi you can select the entire project with the checkboxes next to the headers, I'll note down the missing support for SHIFT style selection on our end.

    Christian Radowski

    What'll happen for me is that I setup and render (lets say) 20 views.

    The client will ask for more (lets say 10) so now I have to deselect the existing 20 and select the new 10.

    The client makes changes so I now deselect the 10 and select the 12 that see the changes.

    .... And on it continues, I rarely render 'all' the views in one go throughout the project's lifetime, it's usually at the end so we have the 'definitive' set all in one folder.


    Thanks for replying and looking at the [Shift] selection

    Hi landrvr1


    Sorry to hear that.


    Do you have a sample file for us where the odd effect with the PNG background shows perhaps?


    I have seen some flickering (more than 3.0) myself as well, however do you have another sample project perhaps where this all shows clearly for us as well?


    You can send me a DM for example with a Wetransfer link if possible so we can look into this.