12 docs tagged with "Application Simulator"

Overview

The Application Simulator tool in the ML Hub lets you iterate and test code changes without having to build and deploy the app to a device. Incorporating Application Simulator into your workflow can result in significantly faster development cycles.

The App Sim (short for "Application Simulator) for Unity is an offering that is separate, but related to the App Sim. Previously, it was recommended to use the App Sim (through the Magic Leap Hub), but due to performance and compatibility reasons, it is now recommended following the steps outlined on this page and not using the pattern involving strating the App Sim in the ML Hub, switching to Unity, and clicking Play.

Follow this guide to setup Application Simulator for use in your development cycles.

You can activate Application Simulator functions to iterate on the device using command line tools.

See our guide for the App Sim for Unity.

The Application Simulator interface in the Hub and the Application Simulator for Unity package can be used across multiple host platforms, applications, and graphics APIs.

Application Simulator is backwards compatible with all versions of the MLSDK starting with 1.0.0. Users are encouraged to upgrade to the latest Application Simulator updates in Package Manager.

Marker Tracking with the Application Simulator

Use session files to re-use your current scene setup for testing or to share your setup with other members of your team. Session information includes:

After opening Application Simulator and starting a session, the Application Simulator module populates with options.

Application Simulator can fit into your workflow in a few different ways. To decide which target mode you want to work in, first you want to decide where your input and world data come from. There are a few different sources this data can originate from.