Battlefield 2042 has been around for a while now, but it is still treating us to a range of new and unexpected errors, the latest of which is the Battlefield 2042 Not Set bug.
This is an issue which has affected large numbers of players regardless of platform or location. So what is it, and how do we fix it? Here's what we know.
How To Fix The Battlefield 2042 Not Set Bug
If you are suffering from this bug, you are probably wondering what you can do about it. And the answer, at the time of writing, is not all that much. But here are your options:
- First of all, stick to the pre-programmed button mappings. This is the simplest and easiest way to avoid the bug from appearing.
- Otherwise, keep checking for updates. EA has already confirmed that it is aware of the issue, and is planning to provide a fix for it via a "future update". They haven't specified a timescale on this, but if an update becomes available, install it as soon as possible, and see if this remedies the issue. The next one is apparently scheduled for early July, but it's uncertain whether it will include a fix for this glitch.
It's worth noting at this point that while the remedy is more of a workaround than an actual fix, EA says that the menu buttons do still work, even when you see the <NOT SET> message appear.
But what is the error, and why has it appeared?
What Is The Battlefield 2042 Not Set Bug?
As you are probably already aware, the not set bug is appearing in some in-game menus. Instead of saying what they are meant to, menus either display <NOT SET> or some placeholder text.
The error itself appears to be linked to update 1.0 which introduced hundreds of changes, bug fixes and improvements. Unfortunately, it seems that a few glitches have appeared as well.
The error seems to be impacting players who have changed the button mapping on their controllers. It's unclear exactly why this is happening, but as we highlighted above, reverting to standard button mapping does seem to mitigate the problem.
It will only be fully resolved when EA releases a patch for it, so it's really important to keep an eye out for any updates. Hopefully, it won't be too long before this issue gets resolved.