Forum Discussion
Anyone defending this because it doesn't happen to impact you in your specific circumstance are part of the problem. You allow companies like EA to get away with nasty bugs, and code which upon exit leaves your system in a broken / unsupported state.
It's this same mindset and blind execution of bad code that left a large portion of their userbase with bluescreening machines during their prior attempts at implementing kernal level anti-cheat. I can promise from reading some of your comments, that if that had happened to some people on this thread, you definitively would not have the technical know-how to recover your system. Not that you should have to of course, EA shouldn't be breaking code in the most privileged layer of your OS to begin with.
A quick search shows many many examples of this behaviour, and that's only the people who have managed to make the connection in their heads that EA games are causing the issue, which isn't an obvious conclusion to most because it's ridiculous. I'll link just a few below.
This is a massive issue for those of us with very expensive OLEDs, it has already caused tangible damage. And on principal, even if it wasn't causing hardware damage, no software should be leaving windows in a broken state after executing. It's that simple.
EA needs to address this as a matter of priority.
See:
https://www.reddit.com/r/battlefield2042/comments/18lxc7b/screensaver/
https://forums.ea.com/discussions/battlefield-2042-technical-issues-en/screensaver-wont-come-up-after-exiting-battlefield-series-games/7064554
https://forums.ea.com/discussions/battlefield-2042-technical-issues-en/screensaver-not-working-after-playing-/6861613
https://forums.ea.com/discussions/apex-legends-feedback-en/feature-request-allow-screensaver-on-pc-after-being-disconnected-/8589696
About Battlefield 6 General Discussion
Recent Discussions
- 48 minutes ago
- 58 minutes ago
- 2 hours ago