Action Bindings
Overview
Overview
The Application Simulator tool in the Magic Leap Hub (ML Hub) lets you iterate and test code changes without having to build and deploy the app to a device. Incorporating the Application Simulator into your workflow can result in significantly faster development cycles.
Beginning with Magic Leap Unity SDK package version 2.0.0, the Magic Leap Application Simulator for Unity package will be officially deprecated. This decision comes as a response to community feedback and our ongoing effort to improve the developer experience.
If you do not wish to install the Application Simulator for Unity Package or if you need greater graphics support, you can run the App Simulator directly from the Magic Leap Hub.
Follow this guide to set up 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 Magic Leap Hub (ML 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 the Application Simulator and starting a session, the Application Simulator module populates with options.
The Application Simulator can fit into your workflow in a few different ways. To decide which target mode you want to work in, first decide where your input and world data come from. There are a few different sources this data can originate from.