The VPS-activated portal failed its calibration in Ingress

I'm Stuck
1

Include the following details (edit as applicable):

  • Issue category: Lightship Maps / Semantic Segmentation / Multiplayer / Real-time Mapping-Depth / ARDK Documentation / Unity Example Package / Sample App aka ‘AR Voyage’ / ARDK Virtual Studio Tools / Developer Tools / Networking / VPS / Scanning Framework
  • Device type & OS version: Android / iOS / Other Ex. iPhone 8+ on iOS 13
  • Host machine & OS version: 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:

Description of the issue:
Hi Niantic Team,

My friends and I have been experiencing persistent VPS calibration failures for several weeks, we have 2 cases here:

  1. 545A7CE4314142508C4D1ED0D4504B0B
  • Portal reactivated 3 or 4 times
  • Still fails calibration in Ingress
  • Lightship URL:
    https://lightship.dev/account/geospatial-browser/23.035459,113.112579,15,545A7CE4314142508C4D1ED0D4504B0B,8d737e6c0d003f8293ab64d64985179a.16/scan-wayspot
  1. 045FC56A69B048BDB6745B073C720C42
  • Recently activated portal
  • Same calibration failure
  • Lightship URL:
    https://lightship.dev/account/geospatial-browser/37.42676518647389,-122.1485118421196,7.77,045FC56A69B048BDB6745B073C720C42,8cecdaf329063438882f99f5696bf87d.16/scan-wayspot

Could you help diagnose why these portals consistently fail calibration?

1 Like
2

same issue on this POI: Niantic Lightship

Sufficient number of scans, very good looking mesh - yet the overclock feature in Ingress always fails to calibrate. I have a suspicion this might be an issue of the game. Perhaps you guys from Scaniverse could lend a hand in fixing it ?