Cheers,
we are trying to track down problems users have when first starting our unity game (CHURRRRN).
Right now I am just looking at the time after the webplayer plugin has been installed (observeProgress - pluginStatus installed) and the first execution of ingame scripting (like Awake() or Start()). I came up with the following possible errors:
1) Updating the webplayer failed
This can be reproduced by disconnecting the internet when you see the progress bar.
2) The game file (webplayer.unity3d) cannot be downloaded
Well, just remove the file from your asset server.
3) User disrupts the process by Back / Cancel / Quit
4) Things like FlashBlock (Firefox) or turbo mode (Opera) block the plugin
Does anyone know about other errors that can occur?
Does anyone know how to be able to track them to find out what the main problem is?
Why aren’t there any callbacks for this in the unityobject2.js file?
Thanks a lot,
Jonas
