Clearly there’s plenty of evidence. Has this been elevated to the dev team? @NianticModKKI @NianticModKIC @NianticModSY @NianticModHF
@TheBigPineappL
Thank you for following up.
Rest assured that we’ve forwarded the issue again with the relevant team for further investigation. If there is any additional information we can share on this, we’ll do so on this thread.
1 Like
Wanna guess where this particular SP hit went to? 
(This is on v113)
Even the number is off screen. If the points had not gone up, I wouldn’t even think it hit the Rathian despite you point-blanking its head.
You’re doing the lords work documenting this. It’s incredibly frustrating when this happens, especially on 10* runs. Hopefully they actually do something soon. If it wasn’t broken on release, how TF did they break it afterword? smh
1 Like
The points did go up: 19044.
Definitely not a damage befitting a direct head shot at +100% damage.
Maybe I could have aimed higher, but then the hitbox might just say no anyway
I believe somewhere down the road they had to optimise the way the hits work so that it takes less computation/processing to register and therefore reduce the load on the mobile devices, but that means compromising precision.
It’s like the difference between ray-tracing vs non-RT lighting: One is computationally heavier because of its attempt at simulating physics compared to the other.
Of course, I don’t know exactly what happened behind the scence (I most likely never will), but given how the game has been quite smooth despite of all the bells and whistles it seems to be putting on, I believe some forgettable corners had to be cut and unfortunately it affected ranged weapons negatively.
I hope the devs can find a solution for this while maintaining the lightweight processing though. It’s never an easy work, I believe.