In my testing there does not seem to be seamless way to replace panorama content rendered and uploaded from Enscape with new content Rendered and uploaded from Enscape. The only workflow I can see is to physically download the the new panoramas from enscape or the web and reupload them with the “Upload new version” option. It would be amazing if there was a more integrated workflow that would allow us to swap out existing enscape panoramas with new ones without having to save down and re-upload them.
+1 on this.
I’ve noticed recently that the ability to import files directly from the enscape panoramas section was added, which is great, but then as soon as versioning comes into play it becomes a manual operation again. it’s still also really frustrating that when panoramas are uploaded they’re uploaded with the project name and time stamp, but completely omit arguably the most important info which is the view name. Every upload has to be manually renamed. Desperately need a better way to control the automatic naming, and uploading, and adding new versions.
Hi again!
We are working on bringing a more advanced integration with Enscape that will streamline all content uploads as well as allow you to upload versions for existing files directly from Enscape.
However this update requires quite some changes on the Enscape product side so it will take some time to finish. We are aiming at the end of summer release in 2025