Recommended Posts

Game works and is stable for me now. Been playing a good bit over the weekend and am now able to enjoy the game.

Even unlocked C4 and got the AWS LMG unlock after 3x Bike + C4 into various Armored vehicles.

Then in a moment of utter Battlefield "OMG THAT JUST HAPPENEND?!?!" as I was coming of a ridge on the mountainous side of Silk Road.

Jet flys low and I jump off bike as it goes off the ridge, straight into the jet, just as I detonate the C4. Best BF kill I have ever had!!!

  • Like 1

This game's audio is very quiet.

I have to turn my speakers up 40% more to play then remember to turn them back down afterward.

It's not my system.

Maybe adjusting the in game audio a whole bunch will help you not having to adjust system settings each time you play?!

Maybe adjusting the in game audio a whole bunch will help you not having to adjust system settings each time you play?!

Obviously the in-game audio is set to max.

 

Some games (probably 1 in 15 or something) seem to have quiet audio.

 

It's happened for 10+ years, I'm just used to it :)

Any Premium members managed to download Naval Strike yet? I checked the XB this morning but it wasn't showing.

I got the usual update for my PS4, and my friends list on PSN was full of people playing Carrier Assault, I was playing InfamohInfamous though.

This is the most unplayable game I've ever had the misfortune of playing, thanks to this patch. The lag issues and rubberbanding are insane.

 

Did you expect anything else out of EA? I stopped playing Battlefield after 2. The amount of crap they loaded in the game to take away from game play and teamwork with all the stats crap, requiring Origin and the requiring of a ranked server if you are a server owner is just beyond lame. RIP Battlefield!

hmmm I haven't had any issues with rubberbanding on BF4 lately, except for on one server, but that was the servers for, or when I forgot to turn off downloads and uploads in the background and have pings in the 150-700 and probably packetloss. 

 

Also the server I play on have scripts that keep reminding of you teamwork, auto recruiting people into squads and some other stuff to encourage teamwork. I see nearly as much teamwork there as I did in the early days of BF2. it's not the features that stop teamwork, it's all the players. in the early days of BF2 there was teamwork because most players where BF2 players who wanted to teamwork, then you got more and more modern war FPS players who didn't care. 

hmmm I haven't had any issues with rubberbanding on BF4 lately, except for on one server, but that was the servers for, or when I forgot to turn off downloads and uploads in the background and have pings in the 150-700 and probably packetloss. 

 

Also the server I play on have scripts that keep reminding of you teamwork, auto recruiting people into squads and some other stuff to encourage teamwork. I see nearly as much teamwork there as I did in the early days of BF2. it's not the features that stop teamwork, it's all the players. in the early days of BF2 there was teamwork because most players where BF2 players who wanted to teamwork, then you got more and more modern war FPS players who didn't care. 

I'm referring to the Xbox One version and the new DLC. I have yet to meet someone who says it isn't insanely laggy.

Broken launch. Broken stride. The second expansion consists entirely of maps grown old. The third expansion is delayed and yet I lost my waning interest months ago.

 

I used to love you, Battlefield. I used to talk you up to my friends. I told of your triumphs and exhilaration.

 

Now I loathe you. You disgust me.

  • Like 2

Wow nice lack of hit markers there!

I really wish they would sort these issues out, I can't believe how bad the Naval Strike maps are when on 64 player servers. The rubberbanding is shocking and just puts me off what seem like pretty decent maps!

This topic is now closed to further replies.
  • Posts

    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!