Forum Widgets
Packet Loss and Latency Issues on Large Scale Battle Maps/Gamemodes
I’ve been experiencing constant packet loss and latency issues mainly when playing the large scale battle maps/game modes but when switching to the smaller scale maps the issue is gone completely. It’s like playing the game in slow motion basically when I just try to deal with it on the bigger maps/modes. I’m running the game on a gaming laptop with a 13th gen i7, rtx 4070 and 16 GB RAM. When the packet loss/latency issues aren’t happening (rarely) I’m running the game smoothly with around 100+ fps and my connection is completely fine (tested other games and conducted internet speed tests). I've posted about this on Reddit and have found that many others are experiencing this issue as well even with better PC set ups also. Hopefully this gets fixed, pretty bummed out that I can’t experience the craziness of the large scale battles BF is known for. EDIT: A work around for this issue for me is the community servers. I’ve played large scale maps and battles with little to no issues. Hopefully this helps you guys out. Still sucks that we can’t play the official servers without having to deal with this.
BF6 Pro Battle Pass And Rewards Are Missing
So I have Purchased Season 1 The Battlefield 6 Pro Battle Pass And all The instant rewards for purchasing plus the battlefield coins which they say that is included are not available and useable . for reference here is an instant reward skin which is accessible after purchasing the pro version of the battle pass(or the simple one) which is clearly not unlocked . i hope the fix this cause it will be a waste of money if it isn't.BF6 Hitting 100% CPU Usage Causing Lag/Stutter/Latency/Slo-Mo Issues
I play on PC, bought the phantom edition on steam for BF6 and played the beta. In the Beta, my game was genuinely unplayable. the constant frame drops and audio tearing made me try everything I could find online about how to fix it and nothing did. now that the game is officially out, I booted it up and it was completely fine (100+ fps no lag nothing) until about 30 minutes in game when boom. instant frame drops, audio tearing, CPU usage at 100%. I cannot find a single fix and I'm starting to wonder if I'm the only one dealing with this issue. CM title editMotion Sensor Settings Nonfunctional
Not sure how many other people use gyro for FPSs, but I got BF6 on my PS5 because I was excited about flick stick on a competitive game. However, the motion sensor settings are completely non-functional - I've tried everything I can think of to get them to work and they don't. I did a bit more research and apparently this has been a thing since the start of the beta. This was the only reason I bought the game. If anyone's gotten it working, I implore you to reply and lemme know how, otherwise I'm very disappointed in DICE for consistently saying they'll have a feature available at launch, not working on it at all during the beta, then not saying anything (not even putting it in known issues) about it's functionality post-launch. Bit of a waste of $75, if you ask me. --- Clarification - Several people have found ways to get motion sensor settings to a semi-functional state. That being said, right stick + gyro is not possible atm, acceleration is very, very rough, and gyro is likely a very low priority for the team until they get Aim Assist and recoil fixed. I doubt this post will be marked solved before the end of the year. Thankfully, there are lots of other great shooters with excellent gyro if that's something people are looking for. Not going to recommend any here, but take a look in r/GyroGaming over on Reddit if you're curious. 10/29 update - No real updates. Console team is working with engine team to fix various controller issues, including recoil, AA, and gyro, but no fixes have been implemented in-game, and there is no timeline of that happening as of today. As a side note, I don't blame the devs for not being able to implement fully functional gyro at launch, since I no longer expect any AAA game to launch truly finished. I do, however, blame those who invalidate gyro and see it as inferior to aim assist, when gyro is SIGNIFICANTLY EASIER TO DEVELOP AND IMPLEMENT THAN AIM ASSIST and also allows the game to be accessible to an increasingly large number of players who, for some reason or another, have difficulty controlling an entire screen with a tiny stick module. You want more people to play your game? Implement gyro. Praise gyro. Gyro is king, and those who don't see gyro as higher priority than aim assist are in for a rude awakening when all major first party controllers have motion sensing and most first and second party games have smooth, intuitive, and functional gyro settings off the bat. Publishers of AAA games want to make good profit but they aren't willing to make the game more accessible to tens (if not hundreds) of thousands of people. It just seems... Counterintuitive.
I can't start the match or join to any server!
PC - Steam, 7800X3D, RTX4090, 64GB RAM, WIN10 When I try to start a match or log in to any server, just BATTLEFIELD logo pops up and returns me to the main menu. I got this after yesterday's AWS downtime, I didn't have any problems with the game before. Please fix it!
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.
Disconnect/Kicked for Inactivity While Actively Playing or Matchmaking
Literally join a lobby, watch the loading screen and then says your session has been timed out from inactivity?????????????? BOTH my brothers are playing in lobbys, same internet, same ethernet, both on PC, just me!? Anyone else get this? Any fixes? Or just classic EA? CM title edit
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.
Community Highlights
Featured Places
Battlefield Game Info Hub
Read the latest news and announcements from the Battlefield Team.Battlefield 6
Discuss the latest news and game information around Battlefield 6 in the community forums.Battlefield 6 General Discussion
Join the Battlefield 6 community to get game information and updates, talk tactics and share Battlefield moments.Battlefield 6 Technical Issues
Having issues with Battlefield 6? Join here to find help with connectivity, performance issues, crashes and more.Battlefield 6 Bug Reports
Report bugs and see what the Battlefield 6 community is saying on this forum.
