Google Chrome version 42 was recently launched and they disables supporting for any Unity Web Player, Completly removed it Unity Web Player Chrome Not Working
Google Chrome version 42 was recently launched and they disables supporting for any Unity Web Player, Completly removed it
Unity Web Player Chrome Not Working
Chrome carries a huge competitiveness total, which range from 25-50% based on whatever source you are examining.
What unity blog said about it!
With Google about to complete the deprecation of NPAPI assistance in their Chrome browser, we’ve been receiving many questions regarding exactly what the ideal alternatives are for publishing games on the web and achieving Chrome users at the same time. With Chrome’s broad usage, these are fair questions
So what exactly should I do whether my game requires the Web Player?
In case your current game needs the Web Player to work properly (specifically for people using advanced high performance games), here’s a few recommendations of what can be done within the meantime:
Option A: motivate gamers to make use of alternate web browser where unity plugins are still working. Make a web page to pop up whenever plugin won’t start that notifies people of what has occurred and show web browser that still function very well along with your game.
Option B: come with guidelines on how to enable plugins to work in Chrome before the plugin is removed totally on NPAPI in September (after which it is impossible to allow NPAPI plugins.
Recommended: Unity Web Player For Linux using Pipelight
Example instructions follow:
Step 1: In Chrome’s address bar, type: chrome://flags/#enable-npapi
Unity also gave the solution for new building games, they said!
What if I’m developing something new?
We recommend that those of you creating new web games with Unity start new projects with Unity 5 WebGL as the default target. WebGL games are more limited in terms of functionality and performance than Web Player games, so you can port your game to the Unity 5 Web Player later if you choose and add some additional functionality to leverage the greater capabilities of the Unity Web Player. This way, gamers will be able to play a WebGL game on Mozilla Firefox, Google Chrome, Apple Safari 8.x or play it as a Unity Web player game on Microsoft Internet Explorer, Apple Safari 7.x, or Yandex.Browser which should provide the widest audience possible.
Keep in mind that with Google well on their way to removing NPAPI support from Chrome entirely, other browsers will follow suit. This eventuality (there are no confirmed timetables for this) makes it very hard to recommend beginning new projects with the Web Player in mind at all.
The short of it
WebGL will be amazing – even better than The Unity Web Player because there will be no plugin barrier for players – but there’s no avoiding that it’s not yet as capable as the Unity Web Player and there’s no spectacular technological option to get around the deprecation of the framework that made it possible. We understand this is a rough transition and feel your pain as we would love the Web Player to continue functioning across all browsers, but unfortunately that decision ultimately is not ours to make. For the time being, if you’re maintaining a very complex game that you want to run well on the web, you’ll need to use the Web Player and direct customers to other browsers.
And we’ll keep collaborating with browser manufacturers to make the WebGL platform and our WebGL tools as powerful as we know they can be!