Migrating unity applications to easyar sense unity plugin 4000
This article explains how to migrate unity applications from older versions of easyar sense unity plugin to version 4000.
Before you start
Depending on the version of easyar sense unity plugin currently used in your project, file deletion and plugin package replacement operations are required before migrating to version 4000.
- Migrating from easyar sense unity plugin 4.2 and older versions requires following the steps in migrating from version 4.2 and older.
- Migrating from easyar sense unity plugin 4.3 - 4.7 to 4000 requires replacing the plugin package by referring to the general migration guide.
Note
4.7 was only open to limited mega development users, with many sub-versions. Specific interface changes need to be determined based on the specific version number.
The lifecycle of 4.7 has ended. Users of version 4.7 are advised to upgrade to 4000 as soon as possible.
Migrating to version 4000
After importing the easyar unity plugin 4000 version, due to significant functional changes, the following modifications are also required.
It is recommended to delete the ARSession in the scene and re-create it.
Related changes:
- Significant interface and script changes.
- Default parameters for some scene components have changed.
- AR foundation support has been rewritten.
Using sparse spatial maps requires adjusting code and scene objects by referring to samples and API reference.
Related changes:
- Sparse spatial map interface has been split.
If your project contains previously imported sample files, you need to completely delete old files before importing new samples. If modifications have been made based on samples, backup is recommended.
Related changes:
- Samples have been completely rewritten.
Adjust diagnostic function options. Refer to making full use of UI diagnostic information and tools to quickly understand essential options. Detailed feature introductions and usage methods can be found in problem diagnosis and reporting in unity development.
Related changes:
- Adjusted and added diagnostic functions.
Using XREAL functionality requires referring to enabling headset support. When using XREAL, importing a separate package is no longer needed.
Related changes:
- XREAL support is built into easyar sense.
Using AR foundation requires referring to enabling ar foundation in easyar projects.
Related changes:
- AR foundation support has been rewritten.