Option to add additional AR Foundation components

[genereddick]

Describe the problem

The AR Foundation wants many of its components to sit on the Camera Parent or the Camera.

But, adding components to the MixedRealityPlayspace and Main Camera is risky as the tooling code makes them easy to replace (using Add to Scene and Configure) and each MRTK version update recommends (has recommended) deleting and re-adding them.

The current MRTK AR solution allows you to add the AR Session, Camera Manager, et.al. to the MixedRealityPlayspace and Main Camera using the Toolkit.

However, there are many more components that may need to be included: AR Point Cloud Manager, AR Plane Manager, AR Anchor Manager, AR Occlusion Manager, and many others

In addition, there are additional configuration options that may need to be set even on the components already being added (e.g. a custom material is needed for the AR Camera Background when using the Universal Render Pipeline).

Currently the solution seems to be either:

a) add all the components in the scene to the MRP or Main Camera and deal with the risk of accidental replacement... essentially the same situation that existed prior to the introduction of the MRTK AR package.

b) Manually edit the UnityARCameraSettings file to change which AR Foundation components are added which has the risk of the file being overwritten on a release update (or if you have created a new file having the reference to your new file replaced in the UnityARCameraSettingsProfile, etc.).

We need a way to configure an arbitrary list of components to be added to each (the MixedRealityPlayspace and Main Camera), either in code or via prefabs.

[david-c-kline]

@genereddick, We have a work items to add support for AR Plane Manager, etc in a future release of MRTK.

Thanks!

[IssueSyncBot]

We appreciate your feedback and thank you for reporting this issue.

Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.

Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.

Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.

Thank you for your continued support of the Mixed Reality Toolkit!