Previous Release / Preview Threads Merged

  • Hi Paul Russam


    Thank you for pointing this out.


    I was unable to reproduce this issue, is this occurring for you in multiple projects or only in a specific one?


    Would you be able to share a (test) project with us where this is happening?


    If so you can send me a link through a DM with for example WeTransfer?

  • Thalles Eduardo , please kindly also include an English translation to your posts that are not in English so everyone can read what you're saying. :)


    Madiyorbek , weather effects/animated models are currently not planned for the near future but your feedback wish to have this implemented has been forwarded!

    I would say weather and animated models would be great - we are experimenting with TwinMotion at our firm even though we all prefer Enscape's graphics for the sole reason that some designers like the animated weather and people.

  • I would say weather and animated models would be great - we are experimenting with TwinMotion at our firm even though we all prefer Enscape's graphics for the sole reason that some designers like the animated weather and people.

    Welcome to our Forum - I have of course gladly forwarded your Feedback for consideration as well. Let me know in case anything else comes up.

  • Just sent a message via Vectorworks but to add here - with Vectorworks when you try to delete assets from Enscape using the Del key or using the bin icon you get an error message when hitting Apply changes.

    We were unable to save all the pending changes. Please try again


    I am working in Vectorworks 2022 Build 614805

  • I don't see the benefit right now of this new placement method for assets.


    I tried it a while, but I can see just as much as in the CAD (because you're still only showing placeholders), but it's much slower because of the required 'saving back to cad' thing. It's just faster and more precise to place directly in my CAD application and it has the benefit that I have all the tools I'm used to for placing.


    I also have serious concerns about how the hosting is handled in Revit. Objects placed in Enscape are not hosted to any level or floor, instead they are just placed relative to the internal origin. They don't even 'have' a level, which as far as I'm aware can only be done through the API. This is going to trip people up a lot. For example all our furniture is scheduled by level, so if designers go in an place Enscape asset furniture they will not show up in our schedules.

  • Um, why? Why add a new way to place assets that can be done perfectly well (or better) through the native app? Is this another step in moving more pieces of enscape out of the native app as a benefit to the company, not the users? How about fixing how lights are placed for example? Kind of disappointed that this is the focus of your development efforts right now.

  • Um, why? Why add a new way to place assets that can be done perfectly well (or better) through the native app? Is this another step in moving more pieces of enscape out of the native app as a benefit to the company, not the users? How about fixing how lights are placed for example? Kind of disappointed that this is the focus of your development efforts right now.Tp

    To continue...one of... if not the key point of Enscape is that it is "Real-Time". So what is the point of controlling assets through the Enscape window if it instantly changed through the native app? We can already control these things through the "Live Updates" button. What does is it provide to the user?

  • I too struggle to see the benefit of this whole implementation. It seems like a much slower, more cumbersome way of doing stuff? placement and move tools are much more evolved in sketchup, and thereby it is much faster. Furthermore i have loads of plugins (like skatter), that makes it even easier! Are you planning on doing something like lumions ability to populate large areas with few clicks? like placing different people, trees and cars along a path?

    I know that a lot of users must have requested this, otherwise i hope developement time would be spend other places. But for what reasons is it requested? can You share some of the use cases for this?

  • Are you planning on doing something like lumions ability to populate large areas with few clicks? like placing different people, trees and cars along a path?

    That would be my guess as well for the end goal of this feature, but I really don't see how this will integrate nicely into the cad applications.


    All 5 platforms have their own specific logic, a one-size-fits-all is going to put a strain on the whole 'enscape integrates tightly with the host platform' paradigm.


    The #1 reason we picked Enscape as our rendering platform is its tight integration with the host platform. This new approach starts to abandon that approach, where Enscape starts to offer its own model editing tools rather than integrating with the host application.


    Sometimes if a feature request requires you to compromise heavily on the main foundation that your tool is built on, it's better to say no, even if that's not what customers want to hear. You can't expect the typical user to understand the technical limitations of all these different API's.

  • Thank you everyone for your Feedback so far regarding the new WIP Asset placement method. While I can of course understand your concerns as well, this is merely an additional feature we wanted to add to Enscape since it has also been requested by quite a few users, albeit through the Forum Feedback alone that wasn't really obvious.


    It's also an additional feature so of course no one is obligated to use it - While I also get that many of you are already familiar with placing Assets through the CAD solution and using the built-in placement tools from Revit, ArchiCAD, Rhino, SketchUp and Vectorworks, this is a solution we've added to also make it easier to place Assets more quickly if one isn't familiar (yet) with the main CAD solutions controls or in case that user doesn't want to use their provided placement methods. As per my reply to Herbo below, we'll also add a scatter-like functionality through Enscape directly, alongside other things to come of course.


    Pieter , this feature is of course still highly WIP so this may all be subject to change - I have for sure forwarded your concerns and additional Feedback.


    andybot , I'm afraid I'm not entirely sure what you mean by "Is this another step in moving more pieces of enscape out of the native app as a benefit to the company, not the users?" - Of course we will have to provide features that our users actually like and use to be able to exist as a company in the first place. There aren't any ill-meant intentions to get rid of the CAD solution part or anything like that, which is why the Asset Library placement is and will be optional alongside the "traditional" methods.


    Herbo , we actually do plan to implement something similar to scatter, but the difference here is that it would be available for and with any CAD solution we support, which is one of the reasons we implemented this functionality in the first place.


    Please keep the Feedback coming of course and I hope some may change their mind and eventually don't mind that new feature or actually use it, especially once it's out of "work in progress" and more fleshed out. :)

  • I don't mean that the host app asset browser will disappear as soon as this Enscape window browser is complete. I'm imagining a few releases down the road, in the name of having a consistent "in-Enscape" management, the browser in the host app will one day disappear. I'm not sure my concern matters though, I'm just a little jaded from seeing the way these things play out, over the many years I've watched various rendering apps go through their development cycle.