Hit registration
I'm landing 1 in 5 shots, while I'm getting Lazer beamed across the map, I AM SICK TO DEATH OF THIS BS, I'm hitting players for more then 100hp, I've gone from 40+ kills top 5 on leader board to near the bottom since your update, weapon lag, and I'm not being funny, you lot can't balance a weapon even if it slapped you in the face, a p90 killed me over 110m a way, 1 shot, I had 40+hp, I was use the L3 with 1017 bullet Velocity, got beaten by a kord with at range while the kord has less damage and battle velocity oh but META, this game is a disaster, I'm looking for something else to play, I will not waste a single penny on this franchise, pathetic COD in a skin25Views1like0CommentsIP 15.197.149.64 accounts.grpc.ea.com rejects auths
EA Auth Server on AWS Global Accelerator rejects valid auth requests (IP 15.197.149.64 accounts.grpc.ea.com) Battlefield 6 Connection Failure from UK / Globally — accounts.grpc.ea.com DNS Resolution Bug Summary Battlefield 6 fails to connect ("Connection Failed") when DNS resolves accounts.grpc.ea.com to 15.197.149.64 (AWS Global Accelerator) as the primary IP. When the same hostname resolves to 99.83.166.42 (CloudFront) as the primary IP, authentication succeeds. The game always uses the first IP returned by DNS and does not fall back to the second on failure. Environment Game: Battlefield 6 (Steam, PC) OS: Windows 11 Pro (Build 26200) Network: All connections on the same LAN (192.168.1.0/24), same router, same DNS servers, same ISP Adapter: Realtek USB GbE (same physical adapter used in all tests) Reproduction The issue is reliably reproducible based on which IP address DNS returns first for accounts.grpc.ea.com: Network Path DNS Returns Server Used Auth Result Direct ethernet via switch 99.83.166.42, 15.197.149.64 99.83.166.42 (CloudFront) Success WiFi (direct to router) 99.83.166.42, 15.197.149.64 99.83.166.42 (CloudFront) Success Ethernet via powerline adapter 15.197.149.64, 99.83.166.42 15.197.149.64 (Global Accelerator) Failure Adding a hosts file entry to force accounts.grpc.ea.com to 99.83.166.42 resolves the issue on the failing network path. Technical Analysis Full packet captures (pcapng) were taken on all three network paths using dumpcap/tshark. The captures show: 1. The gRPC authentication exchange differs by server endpoint When connecting to 99.83.166.42 (CloudFront) — SUCCESS: Client sends 1273-1274 byte auth request Server responds with 527 bytes, then 380-381 byte auth response Client sends 366 byte follow-up Server returns 7081-7083 bytes of session/token data Game proceeds to Blaze redirector and game servers When connecting to 15.197.149.64 (AWS Global Accelerator) — FAILURE: Client sends 1225 byte auth request (48 bytes shorter) Server responds with 527 bytes, then 424 byte auth response (different from success) Client goes silent for 11 seconds Client retries with 1042 bytes Server responds with 113 bytes (rejection) Client sends RST, game displays "Connection Failed" 2. All other EA services work correctly on all paths eaanticheat.ac.ea.com — anticheat verification completes successfully cdn.eaanticheat.ac.ea.com — CDN downloads complete successfully gcs.ea.com — game config service connects successfully collector.errors.ea.com — error reporting works (contacted in both success and failure cases) All TCP connections establish correctly (SYN/SYN-ACK) All TLS handshakes complete successfully Zero packet loss on all network paths 3. The failure is isolated to the gRPC auth endpoint The only difference between working and failing sessions is which IP serves accounts.grpc.ea.com. The two IPs appear to behave differently: 99.83.166.42 (CloudFront): Returns valid authentication/session data 15.197.149.64 (AWS Global Accelerator): Returns a rejection response 4. No client-side network issues Network diagnostics confirmed identical configuration across all paths: Same IP address (192.168.1.241 on ethernet, 192.168.1.207 on WiFi) Same gateway (192.168.1.1) Same DNS servers Same routing table and interface metrics Same MTU (1500) Gateway latency: 1-2ms (ethernet), 3-25ms (powerline) — both well within acceptable range Impact Any player whose DNS resolver returns 15.197.149.64 as the first IP for accounts.grpc.ea.com will be unable to connect. DNS ordering can vary based on ISP, geographic location, DNS caching, and network path, making this issue intermittent and difficult for affected players to diagnose. Suggested Fix Investigate the 15.197.149.64 (AWS Global Accelerator) endpoint — it appears to return different/invalid auth responses compared to the CloudFront endpoint Implement fallback — if the first resolved IP for accounts.grpc.ea.com returns an auth failure, the game should retry with the next DNS result before giving up Verify both endpoints are serving the same gRPC service configuration Workaround Adding the following entry to C:\Windows\System32\drivers\etc\hosts forces the working endpoint: 99.83.166.42 accounts.grpc.ea.com Note: This IP may change over time as CloudFront rotates addresses. This is a temporary workaround only. Evidence Files The following packet captures are available to support this report: bf6_powerline_20260308_004544.pcapng — Failing connection (powerline path) bf6_ethernet_working_20260308_005300.pcapng — Working connection (direct ethernet) bf6_wifi_20260308_010049.pcapng — Working connection (WiFi) netdiag2_powerline_upstairs_2_20260308_001143.txt — Network diagnostics (powerline) netdiag2_ethernet_downstairs_20260308_001524.txt — Network diagnostics (ethernet)33Views0likes1CommentSeperate settings for multiplayer vs Campaign
Settings for Multiplayer vs Campaign must be seperate so that multiplayer can have low settings while not affecting the frame generation & ultra settings of campaign Make seperate settings for multiplayer & campaign. Like I want to have frame generation and future frame rendering at ultra for campaign & low performance for multiplayer. since both are on seperate windows, it won't be a problem. Make frame generation along with dlss quality give stable frame rates with good visual quality.not exceed my 16gb limit of vram Make the game stable for rtx 5060ti. It drops visual beauty quality in campaign like anything Thanks a lot & Regards. HELLOGAMER761 P.S. : Since u are experimenting with battlefield labs 6, I wanted to give my feedback29Views0likes1CommentHow to get on attacking on breakthrough
Casuel breakthrough is rigged how do I get on attacking side shes uve rigged all games so im defending all time it is un acceptable it should be fair or add a SWAP TEAMS button or an auto balance y dont u guys give a **bleep** any more u guys can learn from bf3 and bf4 but u dont11Views0likes0CommentsPlease atantion
The camera shakes when reloading (does your viewfinder shake like that when you reload in real life?) Try even just flapping your hands; you won't notice any shaking in your viewfinder, but your game will. Instead of aiming at respawn points (platoons, vehicles, capture points, beacons (it sticks where it's impossible to land)). It can be difficult to select a respawn point. It feels like the cursor doesn't respond. Sometimes the cursor disappears completely after opening the map or chat. Sometimes it's impossible to scroll through the chat, and when opening it, it shows the middle of the chat instead of the last words. When holding Tab after death, the table closes itself, and you have to hold it down again to see the results. Dust, like smoke, severely obscures the view of enemies; they're already invisible. Dust obscures the view even from hitting the stair railings. Breakthrough Manhattan is a problem for attackers at the very beginning. Overexposure greatly interferes with vision. Medics don't want to respawn; they simply can't see in the chaos. The models are jerky and unnaturally fast; in BF1, the movements look much better, a paradox. Where are the win/loss statistics? Hit delay or indicator delay? Headshots and kills are so noticeable that they're practically measurable (my ping is 40, no packet loss, 100 fps stable). Where are the weather conditions—rain, snow, wind? The color of the marker is the same as the enemy indicator, which is misleading. Prioritize vehicle sound, otherwise sometimes you can't hear it at all. When dealing damage to a sniper, he calmly headshots me in return. ☝️ During a 1v1 shootout with a player, literally in the last split second before I die, the damage from my weapon suddenly stops, even though my shots continue and my crosshair is perfectly aimed at the enemy. The face models are terrible; eyebrows and hair, which should be dark, glow. After the start of Season 2, player models blend into the textures, and the enemy visibility enhancement setting doesn't help. There aren't enough character monologues, not enough originality. I'm from Ukraine, under constant real-life bombing! But! Add Finally, Russian isn't just a language for Russians; it's spoken by 120 million people besides Russians. Your game is called "Battlefields," but it looks more like smaller battlefields. Please add more large maps. I'll wait for fixes and play. I've been a fan of yours for 25 years, starting with BF 2142.17Views0likes0CommentsConnection issue: Please support Hurricane Electric IPv6 Tunnel
Hi, I'm living in a residential home and rely on a IPv6 tunnel by Hurricane Electric for Internet access. Unfortunately I'm unable to take influence on that. I just bought the game via Steam and I'm disappointed that I can't play it because of connecting to BF6 servers doesn't work. If it's causing no trouble please fix that at server side. Thanks in advance Andreas24Views0likes0CommentsAccount stolen
I have played battlefield 6 since nearly launch, and never had an issue logging in, I tried to login to play on my PlayStation 5, and it’s asking for verification who I am but it’s sending it to a different address, then when tried to login online it said I didn’t have an account. I need help and there seems to be no way to contact EA Directly to fix this, did my game get stolen right off my console? What’s happening to where I can’t play my 70.00 game?? Helllp17Views0likes0CommentsCan’t Connect Since Red Sec Update: Xbox Series S
Since the redsec update my sons battlefield 6 no longer works on his Xbox Series S. It’s been 3 days straight now of failed logins. It repeatedly gives an error code and or says queue of 2400 and then the error code. NAT Type is Open, restarted the internet and even uninstalled and reinstalled the game. The issue persist. Sent in multiple request on the issue and nothing back yet. My copy on my Series X has been great. I paid for two copies and only one works. Not cool EA. Please fix. Has anyone else had this issue?180Views1like2Comments