Search Unity

5.0.0f4 issues - memory and compression

Discussion in 'Web' started by michela, Mar 5, 2015.

  1. michela

    michela

    Joined:
    Feb 15, 2009
    Posts:
    35
    The 5.0.0f4 build is publishing a different file structure (Development, TemplateData folders) and no longer generating compressed files.

    On a build with lots of textures, I'm now unable to use Fast builds (emscriptem now runs out of memory) and even on Slow, the resulting build does not work in either Firefox or Chrome.

    Any documentation updates on this? Texture memory constraints?

    Michela
     
    michela, Mar 5, 2015
    #1

  2. ShabihDesperado

    ShabihDesperado

    Joined:
    Oct 27, 2013
    Posts:
    41
    ShabihDesperado, Mar 5, 2015
    #2

  3. lami

    lami

    Joined:
    Jun 17, 2013
    Posts:
    17
    What I remember compressed files are just generated if you uncheck development build in the build settings.
     
    lami, Mar 5, 2015
    #3

  4. jonas-echterhoff

    jonas-echterhoff

    Unity Technologies

    Joined:
    Aug 18, 2005
    Posts:
    1,666
    Yes, we stopped generating compressed files for development builds to speed up iteration times.

    As for emscripten running out of memory in fastest settings, that is a bug in emscripten handling very large functions. It is fixed in latest emscripten, so once we update to that, this will be fixed. It should only affect "Fastest", not "Fast" (which is only slightly slower, really), or "Slow" settings.

    As for the resulting build not working, how does it fail?
     
    jonas-echterhoff, Mar 9, 2015
    #4

  5. michela

    michela

    Joined:
    Feb 15, 2009
    Posts:
    35
    On "Fast" my webgl build is now only playing in Chrome via http (never worked via file url). Via http or file url Firefox crashes without specific error after project loads (webgl loader runs). Firefox was able to play build from b22 ok via http or file. Using latest browser releases.

    I've got a large texture Resources cache in my project which has been growing steadily but would expect unoptimised version to still run. Or are there constraints on overall webgl project size?

    Michela
     
    michela, Mar 11, 2015
    #5

  6. jonas-echterhoff

    jonas-echterhoff

    Unity Technologies

    Joined:
    Aug 18, 2005
    Posts:
    1,666
    Chrome not working via file urls is expected (http://docs.unity3d.com/Manual/webgl-building.html):

    "To view your WebGL content you can open the index.html file in Firefox. Note that other browsers may require you to host the file on a local http server due to access restrictions on file:// urls. The Build & Run button will do that for you, it will spawn a local web server hosting the content, and open it in your default brower."

    As for the crash you are seeing in Firefox, please report a bug.
     
    jonas-echterhoff, Mar 12, 2015
    #6