[BUG] Max range deployments are not max range, CALL FOR ACTION
edited January 2020 in App Feedback (Archive)
When you do max range deployment, the resonators end up around 24 meter range instead of the wanted 40 meters, as witnessed by the images below.
My test portal position: 60.446448, 22.403271
Please test locally and report back.
Would be interested if it is affected by your latitude or not.
Tested on v2.38.3 , Android 9, LG G7
Images in order:
1. before deployment, max range
2. right after deployment
3. standing on top of resonator, showing distance to portal
Post edited by Hiivis on
I can confirm this issue.
And you're not drifting?
Absolutely no drifting, we have multiple cases confirming this behaviour
More data below done in similar fashion as before
1. max range
2. deploy from max range
3. distance from top of deployed resonator
You can actually see the reso ending in totally wrong distance while deploying.
Might need a video to see how the change is happening. I tried to replicate it and resonator appeared where I was.
Yes I kinda feared this would happen. Sure, will provide a video. Btw what is your latitude?
Meanwhile here's a table of measurements I did.
Btw what is your latitude?
I'm in LA where they do all their testing. Things like the faction avatar ring look perfect for me unfortunately.
Can confirm the similar findings. Deploying resonators at max range will place them somewhere between 23-25 meter range.
My latitude: 62.230
I was traveling over the holidays and I noticed that at northern latitudes I could take actions quite a bit outside of the drawn ring, e.g. in Stockholm (59.3° N) I could hack/deploy at nearly 1.5x the radius of my ring. Whereas at home in California the ring pretty much reflect the actual range at which I can take actions.
My suspicion is that they're drawing the action circle and possibly also the resonator distances at a fixed visual distance, whereas the underlying map tile uses a Mercator projection or something like that that stretches things out to be further apart than they actually are.
When you stand with your ring at the portal location, how far is that portal in the real world? It would be interesting to actually measure it.
Sounds like NIA needs some (more) testers abroad.
There is no change, the deploy is short from start to finish. Please see the video below.
Here is another video showing the bug happening. Resonators appear much closer to the portal than the player location.
Yeah, that looks horrible. I'd be interested to know if the resonators are actually at the 39m mark and being misrepresented on the map, or whether the resonators are at the shorter range.
One test would be to get someone from the opposite faction to stand on the portal and fire different levels of resonator to see which hit. If an L8 doesn't hit, then they really are at the 39m range. If it does, they're withing 30m.
The real world portal distance at "prime 40 meter range" is exactly 40 meters.
If you want to actually deploy at the 40 m mark, you'll need to stand as far from the portal as you can, while still being able to deploy. This will likely be beyond the orange circle (see my note above).
If both the orange ring and the resonators are incorrectly scaled, then the resonator will still not be drawn where you are standing, but it will virtually exist there (I suspect the back-end calculations are correct). You could verify this with Perringaiden's ultrastrike test.
It's also likely that the display is warped anisotropically, i.e., there's more distortion east-west than there is north-south, which may explain the varying measurements in your chart above.
For what it's worth, when using the old classic avatar, the ring scales exactly to 24 meters. I don't think this is just a coincidence. However it doesn't affect actual action range (still 40 meters max ), it is just a visual bug.
I would primarily attribute the variation to rather bad GPS conditions at the moment, also it's somewhat hard to get exactly on the resonator given the 3d nature of the view and short distances at the low end, which results in larger errors.
I will test this later by flipping the portal green that was used to measure values for the range table. Then use different level ultras on it from center to see what gets hit.
More data from near equator this time, the deploys (as expected) don't fall short but go long, observed range about 50 meters at 1.3N latitude.
1. at max range
2. after deployment
3. on top of resonator
So from the looks of it, it normalizes around LA/SF and is distorted long north and short south (towards the equator).
This issue has been around for ages. Heres one topic from june 2019 with Prime/Redacted side-by-side comparison😬
The other way around? But yes, it really looks like it. And this also could affect gameplay (defense) since different deplo distances do make a difference.
Is there any screenshots of portals that were deployed in redacted at max range then viewed from prime to compare with?
It seems that the distance of resonators follows the basic Mercator scale factor.
If we assume that the length of max deployed resonators at the equator is 50m (as shown in the image pasted above), we should be able to calculate the distance anywhere with 50m * cosd(latitude). (Edit: formula fixed)
This gives us the following example max resonator lengths:
Equator = 50m
LA (34°N) = 41m
Helsinki, FInland (60°N) = 25m
Tromso, Norway (70°N) = 17,5m
Longyearbyen, Svalbard (78°N) = 10,5m
Tests done. TLDR, it is only a visual scanner bug tied to player latitude. See images below.
1. firing U8 (range 30m) from center, no damage to 40 meter (visual 24m) deployments
2. standing on top of real R8 (it is visually 16 meters away towards portal), firing U1 (10 meter range), confirmed damage
The problem is the silly new avatar. Revert back to standard prime and it will be fine. The resistance and enlightened avatar circle is just too small. I can't believe this has gone though QA.
Not so, the old avatar does have the same latitude dependant scaling problem tho.
I've noticed this behaviour in Pogo, actually. Was in the UK and I could spin stops that seemed to be out of range, where back in South Africa, I definitely need to be closer. Though Pogo doesn't have a visual ring to go by, the behaviour was enough that I noticed the difference.
Will test locally on Ingress