For example, if the product name is defined as “MyPlayer” in the Player settings:- %UNITY_WEB_NAME% The tags are delimited by percent signs (%) in the page source. These include the name, onscreen dimensions and various other useful information about the player. Template Tagsĭuring the build process, Unity will look for special tag strings in the page text and replace them with values supplied by the editor. The thumbnail image will be displayed in the inspector to hint at what the finished page will look like. Optionally, the folder can contain a file named thumbnail.png, which should have dimensions of 128x128 pixels. (the name of the template will be the same as its folder). Once created, the template will appear among the options on the Player Settings inspector. Each template folder contains an index.html or index.php file along with any other resources the page needs, such as images or stylesheets. Structure of a Webplayer TemplateĬustom templates are added to a project by creating a folder called “WebPlayerTemplates” in the Assets folder - the templates themselves are sub-folders within this folder. Unity allows you to supply your own pages to host the player by using webplayer templates. For example, if the Unity content interacts with other elements in the page via the external call interface then it must be tested with a page that provides those interacting elements. The built-in HTML pages are fine for testing and demonstrating a minimal player but for production purposes, it is often desirable to see the player hosted in the page where it will eventually be deployed. There are actually three different variations of this page which can be selected from the Player Settings inspector (menu: Edit > Project Settings > Player). The default page is very simple, with just a white background and some minimal text. When you build a webplayer project, Unity embeds the player in an HTML page so that it can be played in the browser.
0 Comments
Leave a Reply. |