Once your application is ready, you can deploy it via the menu “File/Build Settings…”.
You can find more information on building applications with Unity here :
By default, Predict Engine will be deployed in your application :
all the required Predict Engine assets will be exported with your application, you can find them in your build folder, in the "BuildName_Data/StreamingAssets" folder,
a setting file will be generated at the following path : "BuildName_Data/StreamingAssets/uvr-unity-settings.ous", it contains all your Preferences in an XML format. You can edit it manually when the application is not running if you need to change the path of omen.exe, enable/disable OMEN, edit the runtime menu,...
If you want to deploy your application without Predict Engine, you can disable the "Deploy Predictive Engine with the Application" toggle in the Preferences.
Predict Unity applications can only be deployed on Windows and Linux target platforms with a x86_64 architecture.
Predict Unity applications require a specific configuration in the Player settings (menu Edit/Project Settings..., section Player > Other Settings) :
The Scripting Backend must be set to "Mono",
The Api Compatibility Level must be set to ".NET 4.x".
You can export the current scene(s) with all the required assets (measures, environments, spectrums, observers,...) to a Unity package or to a Predict Engine standalone folder via the menus "PredictSuite/Export Scene/Unity Package" and "PredictSuite/Export Scene/Standalone Folder".
Export to a Unity package : if the “Include Inactive Elements” option is selected, the Predict Engine-specific assets required by the inactive elements in the scene will also be exported with the scene in the *.unitypackage.
If you export a Unity package using the “Assets/Export Package…” menu, you must make sure you select every required assets for the Predictive Engine scene (measures, environments, spectrums, observers,...). Using the “UVR/Export Scene” menu ensures all these assets are exported properly.
Export to an Predict Engine standalone folder : the assets and scene files will be exported in the folder you select when clicking on "Export Scene". The scene file will be named {Output scene name}.osf, the settings file will be named {Output scene name}.ors.
To render a scene using a cluster of GPUs, you must first export the scene using this interface and copy it to the cluster. See the Multi GPU Rendering section for more details.
When exporting a standalone folder from Unity, a scene file will be generated for every active camera in the scene : if there are no active camera in the scene, no scene file will be generated.
You can include Predict Engine in your Unity Forma projects using the Game view overlay display mode. The scene doesn't need additional settings to be started in Predict Engine, just make sure the overlay GPU memory optimization is disabled in the Engine Performances settings (this prevents the camera to be moved when using Forma).
All Forma functionalities should be supported when using the Predict Unity plug-in. Tested functionalities include :
Display of the Predict Engine overlay in front of the Unity render,
Placement of the camera or sensor in the scene and ability to move it using preset positions or the Forma controller,
Interactive choice of material variants,
Visibility variants (require a reload of the Predict Engine simulation),
Pack variants (if the pack lists a visibility variants, require a reload of the Predict Engine simulation),
Product selection (require a reload of the Predict Engine simulation),
Environment selection (require a reload of the Predict Engine simulation),
Hotspot definition,
Builds.
The PredictSuite menu doesn't appear when Unity is using the Forma interface, you can access Predict Preferences by right-clicking in the Hierarchy window, menu "PredictSuite/Preferences".