I know this is very specific, but it is a pretty popular build and it’s almost unplayable on controller because of this issue.
When I activate crowstorm using swipe (it works fine when i directly cast it) it aims 2-4 meters behind my target, often on the ground, even if there are many other enemies around.
I just encountered this same issue. Sucks that I can’t play this build on my steam deck because of this bug
Doing a little testing and I think I might understand what’s going on. On mouse and keyboard, when you use swipe the crow storm that gets triggered just goes where ever your cursor is as if you were casting crowstorm, so you can have it target the ground a few meters away just like what happens with the bug. Something tells me it’s just not reading the targeting logic and Because there’s no cursor when you’re playing on controller it’s instead targeting a default geographic point. Unfortunately using the right stick cursor doesn’t influence it at all, atleast from what I’ve observed.
TLDR It’s bugging out because it’s a ranged skill being triggered by a melee skill
I’ve noticed the same issue here tonight as well as I just switched over to the crow build.
Switching to legacy gamepad targeting in settings is a workaround until they get it fixed.
You are a GENIUS! Thanks for the suggestion
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.