Cannot sprint, unless using knife or gadget.
There's THOUSANDS of people with same issue on ALL platforms since game release. And EA doing ABSOLUTELY NOTHING. I can't normally play the game I bought. I've heard that on Xbox/ps, resetting controller to factory settings or using another controller helps, but it didnt help me (I'm on xbox). So I guess there's no clear solution so far.
This is absurd. EA, please, do something with your game!
Moved post from the Battlefield Franchise Discussion.
Same thing. Any updates bout the issue? Is it still like this to you?
I Was playing the game the day before no problems but now that I play I can't sprint with a weapon out, have to have melee out or gadget to sprint. It's pretty frustrating because from my understanding of reading about it, this was an issue months ago that still haven't been resolved. Can you guys please do something about it because at the moment the game is unplayable for me and I'm sure I'm not the only one that has this problem
Hello, there is a persistent issue with the Pro controller and its use in the game. I am unable to use spring while holding a weapon. It works fine with holding equiptment or having a knife out, but once a weapon is out it just does not work. Swapping to a normal controller works fine, its just the Pro controller. My question is, whats the point in paying $200 for a Pro controller if it can't even be used on your game?
There are other forums where other players have complained about the same bug 2 months ago and it is still out. What can be done to fix it? Even the forward sprint doesnt work while weapon is out.
I find it funny that we post the same issue, yet you posted a month ago and still have no replies at all... wheres the customer service?
Here's a bump. Fix this bug please, I can't play anymore
Go to settings - controller - edit settings - controller tuning - Controller triggers LT dead zone 5, RT dead zone 5
Community ManagerHello everyone,
Thank you all for your reports. I've merged some posts here to avoid multiple discussions about the same issue.
If anyone is still running into this issue, please try the following workaround provided by greyiztoxic :
In the meantime, we've passed along the feedback to the team.
