32-bit Windows OS is a stopper for Unity WebGL. Not just a Chrome.

We have analyzed our three different games that are played in production world-wide. The result is pretty similar for all of them. Usually, Chrome is declared guilty. However, It is just because it is more popular than FireFox. However, even the same FireFox that works well on Win64, has a high failed rate if Win32 is used.

We have gathered a tone of real user browser logs. What we can see there: Internet speed does not mater, memory size does not mater. If user comp downloads the game in 10 secs and a allocates 512Mb memory, it will failed on Win32.

I have attached the screenshot. The latest 2000 attempts for Chrome, FireFox and Edge are analyzed.
WOW64 is a 64-bits. We did not include the cases when users drop the connecting before all files are dowloaded.

Edge is a special case. Windows do not turn on using asm.js by default. As a result, Edge works extremely slow. If the flag is turned on, Edge works perfect.

The most critical moment is processing and executing the main game js file. In most cases the log is ended at this point.

Win64 Chrome always hanged up for 5 secs during the main game js file processing (asm.js issue). FireFox has no delay for this moment.

 

It is a table for one particular game. I have attached other two also.

Column 1 (green): players start to play game successfully.
Column 2 (yellow): player loaded the game (the scene started, but initialization code is failed for some reason).
Column 3 (red): player loaded all game files, but Unity Loader is loader is failed. Scene is not started.
Column 4 is just a visual representation for column 1-3.
Column 5: browser for those numbers.

 

Very nice info, thanks for sharing. If its not too much asking, what does it give as an overall drop rate of player trying to play the game?

 

>what does it give as an overall drop rate of player trying to play the game?

It depends of the region and the size of the game. I have attached one more screenshot from our proprietary game monitoring tool. Those are 50 latest attempts. All players are unique.

green lines - player started to play successfully.
yellow lines - the scene started, but player did not start a level for some reason.
red lines - player downloaded the game, but unity loader was failed to start or scene did not loaded.
grey lines - player close browser tab before all game files are download (usually, slow internet)

1 column - time for unity loader is done (100% of the progress bar)
2 column - scene is started (Awake is called on the scene)
3 column - start menu is shown.

Size: Compressed folder is about 8Mb, Assets Bundle - 11Mb. It is a game on Facebook, mostly women after 40, mostly US traffic.

So, we have about 35% success rate for those latest 50 players. Sometimes, it is up to 45%. I.e. our drop rate is 60%.
We checked a traffic from South America. 32bits are dominated there. 20% for success is a lucky moment. Drop rate is 80% and up.

 

Hi support, would you consider making this proprietary code available for monitoring such things? Either free or paid?

 

I know our company would absolutely love to have something like this! Even just getting loading failure rates with that information in a centralized place would be huge!