a few questions regarding the latest version of the web-player installed on a users machine and the update procedure:
a) Is there somekind of check and notification that there is a newer plugin around and is this working for both OSs? Silent update?
b) What’s happeining if i try to watch content which was done with a newer version of Unity? Do i then get a notification, a silent update or does it just try to run as best as it can?
I remember that i tried out some 1.5.1 compiled content on windows without installing a 1.5.1 plugin (if there is some). Beside of that the colours weren’t the same on OSX and windows i didn’t notice any update…
All updates are silent. The updates happen in two cases: a) the content you’re trying to view requires a newer version than the one you have or b) we force installed web players to auto-update upon first use, in the case we have serious fixes (like 1.5 → 1.5.1).
Another issue beside of the colours is that i badly miss information about which version is installed on a users machine. Could you please update this for both platforms with the next version?!
With “Help/Installed PlugIns” i do get that i have unity but no word about which version is beeing installed which is pretty important for dealing with user issues.
a) the content you’re trying to view requires a newer version than the one you have
<<<
So i click on a new content. Is the information about which version the content has been generated written in the html-file or is it in the content itself?
What if the html-file has the wrong information?
Do i have to load the content first, then it get’s checked, downloading the new player, starting the content?
How are the concrete steps?
b) we force installed web players to auto-update upon first use, in the case we have serious fixes (like 1.5 → 1.5.1).
<<<
The plugin version required is stored in the data file. We start downloading the plugin updates as soon as we receive the required version from the downloading data file.
Auto-updates: the plugin checks our server like “I’m plugin version XYZ, do I need to update”. It then either updates from our server or does nothing if no update is required (or the version check request timed out).
The plugin version required is stored in the data file. We start downloading the plugin updates as soon as we receive the required version from the downloading data file.
<<<
So do you need to download the whole unityweb-file first or is it sufficient to stream just a part of it? After the update is done does the content has to be downloaded again?
Auto-updates: the plugin checks our server like “I’m plugin version XYZ, do I need to update”. It then either updates from our server or does nothing if no update is required (or the version check request timed out).
<<<
So this happens only once after i’ve installed the plugin and the browser is online?
The content is only downloaded once. At the moment we need to download the whole data file to get the version, but that’s an implementation detail that can change anytime in the future.
It happens only when Unity plugin is actually loaded. So if you install it and never browse any Unity content it won’t get updated.
The content is only downloaded once. At the moment we need to download the whole data file to get the version, but that’s an implementation detail that can change anytime in the future.
<<<
Which means as soon as we get streaming this will be enhanced too.
It happens only when Unity plugin is actually loaded. So if you install it and never browse any Unity content it won’t get updated.
<<<
Now i’m confused again…
What comes first the auto update or the update due to the content?
If i click on a *.unityweb file is first the server checked for an auto update (before loading the content) or will the content be loaded first and if needed the player will be updated then or if the content’s version is okay then be looked after the auto update?
Or is this happening parallel in order to pass the server timeout while downloading the content?
When some unityweb player content file is loaded for the first time, the server is asked if an forced update is required (eg. because of a security fix) and the data file is downloaded. Those two downloads are done in paralell.
If the autoupdate check some how fails (eg. you are not connected to the net and you load a web player from the harddrive) then there is a 3 second timeout period after which the force update check will simply be disabled and unity uses only the version information from the unityweb data file.
If you have a web player data file which requires a version of the Unity Web Player that is greater than the one you have installed and downloading the autoupdate fails. Eg. because you are offline. Then the web player will give you an error saying that the auto update failed.
So usually you can just completely forget about all the above, the essence is, if a user has an older version of the unity web player installed and the data file requires a newer one, the plugin will automatically update itself.