I have just updated to version 2.9.2. I found that lzip.getTotalFiles returns the same value as lzip.getTotalEntries. Both includes the folder counts. I compared the codes, both are identical. It looks like a bug.
Per the document in the code, getTotalFiles should only return the file counts, excluding the folder counts right?
Iām running into the same issue. I imported the plugin into a Unity2021 project, and Webgl wonāt compile. Thereās no .a file extension files in the webGL plugins folder; only .bc. I tried making a brand new 2021 project to try and see if it imported well, but it didnāt work. Same compile error as that guy.
WebGL/zipw.bc: machine type must be wasm32 or wasm64
Last time I checked Unity supposed to download the asset according to unity version. It seems something does not work right in this scope.
I will send you a private message with the .a WebGL plugins.
(I will include these also in every version update from now on.)
Hi there, we bought the plugin today for our unity game launcher, which downloads zipped game build from our internet site and should decompress it in the background on the client/local machine. However, the launcher gets absolutely stuck in the āapplication not respondingā during the local decompression process. Any ideas, what is causing the launcher app to freeze during the decompression and how to solve it?
Once the decompression is finished, the launcher application de-freezes and functions properly. It does not do this freezing sh*t when decompressing smaller files (round 500MB), but does it in your build case (round 4GB of compressed file size).
Been using this for a while on OSX and iOS without issue, but recently using it in my Windows x64 project (not UWP and not even doing a x86 build). However, I keep getting DllNotFoundException in the Editor when I try to start the project. On Windows 11, first Unity project in Windows, and Iāve double checked that zip\Plugins\x86_64 is only enabled for x64.
Other plugins like FMOD are ok, so I am puzzled and out of ideas. I checked permissions and everyone had read and execute permission.
Thanks!
UPDATE:
Ok, so the .dll in question was pulled from a git repo. To troubleshoot, I installed zip from the Package Manager (on top of what I had which was all the same / latest version), and the DLL loaded. I check git and it shows the ānewā DLL and corresponding .meta was unchanged (as expected). I then delete them both and then reload it from my git repoā¦and it works?
Any ideas on what is going on? Perhaps there is a flag (in Windows or the project) that was affected when I reinstalled from the Package Manager. I donāt like mysteries like these.