Why is Unity 2018.2 WebAssembly loading intervals only 0%, 90%, 100%
up vote
2
down vote
favorite
Ever since switching to Unity 2018 the loader is really chunky and not helpful. On old builds of my product the loader would smoothly climb to 100%. Now with my Unity 2018.2 builds, It skips from 0 to 90 to 100 and finishes. It stays on 90 for pretty much the whole time. My users are thinking my product is broken because it no longer loads smoothly. They think it's stuck. Ive debugged the UnityLoader.js file and have verified that the progress only gets called once and reads .9 before loading all the way:
function UnityProgress(gameInstance, progress)
console.log("PROGRESS")
console.log(progress)
...
This prints out only 0, 0.9. Then the game loads successfully. No intermediate 0.1, 0.2 etc.. like it used to
Anyone know how to fix this? Is this happening to everyone?
Cheers, Ming
EDIt
This only happens on my project, not an empty project. It seems like it is in the Unity Loading process though, before any of my code is touched, not sure how my code could mess up the loading frequency of Unity's WebGL App progress updates
javascript unity3d loading webassembly unity-webgl
asked Nov 9 at 20:24
MingMan
7421819
add a comment |
up vote
2
down vote
favorite
Ever since switching to Unity 2018 the loader is really chunky and not helpful. On old builds of my product the loader would smoothly climb to 100%. Now with my Unity 2018.2 builds, It skips from 0 to 90 to 100 and finishes. It stays on 90 for pretty much the whole time. My users are thinking my product is broken because it no longer loads smoothly. They think it's stuck. Ive debugged the UnityLoader.js file and have verified that the progress only gets called once and reads .9 before loading all the way:
function UnityProgress(gameInstance, progress)
console.log("PROGRESS")
console.log(progress)
...
This prints out only 0, 0.9. Then the game loads successfully. No intermediate 0.1, 0.2 etc.. like it used to
Anyone know how to fix this? Is this happening to everyone?
Cheers, Ming
EDIt
This only happens on my project, not an empty project. It seems like it is in the Unity Loading process though, before any of my code is touched, not sure how my code could mess up the loading frequency of Unity's WebGL App progress updates
javascript unity3d loading webassembly unity-webgl
asked Nov 9 at 20:24
MingMan
7421819
I am currently using Unity 2018.2.14f1 and don't have the problem with WebAssembly Builds. Did you try a Build with a clean project? Or can you reproduce the problem with your project only? We are working with our project since Unity 2017.2.4 and switched from asm.js to WebAssembly with Unity 2018.2.4
– dome12b
yesterday
Interesting, it did not happen with a clean project. The loading percent hit other percents besides 0, 90 and 100. Any idea where to start looking into a project specific problem like this? This was not an issue for older versions of Unity on this project
– MingMan
yesterday
That is really difficult without knowing the project. I don't know much about the loading process, but you can try the following: make a new scene in you project and set it as first scene. In the scene attach a script withSceneManager.LoadSceneAsync(SCENE_TO_LOAD, LoadSceneMode.Additive);to load your real first scene after the empty scene. Perhaps Unity is loading the first scene async while starting the engine and in your case it is blocking the progress?
– dome12b
20 hours ago
I took that suggestion and no change. Very peculiar.
– MingMan
11 hours ago
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Ever since switching to Unity 2018 the loader is really chunky and not helpful. On old builds of my product the loader would smoothly climb to 100%. Now with my Unity 2018.2 builds, It skips from 0 to 90 to 100 and finishes. It stays on 90 for pretty much the whole time. My users are thinking my product is broken because it no longer loads smoothly. They think it's stuck. Ive debugged the UnityLoader.js file and have verified that the progress only gets called once and reads .9 before loading all the way:
function UnityProgress(gameInstance, progress)
console.log("PROGRESS")
console.log(progress)
...
This prints out only 0, 0.9. Then the game loads successfully. No intermediate 0.1, 0.2 etc.. like it used to
Anyone know how to fix this? Is this happening to everyone?
Cheers, Ming
EDIt
This only happens on my project, not an empty project. It seems like it is in the Unity Loading process though, before any of my code is touched, not sure how my code could mess up the loading frequency of Unity's WebGL App progress updates
javascript unity3d loading webassembly unity-webgl
asked Nov 9 at 20:24
MingMan
7421819
Ever since switching to Unity 2018 the loader is really chunky and not helpful. On old builds of my product the loader would smoothly climb to 100%. Now with my Unity 2018.2 builds, It skips from 0 to 90 to 100 and finishes. It stays on 90 for pretty much the whole time. My users are thinking my product is broken because it no longer loads smoothly. They think it's stuck. Ive debugged the UnityLoader.js file and have verified that the progress only gets called once and reads .9 before loading all the way:
function UnityProgress(gameInstance, progress)
console.log("PROGRESS")
console.log(progress)
...
This prints out only 0, 0.9. Then the game loads successfully. No intermediate 0.1, 0.2 etc.. like it used to
Anyone know how to fix this? Is this happening to everyone?
Cheers, Ming
EDIt
This only happens on my project, not an empty project. It seems like it is in the Unity Loading process though, before any of my code is touched, not sure how my code could mess up the loading frequency of Unity's WebGL App progress updates
javascript unity3d loading webassembly unity-webgl
javascript unity3d loading webassembly unity-webgl
asked Nov 9 at 20:24
MingMan
7421819
asked Nov 9 at 20:24
MingMan
7421819
edited 11 hours ago
asked Nov 9 at 20:24
MingMan
7421819
asked Nov 9 at 20:24
MingMan
7421819
asked Nov 9 at 20:24
MingMan
7421819
7421819
I am currently using Unity 2018.2.14f1 and don't have the problem with WebAssembly Builds. Did you try a Build with a clean project? Or can you reproduce the problem with your project only? We are working with our project since Unity 2017.2.4 and switched from asm.js to WebAssembly with Unity 2018.2.4
– dome12b
yesterday
Interesting, it did not happen with a clean project. The loading percent hit other percents besides 0, 90 and 100. Any idea where to start looking into a project specific problem like this? This was not an issue for older versions of Unity on this project
– MingMan
yesterday
That is really difficult without knowing the project. I don't know much about the loading process, but you can try the following: make a new scene in you project and set it as first scene. In the scene attach a script withSceneManager.LoadSceneAsync(SCENE_TO_LOAD, LoadSceneMode.Additive);to load your real first scene after the empty scene. Perhaps Unity is loading the first scene async while starting the engine and in your case it is blocking the progress?
– dome12b
20 hours ago
I took that suggestion and no change. Very peculiar.
– MingMan
11 hours ago
add a comment |
I am currently using Unity 2018.2.14f1 and don't have the problem with WebAssembly Builds. Did you try a Build with a clean project? Or can you reproduce the problem with your project only? We are working with our project since Unity 2017.2.4 and switched from asm.js to WebAssembly with Unity 2018.2.4
– dome12b
yesterday
Interesting, it did not happen with a clean project. The loading percent hit other percents besides 0, 90 and 100. Any idea where to start looking into a project specific problem like this? This was not an issue for older versions of Unity on this project
– MingMan
yesterday
That is really difficult without knowing the project. I don't know much about the loading process, but you can try the following: make a new scene in you project and set it as first scene. In the scene attach a script withSceneManager.LoadSceneAsync(SCENE_TO_LOAD, LoadSceneMode.Additive);to load your real first scene after the empty scene. Perhaps Unity is loading the first scene async while starting the engine and in your case it is blocking the progress?
– dome12b
20 hours ago
I took that suggestion and no change. Very peculiar.
– MingMan
11 hours ago
I am currently using Unity 2018.2.14f1 and don't have the problem with WebAssembly Builds. Did you try a Build with a clean project? Or can you reproduce the problem with your project only? We are working with our project since Unity 2017.2.4 and switched from asm.js to WebAssembly with Unity 2018.2.4
– dome12b
yesterday
I am currently using Unity 2018.2.14f1 and don't have the problem with WebAssembly Builds. Did you try a Build with a clean project? Or can you reproduce the problem with your project only? We are working with our project since Unity 2017.2.4 and switched from asm.js to WebAssembly with Unity 2018.2.4
– dome12b
yesterday
Interesting, it did not happen with a clean project. The loading percent hit other percents besides 0, 90 and 100. Any idea where to start looking into a project specific problem like this? This was not an issue for older versions of Unity on this project
– MingMan
yesterday
Interesting, it did not happen with a clean project. The loading percent hit other percents besides 0, 90 and 100. Any idea where to start looking into a project specific problem like this? This was not an issue for older versions of Unity on this project
– MingMan
yesterday
That is really difficult without knowing the project. I don't know much about the loading process, but you can try the following: make a new scene in you project and set it as first scene. In the scene attach a script with
SceneManager.LoadSceneAsync(SCENE_TO_LOAD, LoadSceneMode.Additive); to load your real first scene after the empty scene. Perhaps Unity is loading the first scene async while starting the engine and in your case it is blocking the progress?– dome12b
20 hours ago
That is really difficult without knowing the project. I don't know much about the loading process, but you can try the following: make a new scene in you project and set it as first scene. In the scene attach a script with
SceneManager.LoadSceneAsync(SCENE_TO_LOAD, LoadSceneMode.Additive); to load your real first scene after the empty scene. Perhaps Unity is loading the first scene async while starting the engine and in your case it is blocking the progress?– dome12b
20 hours ago
I took that suggestion and no change. Very peculiar.
– MingMan
11 hours ago
I took that suggestion and no change. Very peculiar.
– MingMan
11 hours ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53232812%2fwhy-is-unity-2018-2-webassembly-loading-intervals-only-0-90-100%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I am currently using Unity 2018.2.14f1 and don't have the problem with WebAssembly Builds. Did you try a Build with a clean project? Or can you reproduce the problem with your project only? We are working with our project since Unity 2017.2.4 and switched from asm.js to WebAssembly with Unity 2018.2.4
– dome12b
yesterday
Interesting, it did not happen with a clean project. The loading percent hit other percents besides 0, 90 and 100. Any idea where to start looking into a project specific problem like this? This was not an issue for older versions of Unity on this project
– MingMan
yesterday
That is really difficult without knowing the project. I don't know much about the loading process, but you can try the following: make a new scene in you project and set it as first scene. In the scene attach a script with
SceneManager.LoadSceneAsync(SCENE_TO_LOAD, LoadSceneMode.Additive);to load your real first scene after the empty scene. Perhaps Unity is loading the first scene async while starting the engine and in your case it is blocking the progress?– dome12b
20 hours ago
I took that suggestion and no change. Very peculiar.
– MingMan
11 hours ago