I am having a serious issue with the WWW module. I am using WWW to download a large ZIP file (1.01GB) containing updates to my game. While the download is going, I am attempting to use WWW.progress to display the download progress to the player, but WWW.progress stays at 0.0 until the download is completed and then changes to 1.0. I have been searching for a solution for days, and I could not find anything on the forums, and I really need some help.
The strange thing is that on small files (a few MB) WWW.progress works. But I can’t find any reference to the importance of file size to WWW.
You should check who posted the question and the answer…
That is only a crappy workaround I came up with for the problem…
Hey, this is a known issue that is currently being looked into by the QA team.
Any estimate for a solution?
I’m afraid not but I will post here again if there is any further news.
So… I shouldn’t hold my breath. Good to know. Now I can move on.
Hi FairGames,
The bug John just mentioned was the one I just dealt with: it turned out to not be a bug in Unity but rather a config problem with the server: the server was (for some reason) not sending the ‘Content-Length’ header, so Unity had no way of seeing how much of the file was left.
What (in the case I just looked it) was complicating the issue is that the web server seemed to be only not sending that header for iOS and Android, not PC (no idea why that would be the case, but we verified it several times!) and so it made it appear like it was a bug with the WWW class on iOS and Android.
Dave
Dave, I don’t think that’s the issue here.
I have 2 files. A test file and a large file. The test file is 1MB exactly and the large file is 1GB.
WWW.progress works great with the small files, but it doesn’t with the large ones. Both files are in the exact same place (google drive).
Could this really be an issue with Google?
Plus, this is on the PC, NOT Android or iOS…
There’s two directions you could go with this:
-
If you have a repro case, you could submit it to us using the Bug Reporter.
-
You could use something like a packet sniffer to try and intercept the data sent from the web server and see if the Content-Length header is there
It’s always possible that it’s a completely different issue.
I am working on web app , when i download an asset bundle(10 MB) the WWW.progress always stay 100%. Even my file was not downloaded it shows 100% right from the beginning.
It works fine on editor but in web it WWW.progress is not working correctly.
Any idea ?
when it loading data from cache than it display the progress correctly.
See this it may help you.