Is there any way to fix this?
I think using in routes instead of slants is one way people adjust. It doesn't seem to happen constantly so i just deal with it and look for another read... or throw a pick.
It's not a YOU problem, EA cannot figure out their own code. Use drags instead, Slants seem to stop at or around the hash marks after running a partial route.
But hey, they scanned two more players faces, right? You've got some audacity, expecting receivers to run routes in a fatball simulation game that was released 3 months ago. Hopefully by April 2024 they'll have figured out their issues with pass catching and route running, oof. Til then, please don't think about it. BUY MORE PACKS. 😝
The latest patch notes were basically EA Devs admitting they have no idea how to fix these basic gameplay issues. They already rolled back the "fix" for D-linemen snatching too many passes, because it has the unintended ripple-effect of making ALL players drop wide open passes, if/when the QB was under pressure or getting hit. Buggy ass mess. /sigh
peatrick said:It's not a YOU problem, EA cannot figure out their own code. Use drags instead, Slants seem to stop at or around the hash marks after running a partial route.
But hey, they scanned two more players faces, right? You've got some audacity, expecting receivers to run routes in a fatball simulation game that was released 3 months ago. Hopefully by April 2024 they'll have figured out their issues with pass catching and route running, oof. Til then, please don't think about it. BUY MORE PACKS. 😝
The latest patch notes were basically EA Devs admitting they have no idea how to fix these basic gameplay issues. They already rolled back the "fix" for D-linemen snatching too many passes, because it has the unintended ripple-effect of making ALL players drop wide open passes, if/when the QB was under pressure or getting hit. Buggy ass mess. /sigh
People still wait for the slants to run across the field?