After testing this a bit more, the consistency on being able to reproduce this issue may be due to connection or server location.
I can consistently reproduce this issue on both PC and Xbox Cloud on a private match of “The Pit - Free For All” with my Matchmaking Region set to NA-West, where my ping is 4ms on PC and 1ms on Xbox Cloud.
I also tried NA-Central and had the issue occur with only a single arrow on PC and none on Xbox Cloud.
Tried NA-East and did not have the issue occur on either PC or Xbox Cloud.
Tried Europe and had the issue occur a couple times on PC but not on Xbox Cloud.
To be clear, not having the issue occur during some of those tests just means that it did not happen within a reasonable amount of time, as I’m sure the issue would happen eventually within those sessions.
So, this is either consistently reproducible on NA-West for me due to having low ping to those servers or it, for some (unlikely) reason, occurs on NA-West more often than other regions.
@Flak I hope this issue can be reopened and that these extra details may help QA reproduce the issue.
Again, to be clear, how to reproduce this issue and what to look for (what the issue is):
Select “The Pit - Free For All” (4590-4493-7113), set to Private, play. (Can be other maps but may be less consistent.)
Start the match once loaded in and pick up a Shockwave Bow from the south-east weapon spawners near the Random Loadout sign.
Drop down into the pit and keep firing arrows, the issue may occur during partial or full charges. (A full charge occurs when the bow draw animation completes, the arrow lights up and the screen flashes. A full charge can be held. Tested mostly by firing full charges without holding, so firing as soon as the screen flashes.)
When the issue occurs, sounds will be delayed/broken (most noticeable when a full charge is held) and the arrow will land below the shown arrow path/marker or the charge effect (shockwave/grapple/etc) will not trigger if fired before the delayed/broken sounds end.
This issue will not occur on every arrow, only some.
If this issue does not occur before a reasonable amount of arrows are fired (say, 50, though that might not be enough in some cases, one test where it happened cut close with it happening on the 42nd arrow fired), try a different matchmaking region or with lower ping. For me, this issue occurred most (usually with <10 arrows fired) on NA-West where I have low ping (<5ms, in-game latency meter showing Ping: 0).