September 2020
If you are from pc using a controller and you are econcountering this issue as i am, I found a work around that's actually pretty good, you have to download the latest version of the DS4Windows install everything, and make sure you install the drivers (to make sure you downloaded the drivers go t osettings and on the bottom you should see " Controller/Driver Setup" click on it and follow the instructions)
on the the settings tab on the bottom right click on "ControlPanel", click on advanced, select the "controller (XBOX 360 For Windows)" and click ok.
inside of DS4Windows you have to go to the " Profiles " tab and then click on the profile that you have ( you should only have one and it should be called " Default " ) and click edit,
now in the page that just opened, go to the right in the middle of the page and you should see " L2 & R2 " options where you can change the deadzone, max zone etc...
go to the Anti-dead Zone and put something like 30, (30 works for me you can put what you want), click save on the top of the page, go to the "Controllers" tab and make sure in the
"Selected Profile" there is the Default profile and hit start on the bottom right corner.
If you still have the issue try to open DS4Windows before you open the game, click start and then open the game.
Explaination
Basically i think that when you start pressing the button the game instantly sees that you are pressing it at a 100% and after that part when you press it more the game sees it normally,
the problem is that 100% part when you start pressing the R2 button,
the solution that i've found just makes it so how much you are pressing the button is not how much the game sees you are pressing it,
what the game sees is slightly more then what you are actually pressing, so it skips the part where it thinks you are pressing 100% when you are just slightly pressing it.
sorry for my bad grammar, i'm italian
hope that i helped you!!!
October 2020
November 2020
Same problem on a PC. Regardles of using keyboard or a wheel+pedals.
It is utterly ridiculous. We don't need some improvised community workarounds, rather some fixes, maybe, huh, EA?
November 2020
December 2020
July 2021
Just tried that, and it didn't do a thing for me.
March 2022
I had this issue too and i realized it was because I had a controller (Power A) with a sensitivity toggle in the back by the trigger. My trigger sensitivity was set to midway so it didn't allow the trigger to depress fully. I changed it to the most sensitive setting and it fixed it!
September 2022
It's Sept 2022 and the issue still exists on the PS4. I came on here to see if there was a fix.
October
October
I have this issue as well when I have Chrome open on a 2nd screen that is streaming video. Closing chrome / stopping the stream fixed the random acceleration drop issue in NFS Heat (playing with keyboard) without needing to restart NSF Heat. Perhaps you could try closing any open software / background service you don't need to see if it helps.