After updating Unity to 5.0.1p1 I receive the following error on Web Player/MacOSX/Safari (I have rebooted as well):
“Error launching Unity Player”
(Failed to initialize the content).
Anyone else has the same problem?
Guys! it seems that the Web Player bundle is not published yet.
This address returns a 404 error:
http://webplayer.unity3d.com//autodownload_webplugin-3.x/UnityPlayer5.x.x-x86_64.bundle.zip
I filled a bug, but can anyone confirm this? Thanks.
Guys, can you confirm is this is a new bug?
You shouldn’t publish to webplayer using a patched version of Unity.
The online webplayer only receives an update from released Unity versions.
1 Like
Argh. Thanks for shedding some light on this!
So, how can I test my product offline on Web Player?
Edit: I patched because I had a HTTPs issue with Web Player and Parse API.
If you run a patched editor, you need to also install the patched webplayer from the patches page - it’s listed as a separate installable component when you expand the patch you want to use.
THANKS! I’ll try that tomorrow.
Well… tried today and no luck.
I’ve installed the Web Player package according to the patch release and rebuild the project. Uploaded to my website and still it’s not running (same error, failed to load content).
Don’t know what to do now. I’m supposed to wait until next version?
And, one thing that I don’t understand is: if there’re a important bug fixed in the patch, why can’t I build the project? What the point of having one Web Player bug fixed if it can’t run online because it’s a patch?
I have had the same issue when made a build with 5.0.1p1. I think it’s just best to wait for 5.0.2 containing this fixes…
1 Like
I can’t believe I have to wait for n weeks in a dead end. Please someone from Unity help.
Do you need the p1 patch? I just deployed an app to my server built with V5.0.1f1 and it works just like 4.6 did from Chrome and IE (don’t have Safari of Firefox installed anywhere right now but I’ll test those tonight).
Yes, prior p1 patch there’s a bug with Parse API which asks the user for auhtentication.
We are experiencing the same issue.
What’s the problem with updating the WebPlayer if the patch solves a critical bug? Parse integration from WebPlayer is completely broken in Unity 5 right now.
Same issue here with 5.0.1p1: I could never make the webplayer work, even with my own installed development webplayer plugin installed, same version 5.0.1p1. The error message is “Error initializing player 3d settings” or something like that.
So I reverted back to 5.0.1f1, both Unity and webplayer, and now it works.
This is how it’s supposed to work:
a) You download a patch release, this installs the patch release web player on your machine.
b) You import your project into the patch release and do anything you need to.
c) You make a local web player build.
d) You open the local build which should work, since you have the patch release web player on your machine.
e) If that all works, I guess making a regular web player and uploading it to your server and then viewing it on your machine will work.
There is no way for the patch release web player runtime to be available to anyone who does not have the patch editor release.
Now, it’s possible that the 5.0.1p1 release hasn’t installed the web player. You can check in your regular web player locations to see which version you have. Always look at the Info.plist which will tell you the version. If the plugin fails to find the correct runtime it’ll talk to our servers and be told it doesn’t exist.
As others have said, the web player version on our website is only updated when we make a regular “final” release, so if we release 5.6.7f1 then that web player would be on our website. 5.6.7p8 would not have a web player available to the public.
@Graham-Dunnett - is there any information you can offer as to when the next final / non-patch release will go to the public for Unity 5?
The problem is many of us have not yet been able to ship a web build on the Unity 5 version because every single release / patch / etc. has had HTTPS broken in web player.
5.0.1p1 is the first patch to fix this, yet the fix is pointless / useless for releases until a final release includes it. Having some idea of timeline would be very helpful for us.
Thanks!
1 Like
Where does WebPlayer install to on Mac OS? I can’t find it after a successful installation (Internet Plugins folder is empty).
P. S.: I agree with @cojo71 . I need that fix publicly available so when will we get the next release?
I see it in:
/Library/Internet Plug-Ins/Unity Web Player.plugin/Contents
If you drop into the Frameworks folder inside there you’ll see the Mono and Player components, so dive into them to see the exact runtime versions you have.
We make patch releases over 3 weeks of a month, and round them all up in a fully QAed public release on the fourth week. We do not make patch releases publicly available, because only 0.0001% of customers are affected by the bugs we fix and put into patch releases. (I made up the percentage.) Testing a public release takes lots of time, and is not something we can do weekly.
Now I see. Opening Info.plist reveals:
<key>CFBundleShortVersionString</key>
<string>UnityPlayer version 5.0.1f1</string>
<key>CFBundleSignature</key>
<string>BRPL</string>
<key>CFBundleVersion</key>
<string>5.0.1f1</string>
It seems that you have included the previous version of the WebPlayer into the patch 5.0.1p1 (for MacOS, not checked for Windows), and this is why it doesn’t work locally after installing the patch.
Can you double check this please?