Same issue here
Looks like enhanced online panorama features are coming - but really what I need is to be able to batch render panos. Most of my clients have web design people who just need the raw pano, and the one thing that takes forever in my workflow is to re-render panos when something in the model changes.
Found it hereQuote
Hello! We are constantly working on improvements of image quality, stability, performance and application usability. We are aware of the demand on better reflections, animation and other long awaited features. But some things just can't be easily implemented in a short period of time, no matter how much we want it - sometimes a big amount of work on the infrastructure is needed to make future improvements and new features possible. Moreover, we have more than one development team each focusing on different parts of the product - rendering engine programmers are not implementing UI or CAD integration. So be sure that we are not sitting without doing anything while other teams are working hard and other departments are doing rebranding
That is a comment made by one of your enscape team on this forum (i don't have time to find it sorry) in relation to the many complaints about the lack of "new features" in the enscape 3.0 release, and that is basically a UI update only. He indicated that a number of the development teams were not needed or had limited involvement for this version and that they had been working hard in the background on "other important stuff".
Given that 3.0 is quite a disappointment for many of us and maybe foolishly thought that 3.0 would be a major release with a raft of new features/workflow enhancements/fixes. So with that in mind many will be interested to see what coming in 3.1 and beyond
As most of the developers have not been required in the 3.0 release (its only really a UI update) can we have some good news on the road map for 3.1 and beyond
First off; I appreciate all the work you do. I'm especially glad with how you respond to requests on this forum, so thanks.
But in this case I am concerned. The 3.0 version just dropped, and of all the possible features you could have added, I see none. Am i missing something?
Apart from a new UI and a new logo (which is just a mirrored 9gag logo btw...) are there some actual new features we actually need?
- relative paths/proxy manager
- batched vegetation brush
- winter vegetation
- full reflection
- filled sectioncuts
- appropriately behaving shadows in sections
- 360 video
- vertical water movement
- animated objects
I get that things take time, i truly do. But these requests have been circling the forum for two, even three years, yet i haven't seen a single request about a new look.
I am quite dissapointed and really hope some features are added soon.
Thanks in advance
(thanks for fixing the Scale Assets issue quite fast. Thats appreciated)
I couldn't agree more, I thought that a 3.0 version would be a major upgrade/update, disappointed its basically an updated UI, but apparently they have consulted with their user base and this is what was wanted, go figure
Tearch Nuge I completely understand your wish to get more precise feedback on the feature requests and we will definitely try to improve it in the future but unfortunately it is not always easy. As you can imagine, we get a lot of feature requests via different channels not only the forum. And be assured , we collect and document all of them and of course we also note how strong the demand is for individual features. So if we say "Thanks for the upvote" or " It is heard" be assured we document it and are aware of every request.
For our planning which features will come next, we carefully evaluate all requests. In addition, we keep a mix between planning ahead and still being able to react to urgent circumstances at relatively short notice. For this reason, we can not always say with certainty when exactly a specific feature will come. And that's the reason why we don't make any promises until the features are finally scheduled.
Regarding the Batch Pano , at the moment I can only tell you it definitely won't come in Enscape 3.1
I know, this is not the most satisfying answer but I hope it helps you to understand it a little bit and as said we'll try to improve it in the future.
Thank you very much for all the great feedback !
Sorry but i take exception to your comment "In addition, we keep a mix between planning ahead and still being able to react to urgent circumstances at relatively short notice". I have been using Enscape for many years and i am yet to encounter any feature that has been reacted to "at relatively short notice". you just have to look at this forum to see how long user have been requesting batch rendering for Panos. if your team had to render 20-30 panos for a project i am sure it would have made it into enscape quite some time ago.
All of the "feature requests" your users make are based on real world problems/bottlenecks that exist in our businesses everyday, some more problematic that others, as a product manager you should be acutely aware of these issues and be advocating strongly to your developers on our behalf. Let avoid another release cycle where the only change is an updated UI when so much more could have been done to enhance enscape as a usable product.
thanks for keeping up your voice about the visual settings, Herbo.
Just to clarify it a bit more from our perspective:
Some of us had the exact same concerns when defining with our UX department the changes for the relocation of functionality. In this case we had strong arguments for both sides. As we did not have enough information to be sure which option would be the better one for all of our users, we let the general UX guidelines decide.
We already knew that it might be possible that it is the wrong decision and that we have to change our direction afterwards. But 'afterwards' in our situation means 'after 3.0'. Before we introduce further changes, we need to have more feedback from more users to base further decisions on a solid basement.
So far we received mixed feedback that is not quite telling (and the forum is not our only source).
This topic IS on our table and we are observing it. But we did not decide to change the current behavior, yet.
Maybe we will introduce a preview with changed behavior in a few weeks. But maybe we won't.
We will keep you up to date on this.
Thanks again. All your feedback is much appreciated!
I am curious about what other sources you use to make these decisions, I would have thought that feedback from your user base is one of the most important as we are the ones using your product in the real world everyday, Small decisions made by your UX team are having major implications to a number of users (Refer to Herbos comments) and this could have been resolved very early in the development process had you involved your user base. Previously you had a trello board which was a great feature but you decided to discontinue that in favour of "upvoting". As i have said many times on this forum as users we have no idea what MIGHT or MIGHT NOT be coming in future releases. Why don't you provide a list of items that have been upvoted with the corresponding number of votes, I am sure that most users would have expected more from a major release (3.0) than a UI update
Wouldn't it be beneficial to everyone to make exporting in one or two steps an option in the preferences and just disable it by default? This way users that are accustomed with the current workflow can use it the way they're used to (one click for Opening Enscape & starting the export) while users with larger projects such as Herbo can use the two step method (two clicks - open Enscape, start Export).
Agree simple & elegant solution, Cant understand why the developers wont make this an option, seems like a no brainer to me
Need batch rendering for pano and video. If you think people are just using Enscape for renderings, then the marketshare will be quite small...
And i totally agree with Herbo regarding not loading the model on enscape load up, its a no brainer
Nice video, yes i am also interested to know how enscape handles this
what Herbo says!!
pretty straight forward we don't want to open the enscape window to access the settings, needs to be done on the cad side
Keep the visual Settings button in the menu +1!
I want to keep the visual Settings button in the menu so that I can still conditional visual Settings without turning on render