Sections

Battlefield 4: PC stability patch out today, memory leak addressed

Monday, 13th January 2014 11:30 GMT By Dave Cook

Battlefield 4 developer DICE has confirmed it will release a new PC patch later today, addressing stability and memory leak issues.

It follows a pair of DICE developers teasing future Battlefield 4 updates on Twitter. Hit the link to see what they teased.

A post on the Battlelog forum explains that he update will roll out later today. Here are the patch notes in full:

Jan 13 PC Game Update Notes

  • -Various fixes for improving general stability
  • -Fixed a memory leak issue occurring after level shutdowns, which could result in a out-of-memory crash in longer play sessions
  • -Additional fix for the “sound loop” deadlock when running High/Ultra graphics settings
  • -Added a warning for using Legacy AMD drivers that were out of date
  • -Fixed a player feedback timing issue where blood was appearing before other damage indicators, and before damage was actually done
  • -Fixed a bug where players’ rank icons on the scoreboard would not be updated
  • -Fix for Asian users unable to start Battlefield 3 and Battlefield 4 on Windows 8.1
  • -Normalized repair rates across all vehicles
  • -Fixed problem with killer health in kill card not being correctly updated (showing 100% health even though the soldier was hurt)
  • -Fix for friendly marker not always showing when needed to, resulting in players shooting team members
  • -Fixed a bug where a Main Battle Tank Coaxial HMG ammo box was occasionally blocking the driver’s camera
  • -Increased damage by 25% for the Stealth Jet 20mm cannons.
  • -Stealth Jets now have more similar handling attributes to each other. F35 & J-20 are slightly more agile, Su-50 is less agile.
  • -Attack Jets now have more similar handling attributes to each other, and all 3 are now slightly less agile than earlier
  • -Fixed camera glitch when switching weapons while moving in crouch
  • -Fixed an occasional bug where players could experience intermittent engine sound dropouts when driving wheeled IFVs
  • -Fix for player spawning under the map when deploying on Lancang Dam
  • -Fixed flickering in map and minimap on Rogue Transmission and Operation Locker

Via Polygon.

Breaking news

8 Comments

Sign in to post a comment.

  1. SplatteredHouse

    Release and sell a game in October, that’s somewhat ready to play in January – Are they expecting GRATITUDE for this? It’s In the Game…Other than when it isn’t of course! (see: trailers for current-gen Madden, versus reality)

    #1 3 months ago
  2. ArithonUK

    All very well playing patty-cake with damage percentages, but how about making this £70 game RUN for more than a half a round without quitting to desktop or being unable to connect to any sever in the first place?

    For the money they’ve taken for this broken game DICE have a lot of apologising to do!

    #2 3 months ago
  3. koopa

    Bout Time; I’ve never played such a broken game like this before. Like, Dice used us to beta test the shit for them and months later still broken.
    Ive experience multiple crashes, tons of glitches, hackers, unbalance everything, and my personal hated favorite “Server Lag” since day one. I got an I7 to improve performance with SLI and…..Still broken…..added SSD….broken! For some stupid reason other people say it plays fine and rack up tons of kills with no lag.

    #3 3 months ago
  4. Harrow

    Wow they are still trying to fix it .uninstalled it awhile ago

    #4 3 months ago
  5. rafterman83

    Still no mention of the debilitating lag that seems to effect every server. Lancgang Dam will be forever known as Lag-cang Dam.

    #5 3 months ago
  6. l0cut15

    Nooo last patch was almost perfect, now the sound look crash is back.

    #6 3 months ago
  7. grizzlycake

    My guess is the game was rushed in order to be released with PS4 and Xbox One.

    #7 3 months ago
  8. digmouse

    The Asian Windows 8 fix is pretty silly, all they do is remove the “tm” in the application title because it will cause DirectX to crash if your Unicode setting isn’t US English, the community has found this solution like two months ago and it takes them this long to implement it.

    #8 3 months ago