devtrackers.gg
Amazing action! About the sliding, do you like the way it works right now? I got some feedback that it's hard to trigger or doesn't do so 100%.
Amazing action! About the sliding, do you like the way it works right now? I got some feedback that it's hard to trigger or doesn't do so 100%.
I think it's okay this way. Would be cool if it could give some benefits like moving faster or something when sliding down hills (yes I played too much apex)
We'd like to make sliding speed/length variable based on terrain angle, hopefully we can take a look at it soon.
I wish it was easier to trigger, the keybinding is hard to do while running and shooting and all the other things.
Alright, so what do you propose, different keys or easier to trigger (like simply holding crouch instead of double tap)
I'm honestly not sure, but I feel like it was easier in battlefield 1? It's all too mixed up for me.
It's also a struggle for us to find the best approach, since there are already so many button mappings. More key bindings means more freedom but also a more complex options screen and code. It will always be a trade off.
Currently, the sliding mechanics are perfect. But I can’t speak for everyone and I play on Xbox with a controller.
Alright good to hear, I think the key bindings might be more on a problem on pc but I'll gladly hear from other console players who think triggering sliding on a gamepad is problematic.
I’d like to jump in and offer some feedback. I’ve been playing since BFV released, and I love sliding. I play on Xbox and it doesn’t seem to always trigger. It used to be really consistent when I quickly double tapped B, but then when firestorm dropped it seemed like I had to make two quick and distinct hard button presses to trigger it, I even remember asking my regular squad mates if sliding got broken. Playing last night, it seems like it has gotten better, but it doesn’t quite feel like it used to, though at least it triggers on double tap again, so that’s cool.
Thanks for your feedback. Do you experience high ping when playing firestorm? The sliding functionality not working 100% might have something to do with high latency, something I should investigate.
When it does work, do you feel like the double tap is a convenient way to trigger it?
My ping is generally in the 30s at the high end. When it does work, I like the ability to double tap quickly, but that could be just because I’m used to it by now. Also, I like the ability to long hold B to panic drop into prone, it just feels natural for me. Like, when I’m sliding around, if I start getting shot at, I can just long press the 2nd tap of B and I’ll transition to prone, which has been a thing going as far back as I can remember in most shooters I’ve played on Xbox. I feel like changing the panic prone could frustrate people.
Good to know, I'll investigate soon why it doesn't trigger 100%
Preface: This is all my opinion.
I'd almost want to try it in reverse: press once to slide (only if you're sprinting) then press again to stop sliding. So a double tap while sprinting would quickly put you into a crouch run, while just hitting it once would put you into a slide which leads into a crouch run if still holding forward at the end.
Hold to slide would interrupt the hold to prone feature, which I personally use exclusively to initiate prone.
Sliding does feel more inconsistent than BF1 currently, but I feel like that's because a single button tap let you slide, while in BFV it feels like it could either be contextual (sometimes I slide from hitting the button once, other times it just throws me into crouch sprint) or initiated via button presses that can often feel too clunky to do when you need it.
Sliding is a quick maneuver, it needs a reliable way to activate that can be done quickly and relatively. Crouch run is a conscious decision, and doesn't necessarily need an instant way to activate it all the time, especially since sliding can lead into it.
I agree that sliding should be a quick maneuver and that it's currently not easy enough to use it. We'd like to improve that, using all these feedback when we get back to this feature. Thanks :)