Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
getting_started [14-10-2016 15:52]
admin
getting_started [19-07-2017 09:28]
185.48.102.186
Line 1: Line 1:
 ==== Installing the PDK for Unity3D ==== ==== Installing the PDK for Unity3D ====
-This guide is based on a new installation of the PDK. To upgrade from an older version please see the [[upgrading_from_old_pdk|upgrading manual]]+This guide is based on a new installation of the PDK and the PilloTemplate. To upgrade from an older version please see the [[upgrading_from_old_pdk|upgrading manual]]
 === Set API compatibility to .NET 2.0 === === Set API compatibility to .NET 2.0 ===
 First thing you need to do is set the API compatibility to .NET 2.0. With a project open, go to Edit > Project settings > Player. This will open a new screen in the Inspector window. Click on the tab //Other Settings// to display the //Api Compatibility Level// option. This is (by default) set to //.NET 2.0 Subset//. Change this to //.NET 2.0// Having trouble finding it? [[http://​developer.pillogames.com/​wiki/​lib/​exe/​detail.php?​id=getting_started&​media=1.png|check this image.]] First thing you need to do is set the API compatibility to .NET 2.0. With a project open, go to Edit > Project settings > Player. This will open a new screen in the Inspector window. Click on the tab //Other Settings// to display the //Api Compatibility Level// option. This is (by default) set to //.NET 2.0 Subset//. Change this to //.NET 2.0// Having trouble finding it? [[http://​developer.pillogames.com/​wiki/​lib/​exe/​detail.php?​id=getting_started&​media=1.png|check this image.]]
  
 === Import the Pillo Development Kit === === Import the Pillo Development Kit ===
-Import the Pillo Development Kit as you would with any third party Unity package. Go to Assets > Import Package > Custom Package and link to the //PDK3.1.0.unitypackage//​ that is located in the //​PilloPDK\lib\UnityPackages//​ folder of the PDK zip. Required for development is everything located in the //_Core// folderAdditionally you can import the //Assets// and //​Examples//​ folders if you wish to get the demo data. +Import the Pillo Development Kit as you would with any third party Unity package. Go to Assets > Import Package > Custom Package and link to the //PilloTemplate.unitypackage//​ that is located in the //​PilloPDK\lib\UnityPackages//​ folder of the PDK zip. Required for development is everything located in the //_Core// folder ​and all the required template tools are located in the folder //​PilloTemplate// ​Additionally you can import the //Assets// and //​Examples//​ folders if you wish to get the demo data. 
  
 === Setting up the project === === Setting up the project ===
-The fastest way to prepare ​your project ​now is to simply drag and drop the prefabs from the prefab ​folder into your sceneDrop both the PilloController.prefab ​and the PilloSubscriberExample.prefab into the scene. The PilloController ​is simply ​the script that hosts all Pillo functionality with UseEvent enabled by default. In the PilloSubscriberExample ​you can find the event functionsHere you can start programming your game logic. It also shows how to subscribe ​and unsubscripe these functionsFrom here on you can start building your first Pillo game!+By importing the package you have already set up your project! In the folder //​PilloTemplate/​Scenes//​ you can find the scenes needed for basic setup. You can move the scenes to another ​folder ​if it is easier for you.  
 + 
 +Do not forget to add the scenes ​into your build settingsGo to //​File->​BuildSettings->​AddOpenScene// ​and add each of the Pillo scenes, ordering is not important. 
 + 
 +**GameScene** ​is the scene where you need to program ​all the logic of your Pillo game, it already has 2 prefabs on the scene, //​ManagerSetup & UILoader//, which are responsible for loading Template UI elements and other event managing settings. You are free to do what you want on the scene (only leaving those 2 prefabs), it will not affect the template. 
 + 
 +**MainUIScene** is the scene which is loaded as a second scene whenever ​you play other scenes. It has the reference ​to each UI state and each screen state. It has one object //MainUI// which has children //States, MainUI, MainUICamera and EventSystem//​. For more information about states and UI screens visit [[http://​developer.pillogames.com/​wiki/​doku.php?​id=screen_states|Screen States]]. //​MainUICamera//​ is used to render Pillo UI from this scene. 
 + 
 +**MainMenuScene** is similar to //​GameScene//​ but has Pillo splash screen implementedScreen states are responsible for loading wanted screens, so on this scene we get the background/​header & main menu UI on top of the existing scene.  
 + 
 +**TutorialScene** is the same as //​GameScene//​ and has a reference in the main menu.  
 + 
 +You can run the //​MainMenuScene//​ and browse the menu, as well as, start the game which will lead you to another scene, whereas if you press Escape key you will see pause menu and will be able to go back to the menu. 
  
 === Embed in your existing scripts (optional) === === Embed in your existing scripts (optional) ===