LightshipOcclusionExtension is not yet supported in combination with ar foundation version 6.0 or later

Include the following details (edit as applicable):

  • Issue category: Unity Example Package
  • Device type & OS version: Editor
  • Host machine & OS version: Mac
  • Issue Environment : Editor
  • Xcode version:
  • ARDK version: 3.15.0-2508040839
  • Unity version: 6000.0.53f1

Description of the issue:

In the ardk-samples, in the Occlusion scene, the LightshipOcclusionExtension has a message stating “This Component is not yet supported in combination with ar foundation version 6.0 or later.” I’m using AR Foundation 6.0.6

Also, in the Package Manager, it states that Niantic Lightship AR Plugin is in pre-release. But I can’t figure out how to install a released version.

Any tips?

Hi David,

Thank you for reaching out!

We are aware of issues with AR Foundation 6.0 and later with ARDK 3.15. In order to have the best experience – even on Unity 6 – we recommend using AR Foundation 5.2.0. Please downgrade to that version via the Package Manager and follow up with your experience.

Regarding the “pre-release” message: The version of the ARDK you’re using is the latest available and you can safely ignore that message.

Let me know if you have any other questions or need further clarification!

Kind regards,
Maverick L.

Thank you for your response. My understanding is that AR Foundation 5.2.0 doesn’t support Unity 6, is that true? If Unity 6 is supported, I don’t see how I can downgrade AR Foundation in Unity 6’s Package Manager

When I downloaded the Lightship example at GitHub - niantic-lightship/ardk-samples: ARDK Samples Unity Project , the project is in Unity 6.

In the “Sample Projects” doc ( Sample Projects | Niantic Spatial Platform ) the language implies that I can use Unity 6 or 2022.3.62f1.

So I’m a little unclear. Can I use Unity 6 and downgrade to AR Foundation 5.2.0? Or do I have to use Unity 2022.3.62f1 so I can use AR Foundation 5.2.0?

In the “Setting Up the Niantic SDK for Unity” doc ( Setting Up the Niantic SDK for Unity | Niantic Spatial Platform ) it states that Unity 6 is supported.

You’re very welcome.

Yes, the ARDK supports both Unity 6 and Unity 2022, but there’s a known incompatibility between AR Foundation 6.0 and ARDK 3.15. In our tests, AR Foundation 5.2.0, ARDK 3.15, and Unity 6 work as expected together. You should be able to downgrade and maintain your project in Unity 6.

Kind regards,
Maverick L.

Thank you for that clarification! Do you have a resource you can share for downgrading AR Foundation to 5.2 in Unity 6? I can not find a way to do this using the Package Manager. Thank you!

After researching, I’ve discovered that it is not possible to use AR Foundation 5.2 in Unity 6. This was confirmed by a member of the AR Foundation team → How to downgrade to AR Foundation to 5.2 in Unity 6? - #7 by andyb-unity - Unity Engine - Unity Discussions

Hi Dayvid,

Thank you for your patience, and I sincerely apologize for the delay and the earlier confusing guidance. This stemmed from a miscommunication on our end.

To clarify: certain features—such as the Occlusion Extension—are not yet fully compatible with AR Foundation 6. My earlier recommendation to downgrade your AR Foundation package was not accurate for Unity 6. We are actively working to expand full support for AR Foundation 6.

In the meantime, could you share which render pipeline you’re using and which functions of the Occlusion Extension are most important to your project? That way, we can work together on a solution that best supports your needs.

Kind regards,
Maverick L.

Hi! I’m using URP. At this point I don’t have a specific Occlusion Extension that’s important, just overall occlusion.

What features are currently fully compatible with AR Foundation 6? Thanks!

Hi Dayvid,

After consulting with our team internally, it’s hard to answer that question as AR Foundation has had progressive deprecations in its releases after 6.0. We know about an incompatibility between our occlusion extension and AR Foundation 6, but haven’t noticed other incompatibilities. We’re actively working to resolve these compatibilities and will have a fix for them in an upcoming release.

I apologize for the delay.

Kind regards,
Maverick L.