Checking for AR availability BEFORE launching AR scene?

I am trying to build some logic to test the device after app start to decide whether to allow for AR scene or only conventional 3D scene.
I know we can use

ARSubsystemManager.systemState

to check that but this works only when AR Session component is present in the scene, which means that there needs to be an attempt to initialize AR Session.
This is pretty expensive task that I would like to avoid straight after launching the app.

Is there any way around?

 

Thanks Tim, I tried ARSubsystemManager.checkAvailability() in a coroutine but is doesn't work unless AR Session is initilized - systemState is returning "Unsupported". When checking systemState in AR-enabled scene it works ok.

I guess it is due to these lines of code inside ARSubsystemManager.checkAvailability():

Code (CSharp):

1.             if (sessionSubsystem == null)
2.             {
3.                 systemState = ARSystemState.Unsupported;
4.             }

For me this means you need to try to initialize AR Session first to check whether it will work.
Of course I am considering this for an "AR-optional" app, where depending on the device compatibility the user is given either 3D-only or 3D+AR options.

 

Ended up doing like you said, thanks!

 

Hi @Saicopate, would you be willing to share what you did to establish AR availability? Thx!

 

Sure.
I run this at the start of non-AR scene (replace Debug.Log with your own implementation).

Code (CSharp):

1.    
2. private void OnEnable()
3.     {
4.         ARSubsystemManager.CreateSubsystems();
5.         StartCoroutine(ARSubsystemManager.CheckAvailability());
6.         StartCoroutine(AllowARScene());
7.     }
8.  
9. IEnumerator AllowARScene()
10.     {
11.         while (true)
12.         {
13.             while (ARSubsystemManager.systemState == ARSystemState.CheckingAvailability ||
14.                 ARSubsystemManager.systemState == ARSystemState.None)
15.             {
16.                 Debug.Log("Waiting...");
17.                 yield return null;
18.             }
19.             if (ARSubsystemManager.systemState == ARSystemState.Unsupported)
20.             {
21.                 Debug.Log("AR unsupported");
22.                 yield break;
23.             }
24.             if (ARSubsystemManager.systemState > ARSystemState.CheckingAvailability)
25.             {
26.                 Debug.Log("AR supported");
27.                 yield break;
28.             }
29.         }      
30.     }
31.  

 

Hi
Implemented the solution above.. appears to be working thanks @Saicopate && @tdmowrer

One question.. if using this check in non AR main menu... should I use

Code (CSharp):

1. ARSubsystemManager.DestroySubsystems()

.. after I have completed the check and before I load into my AR scene? as per ARSession?

Or will these subsystems get destroyed gracefully when I unload the main menu scene and load the new AR scene?

Thanks

 

hey @tdmowrer

I have my ARCore Optional app working on devices that do not support arcore etc. And use the above logic to enable AR within my game.

How would I do same for IOS? Such that my app will be made available to all devices running target IOS ver 11... whether they support ARKit or not.. and then allow the logic above to control enabling/disabling AR within my game.

Thanks

 

I don't appear to have that option... Unity 2018.2.6 ARKit preview 17...? Was it introduced in newer version?

Any way to override in xCode? ie. make ARKit optional?

Thanks

 

How can we update this to work in Unity 2019? ARSubsystemManager and ARSystemState no longer seems to exist.