VPS location not loading or working

Bug Reports
,
1

We are writing you in the hope that you can help us, we are honestly desperate. An event related to the municipality of Zurich is happening in a few hours that would involve an AR lens. The mesh was reactivated yesterday and doesn’t work.

Here is the location id

d922fe1c9c823a9389f9f17d0de76bd2.16

It seems that the mesh space is too large and somehow the location is not working. Not in reality or in the cloud simulator.

  • Issue Category: VPS
  • Device type & OS version: all of Android / iOS / Other Ex. iPhone 8+ on iOS 13
  • Host machine & OS version: all of Mac / Windows / Linux / Other Ex. Mac on Big Sur x.x
  • Issue Environment : Unity Remote / Unity Mock / On Device / Dev Portal
  • Xcode version:
  • ARDK version:
  • Unity version:

Bug reproduction steps:

2

Hello,

It’s come to our attention that the messages we’re sending each other back and forth are not showing up on this forum post (we’re working on seeing what the issue is) but luckily everything defaulted to an email conversation so we’ve been able to communicate regardless.

Moving forward you should be seeing the rest of the replies here. I’ve presented all the updated information you’ve provided me to our team and will be reaching back out as soon as I have additional information

3

After a further look at the locations heres what the information i can provide:

  • None of the sizes of the locations are big enough to be considered heavy for the VPS system, we’ve used locations that are much larger and have had successful localizations. We are unable to trim parts of a location’s mesh but, again, the sizes are not at a point where they would impact localization performance

  • I was also wondering if you can clarify something in the following sentence: “Our issue is that locations 1, 2B and 6 are not visible. In addition, in the editor the scan meshes do not appear”

    • Where you’re saying that they’re not visible are you referring to the preview in the Geospatial Browser or is it somewhere else? If you’re referring to the geospatial browser, that point has been clarified before; the preview you see on the map is not indicative of the final composite mesh. Even if a manhole is missing from the mesh preview it doesn’t mean that it’s been discarded in the final composite scan.
    • For the other part where you’re saying that the meshes don’t appear in the editor. Is this after importing the zip folder of the location into your Unity project? If so, can you share screenshots of what you’re seeing in the editor when you do import the mesh?

  • In previous messages (not shown here) you made reference to a “lens” is this like a 3D object you’re rendering into the area once localization occurs or is it something else? Based on what you’ve written via email, it seems like the lense is kind of supposed to act like a portal of sorts where users can see AR content through?

4

Hello,

We were looking into the meshes some more and decided to reactivate them to see if that fixes issues with localization.

We also noticed that these locations don’t seem to have had any more scans contributed to them since last November. I would highly suggest contributing more scans to the locations to improve overall scan and localization quality and reliability.

5

Dear Jesus,

• Even if this is not a file size issue, the problem persists: users are unable to see the AR experience on their phones without waiting 4 to 10 minutes, across all six locations. File sizes are around 10 MB max, and we verified that they are downloaded within a few seconds. Animation scripts, 3D assets, and sound assets are not causing the issue—while testing on the simulator, we turned them off and the problem remains.

Project 2B, 3, 4, and 5 are working fine by all criteria on our side, but when users try to experience the AR on location, they still have to wait 4 to 10 minutes before it appears. This seems to be an issue related to the Niantic platform. We would kindly ask you to investigate why this is happening.

• Project 1, 2B, and 6 have additional issues:

In the Niantic editor (the geospatial browser inside Niantic Studio), the meshes are not loading.

Project 1 is lagging heavily in the simulator and in the GSB (geospatial browser), which indicates that the VPS mesh and/or SLAM data are very heavy.

Project 2B the VPS mesh doesn’t appear in the GSB.

Project 6 is not showing any mesh in the simulator , which indicates a problem with the VPS mesh and/or SLAM data.

We kindly ask you to look into these two locations (project 1 and 6) and manually fix the meshes and SLAM data.

We could send someone to perform new scans, but it does not seem practical that the scans would need to be updated every two months in order for the AR experience to work. What kind of service causes the locations to become obsolete after only two months?

Thank you
Silvia

6

Hi Silvia,

We’ve moved your issue further up the chain to take a deeper look into this. I will keep you posted.