Joined: May 28, 2015
Post Count: 607
Status:
Offline
Re: Export to HTML5 plug-in
Do you mean that you wonder if the 3D viewer would be able to generate such images or view existing images (like the sky texture but also with the other half on ground side)?
Yes I wonder if the online 3D viewer would be able to show the panorama from the images created in Sweet Home 3D (spherical lens). If there is a solution to see these panoramas directly in the 3D view of Sweet Home 3D with a fully spherical sky, why not?
----------------------------------------
EnkoNyito
United States
Joined: May 22, 2016
Post Count: 11
Status:
Offline
Re: Export to HTML5 plug-in
Is anyone having crashing issues? I'm using the Mac App Store version with the highly out of date plugin which I think is causing the crash. Every single time that I export to HTML, the freaking app crashes. Rebooting doesn't help. Renaming the file and opening doesn't do anything. I've GOT to get this exported for my shed builder for a custom quote. Any one know what I could do to keep this bloody thing from crashing? Crash report here: https://pastebin.com/bvYpLvWw
This must be due to sandbox restrictions in Mac App Store applications. I recently saw the same issue in the YafaRay plug-in where I programmed a different way to save a file. It should also work for the Export to HTML5 plug-in. I'll post an update soon.
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
Is there a way to force the "virtual Visit" as the default view (as opposed to the aerial view) ? Sorry if the information is already somewhere, i couldn't find anything.
Thanks for your help and big thanks to the creator of this plugin.
United States
Joined: May 22, 2016
Post Count: 11
Status:
Offline
Re: Export to HTML5 plug-in
Thank you for the reply and while that may be A SOLUTION it's not THE SOLUTION. I'm having the exact same issue for both versions; the MAS and the Open Source version. Now, I'm getting THIS bloody error and I'm about to pull my hair out. I need to get this plan to the construction crew!!!!
PS - And before y'all go blasting me about this being open source software and freely downloadable and I shouldn't get irritated, well, I donate regularly and have purchased the MAS version in an effort to help the project and I really need this software to work as expected.
Switzerland
Joined: Aug 31, 2017
Post Count: 421
Status:
Offline
Re: Export to HTML5 plug-in
PS - And before y'all go blasting me about this being open source software and freely downloadable and I shouldn't get irritated, well, I donate regularly and have purchased the MAS version in an effort to help the project and I really need this software to work as expected.
And if you donate today to the WHO, tomorrow we all have the vaccine against corona...
I can understand you, such problems are annoying. But if it were that easy, you wouldn't have the problem at all.
----------------------------------------
Pascal
United States
Joined: May 22, 2016
Post Count: 11
Status:
Offline
Re: Export to HTML5 plug-in
And if you donate today to the WHO, tomorrow we all have the vaccine against corona...
I can understand you, such problems are annoying. But if it were that easy, you wouldn't have the problem at all.
And if you donate today to the WHO, tomorrow we all have the vaccine against corona...
I can understand you, such problems are annoying. But if it were that easy, you wouldn't have the problem at all.
That's hardly the same analogy; one is a worldwide pandemic that no one outside the Chinese saw coming and the other is a bloody app that CAN BE and SHOULD HAVE been fixed years ago. That many people have PAID FOR via the Mac App Store and have lived with the "known issues" way longer than they should have. An update to this plugin hasn't happened in three freaking years! It should have baked it into the software years ago but for some unbeknownst reason the dev refuses to do so.
I don't use this software to just play with like a lot of the people here. I'm using it professionally and like any other professional app I use, I pay for it. When something is paid for, it's a reasonable expectation that bugs will be fixed in a fair amount of time. Three years without an update to a plug-in that's had many reported issues is not reasonable. To blame it on Apple's App Store for their restrictions isn't reasonable either because the dev(s) submitted SH3D KNOWING the limitation(s) FULL WELL going in. To say, "Hey, use this library/plugin/et al instead..." is just out-and-out laziness. FIX the bloody thing! It's not an unreasonable expectation and it's LONG past overdue.
France
Joined: Nov 7, 2005
Post Count: 9430
Status:
Offline
Re: Export to HTML5 plug-in
Please, let’s calm down.
Kelleychambers, the version 1.4 of the plug-in was released 17 months ago and certainly not 3 years ago. If you could explain why in a professional use, you prefer to use the plug-in rather than your SH3D files with Sweet Home 3D JS viewer, maybe I could learn something interesting. By the way, the bug you encountered happens only with the sandboxed version of the Mac App Store from macOS 10.14. Using the free version is an other way to circumvent this issue. Once again, don’t blame me if Apple decides to make it more and more difficult for developers at each release of their system.
@rrraf If you want by default the virtual visit, simply export your file while you’re in virtual visit mode.
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
France
Joined: Nov 7, 2005
Post Count: 9430
Status:
Offline
Re: Export to HTML5 plug-in
I released the version 1.5 of Export to HTML5 plug-in to include features and fixes which appeared in Sweet Home 3D JS version 6.1 and 6.3. It includes also a bug fix that prevents crashes under macOS 10.14+ when the plug-in is used with the sandboxed version distributed in the Mac App Store. In that environment, the only places where you'll be able to save the generated file are the /Users/user/Library/Containers/com.eteks.sweethome3d.SweetHome3D/Data and /Users/user/Library/Containers/com.eteks.sweethome3d.SweetHome3D/Data/Documents folders (where user is your login). You may create and use the subfolders of your choice in the folder Documents too, but it won't work anywhere else. It's probably a limitation that Apple decided to add to protect users from plug-ins distributed outside of the Mac App Store and uncontrolled by its services.
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
