HUD category in Settings + Minimap size
Anyone else experience this? Go to Settings / HUD Try to leave Settings page pressing ESC You are stuck on this screen unless you select a different settings category and the press ESC While in HUD, changing minimap size to Large and then trying to change again to other size - stuck. Minimap size seems too small now.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.Xbox Series X performance drops every other match
Product: Battlefield 2042 Platform:Xbox Series X Please specify your platform model. Microsoft Xbox Series X Are you using any software with an overlay? No Which part of the game is the issue happening in? Multiplayer Which part of the mode? Conquest Please select your region Europe On which server did this happen? Unknown When did this happen? (dd.mm.yy hh:mm) 19.11.21 19:10 Summarize your bug Performance drops to an unplayable level How often does the bug occur? Occasionally (10% - 49%) Steps: How can we find the bug ourselves? Happens every couple of matches on Xbox Series X. So to find it would be just to play the game on Series X for a few matches. What happens when the bug occurs? Frame rate drops below a playable level What should be happening instead? Consistant performance around the 60fps mark The performance shown in the video is what I experience during normal gameplay. I have also updated my Series X to the latest November update. Unable to attach file so here is the video link: https://youtu.be/3NihQuRMeOsBF2042 and BF6 Beta Crashing
Hi, I have been a long term player of BF, I am encountering a problem which seems to have started when secure boot was required, I have analysed crash logs both from the bf6 beta and 2042, and windows using Grok. I am being told the issue is with EA anti cheat, I have gone through everything that my ai has suggested all the way to doing a clean install of windows and redownloading the game, the problem persists. I have disabled XMP and am not using any other over clocking of GPU or CPU, I have run mem checks as well which were all clear. I have rolled back my driver to 566.36, first removing current drivers with DDU in safe mode. I have followed all other ideas that have helped others in EA forums and Reddit with no joy. I will paste the crash logs and Grok's recommendations below. My system specs are as follows; 13th Gen Intel(R) Core(TM) i7-13700K (3.40 GHz) Corsair Vengeance DDR5 32.0 GB (31.8 GB usable) Asus TUF RTX 4070ti Please Help, I really want to sort this out so i can play BF6 at launch. I have gone through the below list of recommendations, including repairing ea anti cheat. ................................................................................................................ The WinDbg analysis you provided for the IRQL_NOT_LESS_OR_EQUAL (0xA) bugcheck clearly points to eaanticheat.sys as the culprit, which is the driver for EA AntiCheat, used by Battlefield 2042. This driver is causing the crash by attempting to access invalid memory at a high IRQL, likely due to a bug, incompatibility, or corruption in the anti-cheat system. The process name BF2042.exe and the module eaanticheat.sys in the stack trace confirm this is tied to the game’s anti-cheat mechanism. Below are targeted steps to resolve the issue, tailored to the minidump analysis. Steps to Fix the Crash Uninstall and Reinstall EA AntiCheat: Since eaanticheat.sys is the failing module, reinstalling it can fix corruption or compatibility issues: Open the EA App or Steam, locate Battlefield 2042, and uninstall the game. Navigate to C:\Program Files\EA Games\Battlefield 2042 (or your game install directory) and delete any residual folders, including the EA AntiCheat folder if present. Go to C:\Program Files (x86)\Origin Games\AntiCheat or C:\ProgramData\EA AntiCheat and delete any EA AntiCheat files (if you have admin access). Reinstall Battlefield 2042 via Steam or EA App. The EA AntiCheat service will reinstall automatically. Launch the game to test if the crash persists. Update EA AntiCheat Manually: EA occasionally releases standalone updates for their anti-cheat system. Visit the official EA website or check the EA Answers HQ for any patches or updates for EA AntiCheat specific to Battlefield 2042. If no updates are available, ensure the game is fully patched (Season 5/6 updates may include anti-cheat fixes). Run the Game and AntiCheat as Administrator: Missing permissions can cause anti-cheat drivers to malfunction. Right-click the Battlefield 2042 executable (bf.exe or BF2042.exe) in the game folder, select Properties > Compatibility tab, and check Run this program as an administrator. Do the same for the EA AntiCheat executable if accessible (e.g., C:\Program Files\EA AntiCheat\eaanticheat.exe). Disable Conflicting Software: EA AntiCheat can conflict with other software, especially antivirus, firewalls, or monitoring tools (e.g., MSI Afterburner, Discord overlays). Add exceptions for Battlefield 2042 and eaanticheat.sys in your antivirus (e.g., Windows Defender, AVG): Windows Defender: Settings > Windows Security > Virus & Threat Protection > Manage settings > Exclusions > Add bf.exe and eaanticheat.exe. Disable overlays: Steam: Properties > General > Uncheck Enable the Steam Overlay while in-game. Discord: User Settings > Activity Settings > Game Overlay > Turn off. Temporarily disable third-party antivirus during gameplay. Update Graphics Drivers: While eaanticheat.sys is the primary issue, GPU drivers can exacerbate instability. Update to the latest version: NVIDIA: Use GeForce Experience or download from NVIDIA’s website (avoid 531.xx series; 577.00 is stable for Battlefield 2042). AMD: Use AMD’s Auto-Detect tool or Drivers and Support page. Perform a clean install to remove old driver remnants. If crashes started after a driver update, roll back via Device Manager > Display adapters > Properties > Driver > Roll Back Driver. Test and Stabilize RAM: The memory address 00007fffffff0000 suggests a potential RAM issue. Run MemTest86 (download from their website, create a bootable USB, and run 4+ passes) to check for errors. If errors are found, replace faulty RAM or lower overclock settings (disable XMP in BIOS or reduce frequency, e.g., from 4000 MHz to 3733 MHz). Run System File Checker (SFC) and DISM: Corrupted system files can cause driver issues. Open Command Prompt as Administrator and run: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth Restart your PC after each command. Update Windows: Ensure Windows is up to date (Settings > Windows Update > Check for updates), as outdated kernel components (e.g., ntoskrnl.exe) can cause compatibility issues with anti-cheat drivers. Check for Overheating: Overheating can cause driver instability. Use HWMonitor to monitor CPU/GPU temperatures during gameplay. If temps exceed 85°C, clean fans, reapply thermal paste, or adjust fan curves. Update BIOS: An outdated BIOS can cause driver compatibility issues. Check your motherboard manufacturer’s website for the latest BIOS version and update carefully per their instructions. Reinstall Windows (Last Resort): If the above steps fail, a clean Windows install can resolve deep driver or system conflicts. Back up your data and use Microsoft’s Media Creation Tool to create a bootable USB for reinstallation. Additional Notes Bugcheck Details: Arg1: 00007fffffff0000: Invalid memory address accessed. Arg2: 00000000000000ff: High IRQL (0xFF), typical of kernel drivers like EA AntiCheat. Arg3: 000000000000000a: Indicates a write operation violation. Arg4: fffff800a70f155c: Instruction pointer in ntoskrnl.exe, but the root cause is eaanticheat.sys per the stack trace. SYMBOL_NAME: eaanticheat+31370b7: Confirms EA AntiCheat’s involvement. Community Reports: EA AntiCheat has caused similar crashes in Battlefield 2042 and other EA titles (e.g., FIFA). Check EA Answers HQ or Reddit (r/battlefield2042) for recent reports or patches. Some users report that reinstalling the anti-cheat or rolling back GPU drivers resolves the issue. System Specs: Please share your CPU, GPU, RAM, Windows version, and whether you’re overclocking. This can help identify compatibility issues (e.g., specific GPU models or Windows builds). EA Support: If the issue persists, contact EA Support with the minidump file and bugcheck details. Reference the Report Id: 9ce55326-22b6-467d-a82f-e9e3a5a117e1 and mention eaanticheat.sys as the failing module. Next StepsStart by uninstalling and reinstalling Battlefield 2042 to refresh EA AntiCheat, then ensure your GPU drivers are updated or rolled back to a stable version. Test RAM with MemTest86 to rule out memory issues. If you need help analyzing further minidumps or performing specific steps, let me know your system specs or any new error details!Does this resolve the issue, or do you need assistance with a specific step?SolvedScreensaver not working after playing.
Product: Battlefield 2042 Platform:PC Please specify your platform model. PC AMD or Nvidia Model Number Nvidia Geforce RTX 3070 Enter RAM memory size in GB 32GB Are you using any software with an overlay? No Which part of the game is the issue happening in? Game Menu In which game menu were you when the bug occurred? none Please select your region North America On which server did this happen? When did this happen? (dd.mm.yy hh:mm) 11-13-21 Summarize your bug After exiting the game my PC's screensaver won't go back on. I have it set to go into screensaver after 20 mins of non use. it's been 4 hours and it hasn't gone into it. This happened during the beta.The only way to get it back is if you reboot How often does the bug occur? Every time (100%) Steps: How can we find the bug ourselves? Set your screensaver for 20 mins of non use Play the game then exit or crash and wait 20 mins What happens when the bug occurs? The screensaver doesn't activate What should be happening instead? screensaver should work Windows Screen saver doesn't work after playing the game.missile and bullets not hitting targets
Fix your **bleep** game. Bullets flying through walls, missiles and bullets not hitting other people and choppers. whats going on? and you nerf the chopper. runner over opsticals and getting throwen up in the air. kill feed not working good enough. getting killed with no info at all. inviseble walls, people can lie on the ground and you are not able to hit them because of some detail on the map, debree and stuff.?Weird death glitch
So I got killed and hit revive. After seeing it wasn't going to happen in time I hit the button to die. That annoying flatline noise was stuck on and I wouldn't die. I tried several times but just laid there for 5 full minutes doing the princess wave and then someone revived me. I've only seen it that one timeLis’s g-84 missile is bugged on solo/co-op game modes
Lis is my favorite specialist to use and I can only play solo games due to my bad internet but what really drags me down as a specialist for her is after a few times using the g-84 tgm the camera gets stuck to the ground and you won’t be able to see and guide the missile and redeploying won’t fix it either nor using another tgm what’s even worse is it carries over to a vechile where the camera will still be stuck to the ground and you won’t be able to see to drive the vechile/air vechile I’ve tried switching vechiles and redeploying but it still doesn’t fix it and I’ve tried switching to a different operator to see if it at least fixed the vechile issue but it doesn’t and it is still bugged if I switch to a different class and then switch back to lis to see if that fixed it but it doesn’t work the only fix I know is to leave and start a different game can this bug please be fixed or can someone give me a way to fix it without leaving the game?Mouse input choppy bug / Controller is smooth.
Mouse input makes the game look low fps / bad frame pacing / judder. But on controller this issue isn't there. Use a controller and the difference is immediately noticeable. Not related to mouse HZ or DPI. Mouse input is not affecting frame times or stability (maybe).