Since the 1.13 Update the FFB on my wheel has gone back to how it felt in the beta, choppy and unpredictable, especially in the first 10 degress of rotation. This was fine on a race prePatch and is n...
Ideas
Cpayne32 I’m sure there are well established processes in place for testing prior to release. But we are not talking about some crazy edge case or a random device that was unexpectedly effected. The peripherals that the patch broke are precisely the devices it was intended to support on the most widely used platform. The issue also requires no effort to replicate as it affects every race as soon as the game starts. This should have been caught immediately if they did any sort of proper testing, so forgive me if I lost faith in the process.
In any normal situation, if one of the primary reasons for the patch was not only not fixed, but also made the intended devices unusable, it should have been rolled back immediately, as that indicated a fundamental failure. The complete lack of urgency and transparency just means EA can’t be bothered to accept their mistake and take the necessary actions.
I was willing to be understanding a week ago but this has gone on way too long. There’s simply no reason for something that users were able to diagnose in 5 minutes to take this long to fix.
The issue is that while it is possible to rollback an update on steam, consoles isn’t as easy and could result in save data being lost if not backed up or compatibility issues with the servers.
This isn’t me defending EA but the issue is wider than logitech wheels so a solution has to potentially be found for each brand which could explain the delay.
Featured Places
