- Home /
WebPlayer Build
Hello all. The project I am working on is planned to be distributed as a webplayer. However, it is currently really large (90+ mb compressed). One of the issues is I still have all of my movies and sounds in there. I will soon move those to streaming and get them out of my build. When opening the build log, I saw that, uncompressed, my 'Levels' are 59.1% of the build, totaling 142 mb. From what I have gathered this is because of static batching.
Now that I have given you all of that information, here is my question. Should I pay attention to the uncompressed size, or just the compressed size when building a webplayer? Also, what is the max size I should shoot for when building a webplayer?
Thanks.
Answer by henry96 · Oct 05, 2011 at 01:15 PM
WOW!!! 142 mb, I didn't expect that at all. For web game, the size of the file is very important. And the file size needs to be as small as possible. Most players don't really want to wait for long for a game to load unless the game is so awesome. Usually, everything should be compressed so that it can reduce the file size. My idea is when your game is that big, you should also build it as the downloadable, so it gives the player to choice whether to play it online or they can download and play later smoothly without waiting for anything to load.
I really look forward to play your game. Good Luck!
Your answer
Follow this Question
Related Questions
Distribute terrain in zones 3 Answers
How to show an image while waiting for the game to finish loading 0 Answers
Chrome displaying new tab page instead of game 0 Answers
Web Browser Build, ask for Unity Web Player 1 Answer
Playerprefs issue in WebGL 0 Answers