Hi, I’m having a problem with Overclock in Ingress. Portals with overclock unlocked after Niantic - Scopely separation, has problems with VPS calibration. Testing VPS on the same wayspots via Scaniverse (its geospatial browser tool) works perfectly. In Ingress it doesn’t work. Restarting or even reinstalling Ingress app don’t fix problem. In my opinion meshes look good. Portals which had unlocked overclock before separation works as well as before. For now I know only 4 cases with this malfunction. I’m looking for any information about that.
Thank you.
2 Likes
I met the same situation here. The new VPS portal can’t be overclocked in ingress, but vps test check is ok and mesh looks good. OC cannot be performed in ingress on that portal as the scans are all recent. The other two portals can be OC-scanned because they were previously activated (though the attempt failed back then), and they have recently been successfully re-scanned and reactivated.
1 Like
I recently requested activation of one portal which had only experimental status and I tested OC today - it worked. I have yet to test some other newly activated locations.
But I do concur there are issues in the process, as it also happened to me a lot of times that calibration fails on previously working locations.
Bonjour , une réponse a se sujet serai la bienvenue de la part de Niantic Spatial !!!
There is bug with the selection of the data to match an Ingress overclock attempt to. Try other portals in the vicinity of your candidate, one might work. I’ve reported this as Ingress Bug, after a week with no answer posted it to Reddit (Reddit - The heart of the internet) and scaniverse community (Test scans with scaniverse succeed, localization with Ingress fails - Bug Reports - Niantic Scaniverse Community)
On Reddit others confirmed the issue and they also found portals where scaniverse worked but for Ingress overclock to succeed one hast to scan a different portal.
2 Likes
Wow, I checked this idea and it worked! Two portals calibrate their VPS on object nearby, activated previously. I can overclock now but it still doesn’t fix the problem, but it is big clue for Niantic to fix this issue. Thank you very very much.
1 Like
I’m glad to hear I’ve been of some help. And thanks for the feedback, which confirms my suspicions. I have a few affected portals in my area, including some that were working normally before. Perhaps this is another clue to resolve the issue.
Are there any moderators or Niantic staff members here who can help push for a solution? This bug has been known for weeks and seems to affect only Ingress (not Scaniverse)!