An interesting issue has cropped up for me with the Unity Web Player. We have a team of folks showing some early prototypes of our Unity project at meetings where they can’t guarantee to be online (actually often they are not).
This is normally no problem, the unity3d file is local on the machine and the web player is installed. However we are running into a scenario where, based on some unknown factor (date, version) the web player on these machines is presenting as if it is “forcing” an update when the user tries to start the .unity3d file. I am not sure what the trigger is since the laptop is offline and could not know that a new version is even avail (we are currently installing the 3.x player from 12/30/10). Perhaps it is that this is a beta release? But again it is a problem since although we know the unity project works fine in this version of the player, the user is apparently stuck with no way to update and no way to play the file. Is there a way around this forced update for the purposes of offline playback of a Unity project?
Perhaps the local machine does not have the webplayer plugin installed in the version required. Ensuring this can be done by starting it while online at least once.
Alterantively someone provided you with a webplayer built with a beta versions, those are not meant for distribution at all.
Unsure if the player version you install is the newest. the webplayer plugin is updated on its own without a direct relationship to Unity 3 releases (last I checked it, it was at f6 or so already)
Thanks for the response, the laptops in question definitely had been working both online and offline for about 18 days and then on Wednesday of this week just consistently had this issue across any (two that I know of) if offline. Even if I update the web player offline (download the latest installer from unity3d.com (which is where the original installers came from also) it refuses to play, very very strange.
And again, on a laptop that does not have online access it simply will not play the exact same .unity3d file that has been working fine since 12/29/10 until 01/19/10. Any other ideas? I am perplexed.
Was this problem ever resolved? We seem to be having a similar issue (that just began to appear with the release of the 3.2 web player). I believe all of our content worked fine running locally (offline) until this version of the web player was installed on the machine.