Bug More WebGL problems. Only development build works, compressed files in wrong folder?

When I create a development build, my project just works. When I create a non-development build, I get an empty Compressed folder, a Release folder with all the .jsgz files and my project doesn't load. I've read it _should_ put the compressed files in the Compressed folder, and normal files (which don't appear) to Release folder. Is there some steps I'm missing to make the nondev-build work?

 

OK, I'm guessing I need to install apache to actually use those compressed files, amiright?

 

Any plans to change that? Sounds a bit much for people just starting to learn this stuff and wants to upload simple stuff they made.

 

I'm not sure if my webhotel I picked for this allows mod_rewrite in the .htaccess file, so I might be out of luck.

You can't seriously be ditching web player and moving to WebGL if we can't upload these things practically anywhere.

 

Don't generalize too much, the files should work on majority of web hosting places either out of the box with the provided file or with some manual customization. If you are restricted to do any of these then it's probably related the subscription plan you have selected from your host. However like Tak said, these discussions belong to WebGL section.

 

I've just checked here, and there really is a bug with WebGL non-development builds under Linux.
On Windows, it generates:

• Compressed folder - contains the compressed files
• Release folder - contains the uncompressed files
• TemplateData folder - generated if the chosen template was the default one
• index.html
• .htaccess

Meanwhile, the same project built on Linux generates:

• Compressed folder - empty
• Release folder - contains the compressed files
• TemplateData folder - generated if the chosen template was the default one
• index.html
• .htacess

The .htaccess content is the same for both builds:

Code (csharp):

1. Options +FollowSymLinks
2. RewriteEngine on
3.  
4. RewriteCond %{HTTP:Accept-encoding} gzip
5. RewriteRule (.*)Release(.*)\.js $1Compressed$2\.jsgz [L]
6. RewriteRule (.*)Release(.*)\.data $1Compressed$2\.datagz [L]
7. RewriteRule (.*)Release(.*)\.mem $1Compressed$2\.memgz [L]
8. RewriteRule (.*)Release(.*)\.unity3d $1Compressed$2\.unity3dgz [L]
9. AddEncoding gzip .jsgz
10. AddEncoding gzip .datagz
11. AddEncoding gzip .memgz
12. AddEncoding gzip .unity3dgz

As you can see, it won't work unless I modify it or move the compressed files to the correct folder (Compressed).
The problem is that some game-hosting sites does not accept the .htaccess file nor the compressed files (e.g Newgrounds), so I can't just upload there a WebGL build that was made on Linux.

 

My skill levels of Apache Conf Wizardry are quite low, but wouldn't you need the "AddEncoding gzip .jsgz" etc, inside the Release folder, for when it does a separate request for that folder? "RewriteRule" also allows Mime-Type as a flag, so:
RewriteRule (.*)Release(.*)\.unity3d $1Compressed$2\.unity3dgz [L,T=application/x-gzip]

Also, try "x-gzip" instead of gzip, could work for some older servers that don't have mod_deflate?

 

Compressed files are in the wrong folder for sure, but the release folder also misses some files.
Check this project https://github.com/suoko/rocketgame which correctly works (http://suoko.github.io/rocketgame/).
It has been produced with a windows build of unity.

So if you move the compressed files to the correct folder and add the missing files in the release folder, the game works.

 

I also got issues with webGL when building without the development option checked.

For me Unity messes up the file extensions and the content of the .js files inside the release folder are garbled and broken.

 

Can you try export this project ? https://github.com/noamgat/onebuttontorulethemall
Different projects could result in different export problems.
My result is:
- Compressed folder empty
- Release folder full of compressed files

My machine is a 15.10 with java 8

 

Tried to build, getting empty compressed folder, and the files in the release folder have wrong file extensions (.jsgz in stead of .js f.ex) and if i manually edit the file extensions the contents of the files are garbled.

 

It's not that the content is garbage, it's just that it is gzip compressed

 

No, it's not. No archive managers that I have can open them, and they have the same file names as the ones on the development build. Take UnityConfig.js for example, in the dev. build it a proper .js file, and the contents are readable. In the release build however, its named UnityConfig.jsgz and cannot be opened as an archive, and if you rename it back to .js and open it with a text editor, the contents are mangled.

 

Probably you did not, but maybe, maybe you have done this stupid thing like me.
All "Debug" class things seemed to be ignored in normal builds.
I had some codes like this:

int x;
Debug.Assert(int.TryParse("1",out x));​

where Debug.Assert will not be executed in normal builds, so my x never gets initialized.