Hi EA_Shepard, good to see the CMs are still watching this thread 🙂
A bit disappointing to see the focus on a workaround instead of the root cause though...
Do you have any early ideas what might be behind it, or a chance of a proper fix in an upcoming BF6 patch?
I know you’ve got a lot going on, but even a small sign that this is moving toward a real solution would mean a lot 💖
Community ManagerFRYKIKZ Hey, I wish I did have better news on this end. I know it is being looked into still but I cannot say if or when a patch will be pushed for it. I have seen so many different workarounds that make sense and don't make sense that it is harder to pinpoint the root cause of this error. I have seen it caused by issues that don't even relate to the game which is odd. It's on my docket of feedback that I am sending over later today though.
I never had issues with the game prior to the Season 1 update. So, not sure what changed since then. I have tried every fix, but this game is unplayable.
EA_Shepard thanks for the clarity, it’s much appreciated!
Glad to see that updates are being forwarded to different parts of the team.
I hope the geeks responsible for Frostbite gonna take a look at it ;)I’m hoping that among the things we talked about here, some of them gonna lead to a solution.
Again thanks for the info, please don’t forget about us here and please update us whenever you can 💚
The solution is pretty simple for EA but they haven't done it.
They need to stop the game from calling for FSR when it's not active.
why is there a call to FSR happening if FSR is not enabled, or even supported on user's hardware?
Super question that is not being answered
