![]() ![]() ![]() Unity will still allow downloading of the Unity 5.3 Web Player to run any existing content. The short answer is yes, all Web Player content will still be playable in browsers that support NPAPI plugins. So, what about all the existing Web Player content that exists on the web, can users still play my Unity Web Player powered games? Learn more about WebGL support in Unity in our documentation. We are working closely with browser vendors to make sure this gap becomes as narrow as possible, but there are some limitations which are defined by the platform - such as restrictions on the networking protocols you can use, which are mandated by security concerns. However, it is important to understand that WebGL is a different platform from the Web Player and does not match the feature set or performance of the Web Player. This means that WebGL content runs without requiring any plugin install. Unlike the Web Player, WebGL is not a plugin, but uses standard APIs exposed by the browser. So, what does this mean if you want to target the web with Unity from March 2016 onwards? With 5.4, the only option to generate web content in Unity is our WebGL export, which is currently in preview. The Web Player will then become an unsupported product. For the Web Player, Unity 5.2 and 5.3 will still be able to publish Web Player content, but Unity 5.4 (to be released in March 2016) will no longer ship with Web Player support. When Unity marks a feature as deprecated it means that the use of the feature is no longer recommended and that the feature will be removed in a future release. However for maximum compatibility it’s best to place some warning message in case the browser doesn’t support JavaScript and the placeholder isn’t replaced by UnityObject.Today we are announcing the first step in that end-of-life process, the deprecation of the Web Player. U.initPlugin(jQuery("#unityPlayer"), "Example.unit圓d") įinally, the HTML placeholder is placed inside the section. See UnityObject2.initPlugin for more info. ![]() ![]() The second parameter specifies the path to the web player data file to be displayed. Think of it as a temporary placeholder where Unity should be placed. It could be any HTML element with being the most common. The first one specifies the id of the HTML element that will be replaced by Unity content. This is performed by instantiating UnityObject2 and calling initPlugin on the new instance. You can now instantiate the UnityObject2 class to assist you in various Unity-related tasks, the most important one being embedding Unity content. The UnityObject2 script has to be loaded before it can be used. The rest of the document explains the inner workings of this file. In most cases you don’t have to modify the HTML file at all. The HTML file generated by Unity when building a web player contains all the commonly required functionality. It also enables easy Web Player installation. Its primary task is to make Unity content embedding very simple by shielding the user from various browser- and platform-specific issues. HTML code usually does not communicate with this plugin directly but via the script called UnityObject2. Unity content is loaded in the browser by the Unity Web Player plugin. ![]()
0 Comments
Leave a Reply. |