Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Loading Screen Issues since 5.3

Discussion in 'WebGL' started by Matt_at_mindtrigger, Apr 6, 2016.

  1. Matt_at_mindtrigger

    Matt_at_mindtrigger

    Joined:
    Jan 20, 2014
    Posts:
    57
    Hi,

    our client's servers seem to produce an ugly issue with the loading screen since we've provided them with builds from unity 5.3 and higher (currently 5.3.3):

    Let's say our project takes something around 30 seconds to load, this is what happens:

    For the first 15-20 seconds the Loading Screen does not show. Instead the area just stays completely white (the shadows surrounding the rectangle do still show, so the user definately gets the feeling that "there's something wrong"). After that the screen pops up with the progress-bar being filled roughly 15% but the indicator will not move... it's just another "frozen" state further contributing to the feeling that "something's wrong". Another 10 seconds later it just jumps right into the project without any indication that loading has been completed.

    I am not familiar with the server architecture of our client but unlike our own webhosting (where everything works completely normal) they had to configure their server for (gzip-)compression for earlier versions (unity 5.2).

    Does anyone happen to be familiar with this Loading Screen issues? Our client has no idea what to do to fix this. Is there a solution to this?
     
  2. insmo

    insmo

    Joined:
    Apr 17, 2015
    Posts:
    12
  3. sirrus

    sirrus

    Joined:
    Jun 10, 2012
    Posts:
    250
    I believe the "frozen" state is due to the asm.js compilation which is a serious issue for us.