Web Standalone Problems

AlexS · Nov 2nd 2018

Hi,

I'm testing the web standalone export in 2.4 (Build number 2.4.18304.1341). Having attempted to export a huge model, and discovering the maximum recommended upload size limit of 500Mb, I've reduced the complexity of the model (in this case, removing all the furniture & equipment) and re-exported without any file-size warnings appearing.

However, once the progress bar has reached the end, chrome displays an "Aw, Snap!" error. Here's the model - https://api2.enscape3d.com/v1/…a8-400d-b509-58458c47cba8

I've had no problems so far with smaller models.

Thanks,

Alex

Demian Gutberlet · Nov 2nd 2018

Hey AlexS , I'm able to reproduce this issue. Thank you very much for the report!

Our developers will have a closer look at this behavior and we'll get back to as soon as possible.

ArchuCAD · Nov 7th 2018

I am also having this problem. Has it been resolved?

Demian Gutberlet · Nov 8th 2018

@AlexS and @ArchuCAD we're still in the process of resolving this behavior. Thanks a lot for your patience!

perdueterrance · Nov 14th 2018

I'm also having this issue. I tried the link in Edge, FF, and Chrome, but have had no luck.

Demian Gutberlet · Nov 14th 2018

Thanks for your feedback perdueterrance , as mentioned, we're working on resolving these problems.

Sean Farrell · Nov 15th 2018

What happens here is that the browser is running out of memory. This behavior is unfortunately unavoidable, since that depends on your device memory, the browsers security setting and many more factors. We are working hard to reduce the memory footprint of the web standalone, but this is a challenging thing to do.

In the meantime, what you do is either simplify your geometry, as AlexS mentioned and export subsections of the model.

jgendell · Nov 20th 2018

I want to add to this post by saying I think the Web Standalone is a great feature in concept.

However we have tried it recently with a client and the detail level is not nearly as good as we were expecting. We also had an issue where the lighting behaved erratically - flickering on/off. Another model we uploaded the lighting dissappeared altogether, even with the time of day correctly set before upload.

I just wanted to report our feedback. But I stand by the new feature.

Sean Farrell · Nov 21st 2018

@jgendekll Could you report the issues you are having and links to the web standalone through the Feedback Button? This will allow us developers to trouble shoot your issues. Thank you.

MatthiasF · Nov 23rd 2018

Hi Sean Farrell ,

i'm having problems with the webstandalone too. The export runs, but when i want to open the model on Chrome, it always stopping at the same status.

i tryied it with other models and it runs perfect

Demian Gutberlet · Nov 23rd 2018

MatthiasF , could you please send us the link to the Web Standalone? If the project is confidential, you can also send the link via PM. Thank you in advance!

MatthiasF · Nov 23rd 2018

Demian Gutberlet , how and where can i send a PM to you? I don't find a button

Demian Gutberlet · Nov 23rd 2018

MatthiasF , just click on my name and then:

Thanks a ton in advance!

MatthiasF · Nov 28th 2018

Does anybody else have a solution? Sean Farrell ?

Demian Gutberlet · Nov 29th 2018

MatthiasF , pardon for the delayed response. Be assured that your Web Standalone is forwarded to our developers for troubleshooting. I'll get back to you as soon as I have any further news.

hienngocloveyou · Mar 20th 2019

If you want to load your web standalone completely I have a right way, just change Material Selection : Graphics to Appearance.

But the material will not work correctly.

Regards,

narlee · Mar 22nd 2019

Web Standalone is fabulous, but when I try to export an interior view it puts me outside the structure. Is there a way so that when a client opens the standalone exported from an interior view that it opens in that view?

thx,

Geof Narlee

narlee · Mar 23rd 2019

k. seems to be working fine now...:)

And what's nice is that if I wander around, I can get back to the original view by "reloading" the page. Nice.

Sean Farrell · Mar 25th 2019

narlee If I am not entirely mistaken, the position you are in the moment the web-standalone is created will be the starting position. This is consistent with the normal standalone.

Wladi4444 · Jan 13th 2021

Hello,

I have the same issue and I am not he re just to put some more oil in the fire.

Since you already explained what the problem is and that its pretty much unsolvable, I can only give you an idea on how you can go around the problem (maybe)

So - In my opinion the exe standalone is perfect - I can send it to my colleagues and everything works fine!

However when I go to my professors for a discussion on the project I usually use my android tablet to show them my works.

So I can not open the exe file..

Then I use the web standalone.

Now I have this problem because I work on a much bigger project...

So my suggestion is: why not just make Enscape capable of exporting .apk standalone too ( like exe for android)

Then the need for web standalone ( wich obviously is limited by the browsers ) will be iliminated!

Let's not even mention that it will be much better for Enscape - You will have much less load on the servers!

I hope I see the apk feature in the future!

Ipads are also a big platform that people will like to be supported by the Enscape export system.

The hig-end tablet market is growing so fast and the users are mainly architects and interior designers!

Best Regards

Vladimir Mihaylov

Quote from Sean Farrell

What happens here is that the browser is running out of memory. This behavior is unfortunately unavoidable, since that depends on your device memory, the browsers security setting and many more factors. We are working hard to reduce the memory footprint of the web standalone, but this is a challenging thing to do.

In the meantime, what you do is either simplify your geometry, as AlexS mentioned and export subsections of the model.