Javelin Anticheat error (7)(1)
I just redownloaded the game for the first time since launch and am now being hit with "EA Javelin Anticheat encountered an error. Please restart your PC.: C:\Program Files\EA\AC\EAAntiCheat.GameService.exe(7)(1)"" - I've restarted my pc many times - I've done manual reinstalls of Javelin - Redownloaded BF6 twice The small splash screen that says its starting Javelin is the farthest I get. I haven't been able to get farther then that
[BF6] Share Your Experience: Hitreg, Rubberbanding, and Connection Icons
Hey everyone 👋 We’re taking a closer look at reports related to hit registration issues, rubberbanding, and how the current connection warning icons behave during matches. Some players have mentioned that these issues occur consistently for them, and we’d love to gather more real-world in-game examples to help us understand what’s happening in different situations. If you experience these issues regularly and are willing to share screenshots or short videos, your contribution would be extremely helpful. What We’re Looking For 1. Rubberbanding or connection-feeling issues If you see warning icons frequently or experience movement stutters/teleporting: Please share: A screenshot or short video If you’re sharing screenshots, make sure to attach them to your post -- do not embed them. This helps ensure they display correctly for everyone. With the Simple Performance Overview enabled With the Full Network Overlay enabled These help us understand whether the in-game icons match what’s actually happening with your performance or connection at that moment. 2. Consistent hit registration problems If hitreg regularly feels off for you: Please share: A short video showing the moment(s) where it happens With both overlays enabled (Simple Performance + Network Overlay) This allows us to distinguish between true network issues and client-side performance issues that can sometimes appear similar. How to Enable the Overlays Below are the steps for both PC and console players. 🎮 Console (PS5 / Xbox Series) Simple Performance Overview Open Settings in the game menu. Go to Graphics. Scroll to Performance Overlay (sometimes under “Advanced”). Turn it On, choosing either: Simple, or Advanced/Extended (if available) Network Overlay Open Settings. Go to Network, or Gameplay → Advanced, depending on your layout. Enable Network Performance Overlay or Network Graph. Once enabled, you’ll see indicators like latency, packet loss, and connection stability. 🖥️ PC Simple Performance Overview Open Settings. Go to Graphics. Scroll to Advanced. Enable Performance Overlay. Choose Simple or Advanced/Extended. Full Network Overlay Open Settings. Go to Network or Gameplay → Advanced. Enable Network Performance Overlay or Network Graph. Optional PC console command method (Only if you’ve enabled the console in settings.) Go to Settings → System, enable Command Console. Press ~ (tilde) in-game. Use the command: PerfOverlay.DrawFps 1 To turn it off: PerfOverlay.DrawFps 0 How to Share Your Screenshots/Videos Please upload your clips using: Google Drive OneDrive Dropbox Imgur Streamable YouTube (unlisted is fine) Important: Ensure your link is set to public or “Anyone with the link can view.” Private links cannot be opened. If you’re sharing screenshots, make sure to attach them to your post -- do not embed them. This helps ensure they display correctly for everyone. What Happens After You Share We may reply with follow-up questions or ask if you are open to trying a couple of small tests (like adjusting FPS caps or checking CPU usage). This is completely optional and intended only to help narrow down the causes. We’re not making promises about outcomes -- the goal here is simply to gather clear, consistent examples so we can better understand what players are experiencing. How to Participate When posting your report, please include: A public link to your screenshot/video A short description of what happened Your platform (PC, PS5, Xbox Series) Whether the issue is consistent/reproducible for you Thanks to everyone who takes the time to share examples -- it genuinely helps move these investigations forward and improves the experience for all players.
Inconsistent Player Names Make Reporting and Muting Impossible
I’ve noticed a serious issue with in-game chat moderation. Players posting racist or otherwise hateful messages often cannot be reported, because their name in chat doesn’t match any name shown on the scoreboard. It seems that one name might be their platform username while the other is their EA account name. Currently, there’s no setting to unify how names are displayed across chat and the scoreboard. This inconsistency makes it impossible to identify offenders, effectively letting them avoid accountability. It also means I can’t mute them to avoid seeing their messages. Additionally, some players are spamming offensive content by typing one letter at a time to spell out offensive words endlessly. This makes chat unusable and creates a hostile experience for everyone. A consistent naming system, along with more effective chat moderation and muting tools, would go a long way toward addressing this issue.
Time Nudge (TN) issue Megathread
Hello! I've been dealing with issues relating to Time Nudge spikes (can manifest either as high lag or "slow-motion") and high consistent Time Nudge since about Battlefield 2042 update #3.0.0, and these issues have persisted into the BF6 beta, keeping me from pulling the $70 trigger on BF6. I've done research on the causes and "fixes" (though none of them are complete fixes) of the issues caused by Time Nudge, which I'll outline below. Cause: Time nudge, in most cases, appears to be introduced when the CPU can't keep up with the traffic from the server. Time nudge itself is a buffer that waits for the CPU to either process the packets sent by the server or re-sync with the tick speed of the server. This does not, however, mean more powerful CPUs don't have this issue and less powerful ones do - it seems to be almost random which devices have issues with time nudge and which don't: even some consoles have had issues with time nudge in Battlefield 2042. As for it being an internet, location, or router-related issue, I've eliminated those factors by: 1. Changing my ISP and router (for a different reason, but the issue persisted) 2. Using both Wi-Fi and Ethernet (it didn't matter) 3. Even though I live in a major server city, I took my computer traveling out east and still had no dice with fixing the issue on hotel Wi-Fi. The issue is often found in systems whose CPUs have high utilization or are throttling (as is expected), but I've run 2042 and the BF6 beta on 60% CPU utilization well under 80 degrees C with the issue persisting. Your system not getting enough airflow could be an issue causing Time Nudge spikes. From what I've seen, the issue appears both on Intel and AMD chips across multiple generations, including mobile and desktop chips, and across multiple motherboard models as well. It's likely a slight mismatch with something in certain specific CPUs and the Netcode that causes the issues to appear. The issue is not GPU-related: it persists on integrated graphics and both graphics cards I own, and changing graphics settings or turning on DLSS does not majorly affect how severe the issue is. This has been consistent throughout my research into the topic. Additionally, the games usually run with very high framerate and high GPU overhead even when the issue occurs. The issue could be RAM-related in some cases. Tweaking some RAM-related settings in BIOS can relieve some issues relating to Time Nudge. Solutions: The issue can be relieved partially for some devices by lowering the max framerate in the game settings below what it normally . This may give some overhead for the CPU to run network-related processes and Additionally, user-created .cfg files have been circulating that limit CPU usage for the game to only about half of what it would use otherwise. These haven't worked at all for me, but seem to have had some effect in other users' issues. Note that this fix -- pretty much universally -- has been said to not completely solve the issue, but rather alleviate it a bit. For those who have the option, enabling an XMP profile for RAM in your bios could alleviate the issue. Alternatively, adding more RAM to your system could eliminate any issues in the CPU failing to communicate with memory, and give the CPU enough overhead to perform other tasks. Resetting your BIOS or re-installing your OS or game is not a valid way of alleviating this issue, from my attempts at doing all three and anecdotal evidence from other threads. Something I read relating to Time Nudge that seems important to note: "It's an issue with no clear cause and no solution." Everybody's case will be different, and the issue is probably not solvable either on your end or EA's end. As far as I can tell, the only way to completely solve the issue would be to swap to a different CPU, including using a potentially older one. If you have a laptop or a system with a soldered-on CPU, getting a new device to play the game on may be your only option if the fixes I've listed and the ones in the comments don't work. If I missed any solutions (I definitely did), feel free to drop them in the comments. Conclusion: I'm writing this in part to get the attention of EA staff, of whom only one has responded to any time-nudge related thread before (2 years ago). This is an issue that is preventing a not insignificant amount of players from enjoying your game, and one that needs to be solved. This is not an issue for me in any Battlefield game other than 2042 and 6, and not in any other multiplayer game either. Edit 10/25/2025: Just gonna leave an update here - consensus among quite a few posts (here and elsewhere) has shown that if you're having Time Nudge issues on the 60hz servers, playing on the 30hz Community servers is an option. The 60hz servers are just more difficult for the CPU to juggle network traffic with, so a slower tick rate server should alleviate the issue a little. I've bought BF6 and will post the results of me trying those 30hz Community / Portal servers. Something about those servers to note: there has been community pushback against DICE for their decision to make those servers 30hz. While this is a reasonable criticism from a gameplay perspective, a switch to all-60hz servers could end a way for us experiencing this Time Nudge issue to play the game. Due to that community pushback, and assuming the TN issue isn't addressed in a near-future update, you can expect that method of playing the game to vanish after some time. Another thing to note for some users, especially with portable devices: changing power plan settings to not throttle (pick High Performance mode in "Choose a power plan" in Windows search) has had some effect in mitigating this issue with some users I've seen online, especially those with laptops or handheld devices. I will note, however, that altering this did not work for me in 2042 with my laptop.
Battlefield 6 DirectX crashes can only be a problem with the game engine.
Battlefield 6 is crashing with DirectX errors on a wide range of systems. This has been happening since release and appears related to the game engine under heavy load. It needs an official fix. Many players are reporting the same behavior across different hardware and drivers. Some players say that the problem appears to have existed since Battlefield 2042. I can't confirm that myself, as I haven't played BF2042 for very long. My system: - CPU: [I7 14700K] - GPU: [RTX 3090] - RAM: [DDR5/ 64gb / 6400mhz] - Storage: [M.2 SDD/NVme] - Motherboard and BIOS: [MSI Z790 Carbon WiFi/latest] - OS: Windows 11 [24H2] fully updated - Display: [1440P/ultrawide] - Driver: NVIDIA [latest] clean installed with DDU Error codes: - DXGI_ERROR_DEVICE_HUNG - DXGI_ERROR_DEVICE_REMOVED What happens: - Crashes occur sporadically - Sometimes only the game and open Steam processes die (most in my Case) - Sometimes the entire PC reboots (for some players) - there is no consistent pattern by map or time into the match But there are repeated DirectX related crashes that are not fixed by normal maintenance or driver changes. Steps to reproduce: 1. Launch the game normally from Steam or EA App 2. Join RedSec or Conquest mode 3. Played it through heavy action for a few minutes to tens of minutes or Sometimes over one hours 4. Crash with one of the codes above Impact: - Progress and match results are broken - Time is wasted on failed troubleshooting - This affects many players, not isolated edge cases What I have already tried: (None of the following resolved the issue) - Drivers and OS: - Clean driver installs with DDU for multiple versions - Switching between Game Ready and Studio drivers - Windows updates and optional cumulative updates - Removing all overlays and capture tools - Graphics API and launch options: - Launching with -d3d11 - Disabling or enabling the different Anti-lag and upscaling ingame options. - Forcing different shader cache settings in the driver - BIOS and firmware: - Enabling and disabling Resizable BAR - Updating GPU VBIOS - Updating motherboard BIOS and chipset drivers - Power and stability: - Returning CPU and GPU to stock clocks - Disabling XMP or EXPO - Raising power limits or lowering them to stock - Checking PSU capacity and Performance - disable PCI-Express - Link State Power Management on Windows - set Windows PWR-Management to ultimate Performance - Game files and cache: - Verifying files via Steam - Reinstalling the game on a different drive - Deleting DX shader caches - switching Graphics settings - Dropping all settings Low - Disabling Anti-lag and upscalers - Reducing resolution to well below native - Frame cap on and off (ingame and rtss) - Vsync on and off - disable Freesync/gsync - Workarounds that are not solutions: - Artificially throttling performance to keep GPU load very low (this seems to be working) - Running windowed or borderless - (Not tested long enough yet) - Disabling all background apps and services - (Not tested long enough yet) Community signal: Multiple reports show the same DirectX crash codes and the same failure of the usual fixes. The scope appears broad across GPUs from different vendors, multiple driver lines, and fully updated Windows systems. -- All this points to an engine side stability issue under specific render or memory pressure conditions.-- What we need from EA and the dev team: Official acknowledgement that this is being tracked as a top priority and a targeted hotfix or a detailed workaround that does not **bleep** performance. If a driver side change is needed, coordinated guidance with NVIDIA and AMD. Optional: a temporary toggle to disable the specific feature set that triggers the crash. Clear communication on progress and an estimated timeline for a fix. This is blocking normal play for many of us. A stable fix would go a long way for the community. Thank you.
Missing 85 BP points for BF PRO Battlepass
Earlier this week, when the new Battlepass came for BF6 I saw that it didn't have any reward yet. Then a few days later when I already completed it somehow, it suddenly had 85 battlepass points for the BF PRO battlepass. I did not receive those points because I already completed it and therefore am not able to complete the BF PRO battlepass. I've already contacted support and they told me indeed those points have not been granted. But I had to make a discussion here. Who can help me granting these points or just granting me the rewards in the battlepass? I already have 3/10 rewards. So the points I didn't get would give me more than I need. I also have video proof of me having it completed and showing my progress on the BP.Battlefield 6 – FPS drops by half until a setting is changed
Hey everyone, I’ve been running into an issue in Battlefield 6 where my FPS sometimes drops to about half of what it should be when launching the game or loading into certain maps. I found a temporary fix: if I change my display mode from Fullscreen to Bordered Windowed (or vice versa), the FPS immediately goes back to normal. It seems like something gets stuck with the display or graphics settings when the game starts. Maybe it’s related to fullscreen optimization or resolution scaling. Has anyone else run into this? Would be great if EA could look into it.
