Original Post — Direct link

This appears to be predominantly latency/packetloss based as the impact is worse the higher the latency across the handful of testers to confirm the issue.

If you're noticing that even fully drawing the bow, waiting more than enough and letting it loose, you may encounter the arrow simply not going anywhere, like you just rapidly clicked fire without pulling back on the bow at all. Though i did get a few sub 50ms players saying on occasion it'll do the same and initially they thought they just screwed up firing it, only to happen it again short time after.

In around the 80ms mark i'd say about 50% of the shots fired are duds, anything much over 150ms.. basically can't use the bloody bow at all. (ping is accurate latency, not what is shown in game which is 20-30ms below the correct latency)

Having just did the vbuck missions, watch a few players even switch weapons after several of their shots landed at their own feet repeatedly.

In all seriousness, please epic, switch STW mode back to PvE client side mode, so we can play the game properly again, this would fix broken malee, failing to jump and climb right, among countless other atrocities that shouldn't occur simply because the server tells the client seconds after the fact "haha, nope you didn't do that!"

External link →
about 21 hours ago - /u/AryssSkaHara - Direct link

As a main of sniper build with three bows, I find this bug very painful