as we see, the Webplayer plugin needs to have Internet connection on startup (to check if updates are awailable), even if we deploy our projects as offline builds. Is there a solution to avoid this, cause it doesn´t make much sense? Our target sistems may not have Internet connection…
We found a solution for now (source). You have to disable Unity Webplayer checking for updates in the environment variables (“UNITY_DISABLE_PLUGIN_UPDATES = yes”).
So, the webplayer has 3 parts, the plugin, the player, and the mono runtime. When the user views a web site with Unity content, the plugin is fetched and installed using the UnityObject2.js code. Then the data is fetched, and looked at to decide which player and mono to use. These items are then fetched. So, if the user is not connected to the internet, then the player and mono will not be accessible, and the message “Failed to update Unity Web Player” will be displayed. This is the expected behaviour since it’s a condition of use that the webplayer is served from the Unity web site.
To solve your problem, visit each machine, connect to the internet and install the plugin from the command line using the /AllUsers commandline switch. Do this as admin. View some online content, let the plugin fetch and install the player and mono, and then your users should be able to play back Unity content without being connected to the internet. (Or purchase a license that allows you to install the webplayer on closed networks.)
For the record, the offline build simply makes an html file that references a local copy of UnityObject2.js.
I think as Unity gets used more and more in serious games then the ability to allow IT departments to install the webplayer over their network is going to come up more frequently. Several people have this issue if you google around.
Our client base is UK universities and we are blocked with some of the largest because the 1000s of PCs they manage are locked down (students!) so users can’t install browser plugins, but there is no way of remotely installing the webplayer (at least as far as we can find).
We have a product that solves this. You can purchase from Unity a license and an installer that allows you to install Unity WebPlayer on machines that are not connected to the internet, and the plugin doesn’t expect to reach out for updates. At Unity 3.x this was called the “full” installer. With 4.x that was removed, and replaced with our military/simulation product.
However, we are working with academic, not miltiary clients, so that price point is prohibitive especially as the only thing we would want from the bundle is the webplayer installer. We do use SCORM but upgraded the free ADL SCORM Unity3 beta to work with Unity4 ourselves.
hi any updates on this? It kinda blows, something our team thought should come free is now a separate paid product. Btw we have pro license, do we have to purchase this “offline web player” separately? It doesn’t make any sense… any we have deadline looming.
I too am having an issue with not being able to run the webplayer offline. It worked fine up until 4.2 I believe. Now when i do an offline build I receive the failed to update error. Most of the time we are online but there are some instances where we have to be offline so this is very important to our project.
We are also facing this problem in places where the only connection is via vsat (meaning, cannot sustain downloading the player and mono from the internet).
Any alternatives?
Thanks