A little background on my office's Enscape Workflow. We use Enscape for internal design review and renderings for client presentations. Occasionally, we will export a standalone model and cycle through set views. Daylighting and Element Visibility are important factors in this process, especially when showing design options. In my opinion, the best aspect of Enscape was the speed and ease renderings could be created.
I have loved the program since I started using it nearly 4 years ago. However, these most recent updates (in 2021) have caused me quite a bit of frustration. Before the update, users had the ability to control the creation of views within Revit and were independent of the Enscape Software. This allowed users to have one "base view" that we would use to launch Enscape and then have the ability to navigate the different star views without switching from the base view. This was crucial because it allowed a consistency across images, in terms of what was visible in each view, landscape elements, hidden elements in views, and the specified daylighting for the base view. The view creation in Enscape is now native to Enscape and automatically switches to a new base view each time you change the view. Furthermore, the daylighting settings are selected and saved but then will not apply when returning to the view. Additionally, when using design options it requires you to create a new view for each design option. Therefore, the image/rendering is nearly impossible to recreate exactly. Beforehand, you could set a single view then cycle through the options. This kept everything in the rendering, except the design options, exactly the same. This is crucial in comparing the options. While these may seem like minor items, they can cause a massive amount of time to be added to generating renderings, which is not ideal. The part that is most frustrating is the fact that these were not issues before and in fact were beneficial, so why change them?