Previous Release / Preview Threads Merged

REMINDER! If you encounter any issues with Enscape (e.g. crashes, installation problems) or your subscription please reach out to our dedicated support team directly through the Help Center or by using the Support button as detailed HERE! Thank you for your understanding.
    • Official Post

    Enscape4.0 Add this feature ?

    This feature will not make it into our upcoming 4.0 release, but it's something we plan to implement with our next release of Enscape, likely providing this addition in future upcoming previews to try out beforehand as usual.

  • Thank you for the additional feedback as always Paul Russam and Ondrej42.


    This won't be much of a satisfying reply I'm afraid from my side but there is actually a technical reason as to why the previously selected material is not automatically re-selected after re-opening the Material Editor.


    That in turns means that isn't a bug currently, but expected behavior. I will still make sure to get together with product management regarding this to see if we could perhaps adjust this in the future eventually. For now I'm afraid there isn't much more I can say other than that, though I'd definitely update you in case of any further specific news soon.

    ...but it used to work as expected, yes? At least I think I can remember a time when it did. This one is an ongoing annoyance for me as well.

    • Official Post

    Dear Forum Community,


    We've just released our latest Enscape Service Pack 4.0.1!


    NEW:

    • SketchUp 2024 Support
    • Revit 2025 Support


    BUGFIXES:

    • Metallic Materials Become Too Dark in Reflections
    • Incorrect Shading of Foliage Materials With Ray-Traced Artificial Lights
    • Significant Stutter During Camera Movement After Loading Scene
    • File or Folder Paths Displayed in the UI Became Invisible After Hovering Over
    • Panorama Fly to Functionality Was Hidden
    • “New” Category in Asset Library Was Not Populated
    • An Error Occurred While Switching Asset Variants
    • Fixed a Crash on Switching the Project in Sketchup, Archicad or Rhino While the Enscape Custom Asset Editor Was Open
    • Fixed a Crash on Site Context Import When Cad Project Was Closed
    • Fixed an Issue With Asset Selection While Using the Translate Tool in the Renderer Asset Library
    • Fixed Some Textures Appearing Too Dark Randomly
    • Fixed an Error on Mac When Importing Custom Assets From .obj Files That Contain Windows Paths
    • SketchUp – Fixed Material Not Being Deleted When Removed From Imported Model
    • Revit – Removed Misleading Logs
    • Rhino – Fixed Texture Getting Lost When Converting Material Type to Enscape


    KNOWN ISSUES:

    • Rhino Viewport Always Changes When Selecting Enscape View


    To see what has been added with Enscape release 4.0 please refer to this announcement here.


    If any questions or further feedback arises, please let us know via this thread or by reaching out to support. In case your experience any crashes, freezes or similar, ideally submit a feedback report with log files directly if possible.

  • Hello, is the camera settings input field bug fixed in this? I can't see any mention of it on the list.


    We are waiting for it to be addressed, otherwise we cannot upgrade to 4.0 yet as that feature is used on a daily basis in the company.


    Thank you!

  • Hello, is the camera settings input field bug fixed in this? I can't see any mention of it on the list.


    We are waiting for it to be addressed, otherwise we cannot upgrade to 4.0 yet as that feature is used on a daily basis in the company.


    Thank you!

    Demian Gutberlet would be be kind to reply to this please? 🙂

    This is really important and we've been waiting for 4.0 for a very long time but we cannot upgrade, because of this bug.

    It's been reported here: RE: Enscape 4.0 - Bug when trying to type camera values.

    • Official Post

    Demian Gutberlet would be be kind to reply to this please? 🙂

    This is really important and we've been waiting for 4.0 for a very long time but we cannot upgrade, because of this bug.

    It's been reported here: RE: Enscape 4.0 - Bug when trying to type camera values.

    I'm afraid this behavior continues to persist in our latest service pack, as we currently still remain in the process of resolving this internally. I'll definitely let you know right away once there's any progress or updates to share soon.


    I also am aware that this isn't ideal, but it should still be possible in the meantime to paste any specific values which have been copied into your clipboard prior. So copy-pasting something like "0.55" (as per your example) should do the trick. Again this is not the ideal solution but perhaps it would suffice until this is fixed soon.

    • Official Post

    Paul Russam and Tim , pardon the delay here but currently the option to "Save as external model for Enscape" remains disabled, though we're already looking into reworking this specific functionality so we can provide this feature once more in the future. There is no specific release date or such I can mention yet though. Also Paul Russam , I'll have to reach out to you again regarding the crashes, expect another message very soon via the existing case of yours or here.

  • Paul Russam and Tim , pardon the delay here but currently the option to "Save as external model for Enscape" remains disabled, though we're already looking into reworking this specific functionality so we can provide this feature once more in the future. There is no specific release date or such I can mention yet though. Also Paul Russam , I'll have to reach out to you again regarding the crashes, expect another message very soon via the existing case of yours or here.

    Wait, if that feature is disabled, do I understand correctly, that the ability to make 3D proxies has been deactivated indefinitely?

  • Wait, if that feature is disabled, do I understand correctly, that the ability to make 3D proxies has been deactivated indefinitely?


    Correct. Hoping for them to bring it back....quickly. Because it's incredibly useful- but luckily there are other methods to make a quick proxy. If it gets postponed and moved to the "voting portal" I'm gonna lose it :P .

  • Correct. Hoping for them to bring it back....quickly. Because it's incredibly useful- but luckily there are other methods to make a quick proxy. If it gets postponed and moved to the "voting portal" I'm gonna lose it :P .

    Oh God, then that's another reason why we will not upgrade.

    We use the Plus sign and import SKP 3D models as Enscape proxies into our interior scenes (so that we don't spam the Material and Components list with extra unnecessary things that are only used in the 3D asset). But if we can't do it in v4.0 then we will not upgrade until it's fixed. We use that feature on a daily basis.

  • Oh God, then that's another reason why we will not upgrade.

    We use the Plus sign and import SKP 3D models as Enscape proxies into our interior scenes (so that we don't spam the Material and Components list with extra unnecessary things that are only used in the 3D asset). But if we can't do it in v4.0 then we will not upgrade until it's fixed. We use that feature on a daily basis.

    No, not quite like that. Sorry, I should have read your statement more clearly. You can still use linked models/proxies. The right click option to quickly "save as external model" was removed.


  • We have noticed significant visual issues when using Enscape 4.0 to connect to a Meta Quest 3 VR headset.

    There are serious rendering quality glitches when moving around the model, and it takes more than a few seconds for any shapes to be redrawn when movement stops. We tested Medium, High, and Ultra quality and with each level the issues were progressively worse.


    Has this been addressed in v4.1?

    For clarity - we did not experience these issues when using Enscape 3.5 and Steam VR to connect to the Meta Quest 3 .

    • Official Post

    We have noticed significant visual issues when using Enscape 4.0 to connect to a Meta Quest 3 VR headset.

    There are serious rendering quality glitches when moving around the model, and it takes more than a few seconds for any shapes to be redrawn when movement stops. We tested Medium, High, and Ultra quality and with each level the issues were progressively worse.


    Has this been addressed in v4.1?

    For clarity - we did not experience these issues when using Enscape 3.5 and Steam VR to connect to the Meta Quest 3 .

    Welcome to our Forum.


    Please ideally submit a dedicated support report right away as detailed here so that we can also check out your machine information to see what kind of graphics card, active settings and such you're currently making use of for VR, alongside the attached log files which may give us further hints why you experience this behavior. In general whenever you experience issues within Enscape that is the ideal way to reach out for help.


    Thank you very much in advance, you will receive a response back via the created case very soon thereafter.

  • We have noticed significant visual issues when using Enscape 4.0 to connect to a Meta Quest 3 VR headset.

    There are serious rendering quality glitches when moving around the model, and it takes more than a few seconds for any shapes to be redrawn when movement stops. We tested Medium, High, and Ultra quality and with each level the issues were progressively worse.


    Has this been addressed in v4.1?

    For clarity - we did not experience these issues when using Enscape 3.5 and Steam VR to connect to the Meta Quest 3 .

    Have you tried turning off the Ray Traced Artifitial light option. This is a very heavy option to have on.