Quick Play Matchmaking Broken
Quick Play matchmaking is broken. After the countdown reaches 0, the screen goes black for a second and the game returns me back to the lobby/menu instead of joining the match. Server Browser works normally and I can join servers manually without problems. Things I already tried: * Enabling/disabling crossplay * Restarting game and EA App * Repairing/verifying game files * Reinstalling EA AntiCheat * Clearing EA App cache * Deleting/resetting Battlefield 2042 config folder * Changing DNS * Flushing DNS * Disabling overlays (Discord, EA, NVIDIA, MSI Afterburner/Rivatuner) * Running game as administrator * Trying different game modes * Network reset Issue still continues. Looks like many other players are having the same matchmaking problem right now.
Breakthrough Returns to Main Menu After Match Found
There is a serious issue with breakthrough on PS5, Xbox and PC. I and others have been unable to connect to a game of breakthrough (offical server) on the main menu. It finds a game, counts down, fades to black and then eventually returns you to the main menu. For me all other game modes work without issue, but others have reported the same bug with conquest. There are two other posts on this forum with the same issue and a post on Reddit where others are stating they're experiencing the same issue as well. I've tested and confirmed the issue on my PS5 (local install & streaming) and Xbox Series X consoles, both with two different accounts and tried uninstalling and reinstalling to no avail. Please can this be looked in to as a matter of urgency. (I literally only play breakthrough) (cm edit updated title for vis)Matchmaking not working.
Yes that's about 20 days. We all understood matchmaking is not working properly or can't play what he want to play. What about EA support? What did they do and is there any info for us ? When will the problem solved? Is there any official patch soon? Or all the players must pay for the BF6?
Broken Matchmaking
Im not doing anyone of your work around again they are stupid and shouldnt be required for the customer to fix the product thats supposed to be WORKING cant matchmake into conquest and sometimes if i do i can only play for 1 game then it boots u to main menu when trying to load into the next game this is not a system issue this is an issue on your end other have the same issue with other gamemodes as well this is clearly an issue on your end
Loadout Notifications
Aww, isn't that convenient? The seemingly only way to contact the actual company we're paying happens to not be working (for ages already by the way). What a shame, now the customers have to talk amongst each others to try and fix EA's **bleep**. If anyone from EA does happen to read this: remove the **bleep** notification icons from the loadout menu, they're bugged out and have become a useless nuisance. Get rid of them. Thank you!2042 server bug
Can yall please fix the servers? Every lobby i try and join goes to black screen and kicks me back to the main screen. Im on ps5. I have uninstalled the game, reinstalled, cleared cache in safe mode, rebuilt the data drive in safe mode, power cycled the internet, renewed the license, etc. No fix.
BF 2042 Conquest only certain maps working
Looks like I'm having the same issue a lot of other folks are having. I'm on PC and when I try joining Conquest only certain maps work for me. If I try to play Reclaimed or Valpairiso I get the map loading music but it goes black after 5 seconds it kicks me back to the lobby. In the beginning I got an error code and the load music would keep playing even though I was back in the lobby. Now I don't even get an error code anymore, it just boots me back to lobby as if nothing happened. It's been very frustrating.VKB Gladiator NXT/EVO
I know this is an old thread, but- I tested my VKB Gladiator NXT/EVO first in Battlefield 6, then in 2042 after seeing they claimed to have “joystick support.” Two things popped up... Problem #1- The games wouldn’t see any button numbers higher than 17, so I remapped what I needed into 1–17 and turned the rest into keyboard keys. Problem #2- The real issue was the thumb mini-stick. When I first tested this out, I was still running my Star Citizen profile that I have used for a few years, which disabled the mini joystick and replaced it with a virtual mouse input. During this time the stick was recognized and worked just fine. The other night I reset everything back to factory, not realizing that the only reason the stick was actually working with Battlefield was due to how I had that mini joystick set up. Once the default axes were reassigned to the mini joystick (X Rotation / Y Rotation), the game started treating my VKB like an Xbox controller instead of a joystick. When I switched that mini-stick back to a virtual mouse inside VKB’s software (which removes X/Y Rotation), BF6 and 2042 immediately recognized the device as a normal joystick again. Took me a while to narrow it down, but this is the root cause for everyone who's had issues running higher end sticks on Battlefield these past few years. Basically for some reason the sticks of an Xbox controller and those two axes for joysticks share the same hardware ID profile. Doesn't matter if it's VKB, Virgil, JoyToKey, or VJoy- if either X Rotation and/or Y Rotation are enabled, it'll come up as an Xbox controller. So, how to fix: In VKB software, disable X Rotation and Y Rotation on the mini-stick and set it to act as a virtual mouse. Alternatively, z rotation causes no issues and can still be used, so if you wanted to instead remap the y-axis of that mini stick to Z Rot, you could. No third-party remappers needed; there are several YouTube videos and guides out there that show exactly how to remap buttons and set up VKB’s virtual mouse if you haven’t done it before. Or if you wanted to get a little more advanced, you could use v joy to create a virtual joystick and joystick gremlin to remap any and all of your BKB buttons to be what you want on that virtual stick. Just make sure when setting it up that you uncheck X Rotation and Y Rotation. I've confirmed that a virtual joystick created this way will not come up as an Xbox controller. Using this method, if you have HOSAS or HOTAS, you can also combine the inputs on both into one virtual joystick, if that's how you wanted to fly. If anyone ends up ever actually reading this and wants help setting any of this up, feel free to message me here or on Discord (Silversquirrel) and I'll happily jump on a call to walk you through it. I can confirm that using the VKBs to fly in both Battlefield titles is pretty epic.
