Problem with Webplayer and NGUI on hosting server

Unity Engine
1

Hi everybody,

I’ve been searching for this problem in the forum but all I found was people complaining that they couldn’t play some specific games.

let me try and explain the crazy stuff that’s going on.

I’m developing an applicaiton for webplayer and when I execute it locally it runs smoothly. But when I send it to the server I cannot even load it and Unity gives the following error: “Error launching Unity Player” and on “Error details” it says “Invalid Unity Web File (Decompression Failure)”. It’s not just a matter of corrupted files cause I uploaded it and many other projects and tests scenes at least 15 times and got the same error. I also tested it on another computer and the same happened. See the following picture for more details of the error:

1303360--60710--$errorUnity.jpg

Then I went and created a new empty project with just a single Unity Gui Texture, uploaded to the server and was able to load the game properly. This clears out the hypothesis that the server could be the one with problems.

After doing some deleting and checking I’ve discovered that just by importing the NGUI package, the error returned, even with the simple scene I described earlier (a scene with just a simple unity gui texture).

I cannot grasp what is going on, because I find hard to believe that the second top rated app on asset store (as of today) would be responsible for causing this error. Has anyone ever gone through that or something similar? Do I need to change any of the build settings to use NGUI on the webplayer?

Thanks a lot!
Caspila

2

Try this:

  1. compute the md5 hash of the unity3d file when it’s sat on your hard drive after the build completes.
  2. upload the unity3d file to your server. Then compute the md5 hash of the unity3d file.
  3. use a web browser and download the unity3d file to your hard drive. Then compute the md5 hash of the unity3d file.

Compare the md5 hashes. They should, of course, be identical. If the hash from (2) is different from (1) then the problem is in your upload to the server. If, instead, the md5 at (3) is different from that at (1) then the problem is in the web server configuration. If computing md5 hashes is hard for you, then just check the file size of the unity3d file at these locations.

3

Thanks Graham, that’s indeed a great idea!

I only have access to the application on commercial days so I’ll be checking it tomorrow. I’ll post as soon as I do the checkings or find something new.

4

Oh gee, I’ve gotta be embaressed after this one… The problem had nothing to do with NGUI or Unity.

I computed the md5 like Graham sugested and (1.) differed from (3.). After a few moments I realized that I was uploading the file to the server using Text Mode. Therefore, the .html was fine but the .unity3d was “corrupted”.

For any1 that has a problem similar to this I suggest 1st checking the md5 and then paying attention to the upload mode: upload the .html in text mode and the .unity3d in binary mode.

This problem can now be marked as solved.
Thanks.