Unity Compatibility Problem

Bug Reports
1

Hello, I’m trying with MetaQuest3. I’m trying the latest version of OpenXR in Unity 6000.3.4f1, and when I download the LightshipQuest Package Library\PackageCache\com.nianticlabs.lightship.metaquest@0bbd1fb95e9a\Runtime\Utilities\OcclusionMesh.cs(275,25): error CS1061: ‘MeshRenderingPass’ does not contain a definition for ‘SetMaterial’ and no accessible extension method ‘SetMaterial’ accepting a first argument of type ‘MeshRenderingPass’ could be found (are you missing a using directive or an assembly reference?) Library\PackageCache\com.nianticlabs.lightship.metaquest@0bbd1fb95e9a\Runtime\Utilities\OcclusionMesh.cs(276,25): error CS1061: ‘MeshRenderingPass’ does not contain a definition for ‘SetMesh’ and no accessible extension method ‘SetMesh’ accepting a first argument of type ‘MeshRenderingPass’ could be found (are you missing a using directive or an assembly reference?) The above problems come out. I somehow bypassed the error and changed Passthrought to a LightShip one, so it takes infinite loading and doesn’t work. If I change it back to Meta Quest Passthrought, it runs, but I don’t think tracking is possible. Is there a way?

  • Platform category: Unity
  • Device type & OS version: Android
  • Host machine & OS version: Windows
  • ARDK version: 3.17.0

Bug reproduction steps:

4 Likes
2

I’m having the exact same problem. It seems to call functions that are only available on Unity 2022, not Unity 6. However, I also tried to run it on Unity 2022, which doesn’t work either, because it depends on ARFoundation 6.1.4, which is only available on Unity 6. Hence, neither Unity version works. So from all I’ve seen, Quest support is currently completely broken and Niantic needs to fix it.

1 Like
3

I am facing the same issue, is there any sort of fix that people found?

No matter the version of Unity, it seems to be repeating. and this is happening with NSDK 4.0 or the previous ARDK UPM.

image
image1230×305 41.8 KB

4

Thank you for sharing your reports. I’ve escalated these findings to our engineering team for further review and resolution. I will provide an update here when one becomes available.

Kind regards,

Maverick L.

1 Like
5

Here are my findings, I hope this will help.

The issue occurred by doing these steps:

  • New Project in (Unity 6.0.52/6.0.58/6.3.2f1)
  • Android Platform and Meta SDK Setup
  • Added NSDK / ARDK
    (No errors till here)
  • Added NSDK/ARDK - Meta Quest UPM
    Here: The above screenshot issue occurs. This happened no matter what version or new or previous SDK, even with Tar ball or git import.

An Interesting finding is, this wasn’t happening when I cloned the Immersive Insiders Example project.

In which, the package code is very different, the files dont have #if MODULE_URP_ENABLED etc.

Here is their project and video (Note: I recreated their tutorial steps, and I still faced above issue, and this is also the old ARDK):

Thank you

6

Hi everyone,

Thank you for your patience. Our engineering team has resolved these issues, and the fixes will be included in the next NSDK release.

Since the issues outlined in this thread have been resolved I’m going to close this thread. Please create a new topic if you experience any issues with the Meta Quest 3 or any other features of our NSDK.

Kind regards,
Maverick L.

1 Like