C# Program Runs Fine in Editor, But Webplayer Build Has Issues

Unity Engine
1

And boy, what issues it has :stuck_out_tongue: Firstly, the webplayer is set to render in 1024x768, the same dimensions as in the editor. The “How to Play” page is blurry, but it’s crisp in the editor. Both music tracks I use play in the editor but are absent in the webplayer build as are the other sound effects excepting the one that’s on a prefab. Also, the number keys across the top of the keyboard (1 - 4 in my case) don’t work, although the a,d, and arrow keys work fine. Been looking for a couple of hours and can find no explanation for this behavior. Any thoughts?

2

Okay, it gets weirder. Changing the spawn frequency value does NOTHING in the webplayer. It’s consistently spawning at 5 seconds, while in the editor it’s set to 10 seconds and waits 10 seconds. Did I miss a setting somewhere or does the 4.1 Webplayer have some serious problems?

3

Making no headway on this. I noticed the one that was working was an mp3, so converted on of the OGGs to an mp3. Still doesn’t work. Still no clue why the timing of the piece entry changes between stand alone and web player.

EDIT: This is a far bigger problem than I originally thought. I just ran the Windows version I built, and all the problems are in that too. For some reason it’s not properly exporting most of my project whether it’s to Windows or the Webplayer. What the heck is going on?

4

Have you tried putting the sound files in the “Resources” folder? Unity attempts to intelligently figure out what assets you’re actually using in your project and will package those up with your build. Sometimes it does make mistakes and forgets certain files though. Anything in the “Resources” folder will automatically get included with your build regardless of weather or not Unity thinks it’s being used in your project.

5

As for your blurry “How to play” page, have you checked the web player settings for the images you’re using on that page? It could be that your webplayer settings for those assets have some crazy compression enabled.

6

Thanks for the ideas, but just figured out the problem, and man what a stupid mistake. Somehow, I had created a new scene and that’s what all the changes were being made to. In the meantime, the build settings were still using the old scene :shock: No wonder nothing worked as expected.