I have the 5.1 version and a 5.3 version built. Yes, I do have a working 5.1 build and for comparison's sake I put both on a brand new Ubuntu VM running Apache 2.4.18. This is in stark contrast to how it worked prior to 5.3. In plain English, the progress bar does not update during download and when it does update, it happens very fast. Finally, "Running." is displayed via SetMessage and then after a second or so the scene is loaded. data file is loaded and a similar process happens, but this time SetProgress is called with values from 0 to ~0.93 and this all happens within about 50 ms, so the progress bar goes from 0 to 93% very fast - blink and you'll miss it. These all happen within 80ms so you don't even see this. SetMessage is called ~13 times but also SetProgress(0) is called. Once downloads are complete, the message "All downloads complete" is very briefly displayed (along with progress being set to 0), and then "Preparing. SetProgress is never called during the download process, so the progress bar would not be doing anything during this time. I added more console.log statements to confirm my suspicions:Īt the start of the script when the progress bar is created, the first message is "Downloading 0.0/1". However, the loading bar is again not working. The server is matching these and passing back the gz version along with the correct content-encoding header, and just as before the scene loads and works as intended. What changed from 5.1 to cause this? How can we work around this problem? At the very least it would be useful for the progress bar to be updated as files are downloaded, especially for those with slower connections. The result is that the progress bar is only visible for a brief moment just before the scene is ready. Once the files are downloaded there are calls to SetProgress, but they all happen very quickly and my guess is that the main thread is so busy loading data into memory that the progress bar is not actually redrawn until everything is done. When the files start downloading it displays "Downloading 0.0/1", but this is never updated. From my observations it does not look like the progress bar or message is updated during file downloads at all. I've put in console.log statements in various places within the progress script to try to see exactly when the bar is updated. the scene does work as expected once everything is loaded the UnityLoader script is not complaining about having to do client side decompression the server is sending these files with the appropriate gzip encoding header the paths to the dataUrl, memUrl, and codeUrl values are directly to the *gz files I'm using nginx instead of Apache, but the compressed files are being served as expected: I'm sorry to hijack an old thread, but I'm having the same problem with the progress bar not updating smoothly in 5.3 like it did in 5.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |