Preparing To Deploy

Directory Structure

The following files must be in your root project folder at build time:

File	Description
./LauncherMedia/Icons/Auxiliary/<any_name_prefix>@2000x1200.png ./LauncherMedia/Icons/Auxiliary/<any_name_prefix>@1600x800.png	These images are used by the P3's Launcher app to show your app's image on a mini-display on playfield modules such as Lexy Lightspeed - Escape From Earth and Cannon Lagoon. The format must be 8-bit/color RGBA non-interlaced.
./LauncherMedia/Icons/Backbox/<any_name>.jpg or ./LauncherMedia/Icons/Backbox/<any_name>.png	This should be a 1080p image representing your app.
./LauncherMedia/Icons/Main/*.png	These files are used to populate the app selection tiles in Launcher. Create images by modifying existing images and changing the content inside of the pink pillar bars. If multiple images are provided, the Launcher will cycle through them while the game remains the highlighted selection.
./LauncherMedia/Sounds/Launch/<any_name>.ogg or ./LauncherMedia/Sounds/Launch/<any_name>.wav	A sound effect or voice callout to be played when the app is launched.
./LauncherMedia/Sounds/Theme/<any_name>.ogg or ./LauncherMedia/Sounds/Theme/<any_name>.wav	A music file to be looped when the app is highlighted in the launch menu.
./Configuration/AppConfig.json	Configuration file.
./MiniLCD/*	Content for mini-display if using Multimorphic's MRPI Connection Management API.

Deploying To Your P3 For Testing

Follow these steps to build an installable package of your app for your P3. With you project loaded in Unity, select from the top menu Multimorphic->"Package App For Distribution". Fill in the fields in the dialog that appears and click "Continue". An internet connection is required.

When the process completes, you should have a new .p3p file within your project's Packages directory. The dialog also offers the option to write a copy of the .p3p file to a USB drive during the build.

The .p3p file can then be installed on your P3 via a USB drive.

Note: The current dev kit does not include the ability to deploy to a P3 programmatically.

These are the fields presented in the packager dialog:

Field	Description
Display Name	Name of application in the P3 Launcher carousel
Version	Application version (recommended format: a.b.c.d)
Description	Description of the application in the P3 Launcher carousel.
Compatible Module Ids	Comma separated list of module Ids that work with the app (e.g. "LL-EE, CCR, CL, Heist, WAMONH, FR, TPB", or "Any" to require any module, or leave blank to work whether any module is installed in the machine or not).
Feature Flags	Comma separated list of feature flags. Usually used if there are build variations.
Tags	Comma-separate list of tags. Reserved for future use.

Obtaining A Unique Playfield ModuleID

If you're developing a new upper playfield module, contact Multimorphic at support@multimorphic.com to be assigned your ModuleID.

Releasing Your App

Contact Multimorphic at support@multimorphic.com for more information about releasing both beta software and final versions for purchase/download from the Multimorphic website or for long-term deployment to your P3.