I tried that in another teamviewer session, but it didn’t help.
The error in the log was interesting though:
So for some reason it does not detect the installed revision - anyone knows what the cause might be? Where does the manager look for this installed revision?
I had this issue after installing 4.6.0p1, I mean everyone that tried to load the build in any 32 bit based browser (Windows and OSX) got the failed to update error. Only worked again once I downgraded to 4.6.0f3 and republished. If latest version of Unity Editor is 4.6.0p1, should the latest version of the webplayer also be 4.6.0p1, currently it’s 4.6.0f3 and it wants to update above that for anything built with the latest patch of 4.6 from what I’ve tried.
I have the same issue. I was about to report this in a new thread:
After installing 4.6.0p1, the WebPlayer plugin appears broken on my machine.
Here’s the use case
build game with 4.5.5f1
install 4.6.0p1 editor (and webplayer browser plugin that comes with it)
open game in firefox
failure
Here’s the WebPlayer.log :
141205 18:33:13 Instance starting, version 4.6.0p1_2cb3e4754d7f,UNITY_WEB_ENABLE_AUTODOWNLOAD: 1,GetDisableAutoUpdates(): 0
141205 18:33:13 Datafile file:///Users/lacostej/Code/WWTK/euclid/target/Euclid/Euclid.unity3d
141205 18:33:16 Requesting bundle 1 (3.x.x) update. Required revision range is 4608003 to 4608003, installed revision is ffffffff
141205 18:33:18 Setting error display: 'Failed to update Unity WebPlayer', details: 'A newer version of Unity Web Player is required, but the auto-update download failed. Was trying to download [URL]http://webplayer.unity3d.com//Channels/30840d631a27/UnityPlayer3.x.x-x86_64.bundle.zip[/URL]', link: 1
Removing the plugin (4.6.0p1) and reinstalling the one that is proposed by the wrapper html/js (4.6.0f3) fixes it.
I’ve since read this is all by design, patches are never released with corresponding webplayer. Basically patches are not for producing published work, they only seem to be for fixing development issues while waiting for the next point release. For me with demoing prototypes to customers etc and testing multiple times in a day it makes patches something to actually avoid.
"“The patch releases are not accompanied by a webplayer release. You have to wait for the next proper point release (4.6.1fx) which will include all the 4.6.0pX fixes and also an update to the webplayer channel.”
I know I meant the 4.6.0p1 issue. I.e. if there’s a patch release for 4.6.1 to 4.6.1p1 it won’t work with webplayer until 4.6.2 is released.
So people shouldn’t expect to be able to publish to web with Editor updates/patches between the point updates. It’s important to note because I didn’t know this until I hit the problem and it affects whether I should install the patches. As of right now I recommend everyone at my company not to install patches just because of this release pattern.
Maybe it’s worth having a note here on the page itself Download Archive that these patches don’t come with corresponding webplayers and won’t work until the point release later.
Unless I’m misunderstanding the blog post but it would explain why 4.6.0p1 doesn’t publish to web until 4.6.1 webplayer was released. What seems like a bug is actually by design of releases, which to me seems a bit confusing. Especially as this is reported on the forums as a bug more than once and no one actually was able to say this was the reason.
Well it’d make sense that info or a link to it at least is on the web page.
Every dev I’ve spoken to so far didn’t know about this, so it’s not my normal blindness (for once). I think just a case of all the right information is out there just not easy to find from one place to the next.
