Crossbows firing on loading animation?

[ssarasin]

I was trying out a Warforged Artificer over the weekend and noticed that with the repeating crossbow that it was actually firing on the loading animation instead of the firing animation. Has anyone else come across this, or is it just me?

It seems that it happened after I had charged up and fired my rune arm. It was working correctly before that, and then once I fired the arm, the crossbow animations were swapped on when it actually fired the bolts.

After a little testing, it seems that if you swap to a different weapon and then back, the animations would go back to normal and it would actually fire on the correct animation. But once you use the rune arm again, the animations were once again swapped.

I tried to bug report it, but I wasn't actually able to submit the report. (It kept telling me that I needed to fill out the form completely, even though I had everything filled in...)

So I thought I'd post here to see if anyone else had run into this, and if it has already been submitted as a bug?

[Tenkari_Rozahas]

this same topic has been posted several times already, so yes people have been running into it. myself included.

[Dungnmaster001]

I was trying out a Warforged Artificer over the weekend and noticed that with the repeating crossbow that it was actually firing on the loading animation instead of the firing animation. Has anyone else come across this, or is it just me?

It seems that it happened after I had charged up and fired my rune arm. It was working correctly before that, and then once I fired the arm, the crossbow animations were swapped on when it actually fired the bolts.

After a little testing, it seems that if you swap to a different weapon and then back, the animations would go back to normal and it would actually fire on the correct animation. But once you use the rune arm again, the animations were once again swapped.

I tried to bug report it, but I wasn't actually able to submit the report. (It kept telling me that I needed to fill out the form completely, even though I had everything filled in...)

So I thought I'd post here to see if anyone else had run into this, and if it has already been submitted as a bug?

Pretty sure it has nothing to do with the rune arm though since I was experiencing this at level 1 in the very first quest I ran. I didn't bother trying to test it but it seemed to me that it only happened if I tried spamming the attack key instead of either holding it down or doing slightly slower clicks. I figured I was just trying to fire faster than the animation could keep up and caused it to get out of sync.

[Letrii]

Pretty sure it has nothing to do with the rune arm though since I was experiencing this at level 1 in the very first quest I ran. I didn't bother trying to test it but it seemed to me that it only happened if I tried spamming the attack key instead of either holding it down or doing slightly slower clicks. I figured I was just trying to fire faster than the animation could keep up and caused it to get out of sync.

It happens when holding the button down too.

[Beddgelert]

I noticed my crossbow likes to fire randomly while I'm running, too. It's not been a huge deal so far since I can reload on the run, but I haven't been in any large-scale fights yet either. It would stink to have that delay, however slight, when faced with a mob.

[Dungnmaster001]

I noticed my crossbow likes to fire randomly while I'm running, too. It's not been a huge deal so far since I can reload on the run, but I haven't been in any large-scale fights yet either. It would stink to have that delay, however slight, when faced with a mob.

Actually from what I can tell that happens when the animation is out of sync. It's not actually firing, it's reloading but since the animations aren't synced it looks like it fired. If you fire a shot and don't reload after a min or so it auto reloads for you but when the animations are backwards it doesn't look like it is.

[Cordovan]

This is being added to the Known Issues list for when U11 is released, and we hope to fix it soon. In the meantime, unequipping and re-equipping the repeater can help, at least temporarily, although it should be noted that this is essentially a display issue, in that the reload and fire animations are getting reversed, so it isn't actually impacting damage or to-hit.

[Shade]

This is being added to the Known Issues list for when U11 is released, and we hope to fix it soon. In the meantime, unequipping and re-equipping the repeater can help, at least temporarily, although it should be noted that this is essentially a display issue, in that the reload and fire animations are getting reversed, so it isn't actually impacting damage or to-hit.

It actually does effect DPS in a way.

Because when it occurs, if your not actively attacking, but appear to have your crossbow loaded and at the ready. The next monster you face, you will fire, and get no damage until the reload animation.. Thus slightly delaying your intiial shot, and reducing your initial burst dps.. If not your longer sustained amount.

[ckorik]

It actually does effect DPS in a way.

Because when it occurs, if your not actively attacking, but appear to have your crossbow loaded and at the ready. The next monster you face, you will fire, and get no damage until the reload animation.. Thus slightly delaying your intiial shot, and reducing your initial burst dps.. If not your longer sustained amount.

I'm not convinced - although I don't believe in many of the things you think happen in a fight. If movement and such were always working correctly - we wouldn't have mobs that are stunned/paralyzed that continue to fight/etc. It's pretty obvious that things happen on the server and then are sent to our computer - and what we see is only an approximation of what has happened. Same issue when you have damage/heals/spells land *after* something is dead.

It may affect your perception - but it most likely isn't affecting things server side much at all.

[TheDjinnFor]

It may affect your perception - but it most likely isn't affecting things server side much at all.

What he's saying is that if you think it's reloaded because it showed the reloading animation even though it's not and you go to fight another mob, you'll have to wait for it to actually reload.

[Jacoby]

This is being added to the Known Issues list for when U11 is released, and we hope to fix it soon. In the meantime, unequipping and re-equipping the repeater can help, at least temporarily, although it should be noted that this is essentially a display issue, in that the reload and fire animations are getting reversed, so it isn't actually impacting damage or to-hit.

Hopefully they can fix this one in the first patch as this can be a menace to one's twitch factor.