Anyone else seeing this same issue (it’s definitely more than just me at my work). Where playing webplayer of Unity since Chrome 32.x only shows a white screen. The player is definitely loading and can be seen by "refreshing " through resizing the page in some way by pressing F11 etc. I’ve seen some posts elsewhere of similar issue with Flash.
Update: Version 33 of Chrome seems to have fixed this issue, and so it was a genuine bug in Chrome. The NPAPI stuff is a bit of a smokescreen and I don’t think related to this since for now Unity is on the Google Chrome NPAPI whitelist.
Are we Sure Google will even consider this a Bug at this point with them on their way to completely remove support for NPAPI Plugins? Hell I wouldn’t be surprised if they didn’t care, who knows they may be pulling the plug right now…
I just started getting this issue also, Unity Player Not Loading… I even cleared by browser Cache and History, Restart Chrome and still it did not load Unity at first, eventually it started loading… but then happened again.
I doubt Google will care… best of luck to us who Need Unity Webplayer Working, and Chrome Pulling the Plug on it soon…
I’m in the same boat, all the Unity developers I work with develop for Webplayer as the primary platform, for paying end users. Simply “well it won’t work on Chrome now” isn’t really good enough unless we know clearly that it will be fixed or there’s an alternative.
I had this issue, and then discovered that if I opened the plugins window ( chrome://plugins ) and manually checked the “always allow” for the Unity WebPlayer, it worked again for me.
Perhaps my issue was unrelated as I can only speak from my own experience, but hopefully it helps some of you out at least.
EDIT: As an aside, actually selecting “Allow for this site” or “Allow now” when chrome prompted did NOT work, I just ended up with a blank area, only going into the plugins settings and forcing it to “always allow” was what fixed it for me.
This makes no difference for me or the others I know with the problem unfortunately. Even if it did work there’s still the issue of the thousands of our end users then having to make this manual change.
Ah, that’s a pity … it definitely did the trick for me. I agree 100% that it’s not a “solution” though. It’s merely a hacky work-around (if it does work for you) for those that might need it.
Ok so, I found another PC to test and try some things with this, using various random WebPlayer examples online.
This is definitely a Chrome bug. I’ve noticed that, even with the settings I used (in my above post) it still shows a white screen in each tab until you open the developer console. At that point, it displays, you can then hide the developer console and any other WebPlayer examples loaded in that same tab will now work.
It seems that (sometimes) it simply doesn’t load and you have to give it a gentle “jiggle” (ie: open dev console) … and then it displays in that tab. Most frustrating.
Yep, this is definitely a problem. I sure hope this gets addressed soon, it’s so much easier to get people to play your game in a browser than from an executable they have to download
Is that really how this is going to go? My understanding is that the standards have changed and ALL browsers will going this route in future releases. I think another user already reported issues in the nightly builds of firefox. I don’t think the browsers are going to budge on this one…
Yes at the end of 2014 the Unity web player will stop working in Chrome. And yes, that’s frustrating, and yes, Unity is talking with Google about this. However, this thread is about a bug in current versions of Chrome, which, if you following the link above, you’ll see was reported by one of the Unity engineers. The parent bug (325309) was fixed by Google on 23rd Jan. So looks to me that Google has budged on fixing a bug in Chrome. I’ve had a quick look around the Chrome release page, but not seen any SVN logs that indicate this fix has made it into stable, beta or dev versions of Chrome, yet.
Actually I thought this thread was about “Chrome version 32 not displaying webplayer”
That bug is certainly related, but so is [332749] which appears to have been incorrectly merged with the bug you linked, and doesn’t appear to have been resolved.
Thank you though for the clear and concise statement “at the end of 2014 the Unity web player will stop working in Chrome.” I feel like it’s been pulling teeth to get that statement from anyone at Unity.
Yeah, but I think by the end of 2014 there’ll be a version of Chrome newer than v32.
As I said, 332749 was reported by one of the Unity engineers to Google. Google then merged it with 325309 which appears to be the same problem affecting regular URLs without the Unity plugin. I can’t comment on how Google handle their bugs, however.
Well the web player we know and love is an NPAPI plugin, and Chrome will cease supporting NPAPI at the end of the year. So, it’s true that the plugin we know and love today is going to stop working. I don’t think that’s new or I’ve revealed some hidden truth.
Not surprising… why should they care to fix this, fixing a Unity Webplayer Plugin based on NPAPI is that last thing Google is concerned about right now. Sorry for being so bitter, but yea Graham, i’m pretty damn disappointed about the whole situation and will continue to be until i see a solution from Unity regarding Unity Webplayer not working in Chrome past this year, hell it’s barely working now… And of-coarse I know this is not Unity’s fault… just patiently waiting for some news on where Unity is going with the Web Player…
