I see. Thanks for the insight.
No need to download. Just export, change the extension from ZPP to ZIP, and double click.
That’s an interesting response from Zappar support, since for me, it’s the user experience that matters most. I’m using WebAR, so download time is critical, and as it stands, the “final download size” provided by Studio is wildly inaccurate. In fact, I really feel like I’ve been duped.
I did some tinkering this weekend while exploring an automated solution for optimizing Zappar project files, and I made a puzzling discovery. If I export a project, unzip it, zip it back up without modifying anything, and then try to import it, Zappar doesn’t recognize it as a valid project file.
There seems to be something special about the way the project folder is compressed. @George, can you or anyone at Zappar shed any light on this?
Ideally, I’d like to export a project, optimize it, and then re-import it without messing around in the hidden projects folder.
You are making it too complicated. I told you to just duplicate folder. Any folder in the .zapparstudio folder will show up as a project to load. So duplicate the folder and it is the same as exporting and importing it.
Yes, it will show up, but it won’t necessarily load.
No, it is not the same. For one thing, an exported project does not have a “models” folder containing the 3D assets in their native format.
And yes, I saw and understood your recommendation. As I said, I’m looking to go about it a slightly different way. It might not be possible, but I’m still exploring. I’ll just start a new thread if I have further thoughts to share. Didn’t mean to hijack yours.
Apologies for the inconvenience this has caused for the both of you.
We’ve been able to push an update yesterday to the ZapWorks CLI; a ZPP cleaner.
It’s part of our ZapWorks command-line tools. You can find documentation on the tool here. Once you have the tool installed following the ‘Getting Started’ section in the article, you can run the following command in your terminal:
zapworks zppclean MyProject.zpp
It will then produce a cleaned version of your project, called MyProject_cleaned.zpp. This will help remove any unnecessary hidden files and commit history from your project, however, this does not perform any optimizations to your project, of which you’ll best be served by reading our ‘Optimizing your experience’ article here.
We’re working on documenting this tool within the next couple of weeks to help both you and other users with this issue.
We hope this helps you, and please get in touch with support if you have any urgent issues.
Clean your project before publishing!
Hey @Bob, can you clarify something? Must the project reside in the official hidden Zappar folder, or can the project name supplied as a command line argument be the path to an exported ZPP file?
EDIT: I just tried this out, and it works great on an exported ZPP project file. The resulting ZPP file is still twice the “download size” that Studio reports, but it’s less than 1/3 the pre-cleaned size.