![]() 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. Keep in mind that with Google well on their way to removing NPAPI support from Chrome entirely, other browsers will follow suit. 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. 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. We recommend that those of you creating new web games with Unity start new projects with Unity 5 WebGL as the default target. Step 1: In Chrome's address bar, type: chrome://flags/#enable-npapi Option B: Provide instructions on how to allow plugins to function in Chrome before the plug gets pulled completely on NPAPI in September (at which point there is no way to enable NPAPI plugins. Create a page to pop up when the plugin won’t start that informs people of what has happened and list browsers that still work well with your game. Option A: Encourage players to use alternate browsers where plugins are still available. If your existing game requires the Web Player to run properly (especially for those of you with complex high performance games), here’s some suggestions of what you can do in the meantime: So what do I do if my game needs the Web Player? It’s also very important to note that Unity Web Player still works beautifully on other browsers outside of Chrome, so there are options. Given this, we will continue supporting it for as long as it's useful for developers. The Unity Web Player is still the best option for high performance games on the web. The great news is that Unity and the browser manufacturers are collaborating closely to solve these issues! Everyone involved is very invested in ensuring WebGL achieves its great potential so we have every reason to believe that WebGL will make developer and gamer lives better in the long run. In the meantime, the best place to discuss WebGL issues is on the forums ( ) where our developers are very active. Unfortunately, because the technology is still in heavy development, both on our side and on the browser side, we cannot provide support through our premium support channel before we have a full release. Heavy games with high performance needs will likely find the WebGL option currently won’t fit their needs due to the aforementioned performance gap, some other platform limitations like networking, and scalability issues due to build sizes and browser-side memory constraints. ![]() It’s unlikely that you’ll be able to simply float your game over from Unity Web Player and expect everything to work perfectly. WebGL is totally feasible for “lighter weight” web games and apps in it’s current state but it is important to set realistic expectations. For more on WebGL performance, see our earlier blog post here: This includes a performance gap we are working to narrow though the issue is made more complicated by widely varying performance in different browsers. While this solution will eventually be excellent and we are working hard on WebGL with browser manufacturers like Mozilla, Google and Microsoft, the base WebGL technology is still limited in comparison to Unity Web Player. What seems to be the obvious solution to this is simply to make games in WebGL. We decided on moving forward with WebGL, which we announced at GDC 2014 and is now available in preview as a build target in Unity 5. There is not an explicit timetable for NPAPI deprecation in other browsers, though it will happen.įollowing this announcement, we began serious investigations into alternate avenues for web games. Currently, there is a workaround to get the NPAPI support back on in Chrome, but Google plans to completely remove NPAPI support from Chrome in September 2015. In 2013, Google announced that they would be deprecating and then disabling NPAPI, the plugin framework that Unity Web Player relies on to enable the richest interactive content experiences on the web. ![]() On the off chance that you’re creating web games and hearing about this for the first time, here’s a quick overview. Given Chrome’s wide usage, these are fair questions. With Google about to complete the deprecation of NPAPI support in their Chrome browser, we’ve been receiving some questions about what the best options are for publishing games on the web and reaching Chrome users at the same time. ![]()
0 Comments
Leave a Reply. |