Forum Discussion
ETA is probably S3 patch on May 12th. Could possibly also be April 28th, if there is a patch planned that day. Doesn't seem like it's part of the patch on Tuesday, according to today's patch notes.
That would be a real shame. I think they could still include the fix in the next patch if there was positive feedback in BF Labs.
- Okinouko1 month agoSeasoned Hotshot
Nah i don't think it's a good idea, we have waited for so long, we can wait a few more days to make sure the fix is solid, they need to make sure it's not breaking anything else in the game and Dice is really good at triggering new issues by fixing past ones.. so let's give them some time, will be good for everyone.
- Soulshot961 month agoNew Adventurer
You say that like they QC these patches at all lol. **bleep** near every one since launch has broken just as much, if not more than it's fixed.
Them testing this in Labs is probably the absolute closest thing to QC any of these changes ever get as is.
- Okinouko1 month agoSeasoned Hotshot
This isn't just a one feature/setting fix, like the defib or shooting dispersion.. This Frostbite engine got a pretty complex mouse input-image rendering pipeline compared to Unreal Engine 5 or other ones. Them deciding not to implement it right away is always better than rushing it no matter their past mistakes, you can't deny that. It's still a huge shame they didn't adress that obvious problem since launch, this stays pathetic of course.
- krismate1 month agoNew Adventurer
Due to validation process and general development patch cycles, the patch on Tuesday was likely finalized and in the bag several weeks ago ready for validation etc. so they can't just add something in at the last minute without having to re-test/re-validate, which would've delayed the upcoming patch. I agree sucks not to get it yet, but at this point, I'm willing to be patient, knowing a fix is happening soon.
- zeitlosFuhrer1 month agoSeasoned Traveler
6+ months is pretty patient…. Ha. Especially for a game most if us paid for.