Chaos Enscape Ideas Portal
The online platform for Enscape users to submit, vote, and collaborate on creative suggestions.
The online platform for Enscape users to submit, vote, and collaborate on creative suggestions.
Hi Enscape team,
it occured to us that it's not possible to export any enscape renderings - neither .exe files nor the webbased .exe - on our iPad to show.
We want to show our costumers the renderings directly on the construction site on our iPad - just like the 3d model exported from Vectorworks 2024 as .vgx file to the Vectorworks Nomad app.
Please consider to offer export functions compatbile with iPad, its crucial to our work and how we show and present our planning.
Thank you!
Best regards,
Julian Flamm
Help Us Test the New iOS Mobile App
We’re running a user research study to explore the new iOS Mobile app - a mobile experience that lets you view and interact with shared 3D scenes directly on iPhones and iPads.
If you’re interested in helping shape the future of this app, we’d love to hear from you!
Please fill out this short questionnaire to take part: https://forms.gle/j2FQUiNvUArwFfA38
During the session, we’ll walk you through an interactive prototype and ask for your feedback on the experience — no installation required.
Thanks in advance for your support!
We’re excited to hear your thoughts and ideas.
0
Planned
0
Planned
I found out yesterday that enscape is no longer supporting stereo panorama (google cardboard) functionality for iPhones while teaching a class on this very thing.
From the support ticket:
"We discontinued Google Cardboard functionality with panoramas uploaded to the Chaos Cloud. We made this decision based on two factors:
Chaos Cloud did not have native compatibility with Google Cardboard
Google itself has deprecated Google Cardboard and no longer actively updates or responds to inquiries about its software.
We've since moved to WebXR; however, iOS currently doesn't support WebXR. Our product management team is investigating this matter with our developers to see if it can still be resolved using the currently used technology."
Why would you deprecate a feature that worked for likely more than half of the mobile devices without a fix in place?