Battlefield 1 Deploys First Post-Launch Patch

Battlefield 1 [official site] has received its first patch since the customary launch update which arrived alongside the game on Friday. If you’ve been playing over the weekend you may have noticed a few problems, and this patch does fix some of ’em, including incorrect class ranks. It should wing its way to you via the usual Origin update-o-way. Patch notes are over here but the forums have been throwing a hissy fit over who is and isn’t allowed to access that so do read on.

Voila, your patch notes:

General

  • Fix for one common and one uncommon client crash.
  • Fixed a potential soft freeze in single player campaign connected to AI.
  • Fixed an issue where players experienced getting stuck in the globe screen when cancelling matchmaking.
  • Fixed an issue when trying to join multiple servers.
  • Fixed an issue where players experienced weapon skins not being removed when scrapping items.
  • Fixed an issue where players were missing ‘The Insider’ Dog Tag.
  • Tweaked calculations of values in End of Round.
  • Fixed issue where Class Rank was incorrect.
  • -Note: This fix may result in players going down in Class Rank to the correct rank. In this scenario, any unlocks purchased at a higher and incorrect rank will not be lost.

  • PC: Fixed an occasional crash when a user shutdown the game.
  • PC: Fixed an issue where players experienced troubles with A and X button functionality on PC while using an Xbox One controller.
  • PC: Fixed an issue where players experienced crashing while closing the client during streaming installation.

UI

  • Fixed two issues in the ‘Through Mud and Blood’ War Story where no new objectives would appear.
  • Fixed an issue where players experienced wrong info in loading screen.
  • Fixed an issue where players were missing the Dog Tag counter.
  • Fixed an issue where English text would appear for players in non-English regions.
  • Fixed an issue where players experienced a placeholder image when opening the Operations menu for the first time.
  • PC: Fixed an issue where players were missing an option to display controller button prompts.
    Fixed an issue where players experienced End of Round screen not loading.

Graphics

  • Fixed a crash related to soldier animation.
  • Fixed a graphical glitch when exiting a War Story and going to the main menu.
  • Fixed an issue where players experienced player icon overlapping while matchmaking on console.
  • PC: Temporal anti-aliasing is now the default anti-aliasing mode on medium graphics quality.
  • PC: Fix for a graphical issue causing artifacts in shadows.

Those are some patch notes right there all right. If Brendy were here – he who told us Wot He Thinks BF1 – I’m sure he’d have some more insight. Me? Ah, yes, I certainly can see why you might want those crashes fixed. Tidy up those glitches too. Yes, graphical glitches are a problem in war all right – I’m sure Wilfred Owen wrote poems about ’em? And weren’t ‘End of Round’ problems the driving force behind Siegfried Sassoon’s anti-war protest? Yes, yes.

From this site

10 Comments

  1. wykydtronik says:

    I see they haven’t patched a few bugs that I’ve experienced…

    * Player not being able to aim down sights/scope with no gas mask on (seems to be a bug with the gas mask, have to spam T a few times to fix it)
    * Player bayonet charges past an enemy right in front of them (even when crosshairs line up, perhaps desync?)
    * Pistol bug? Switching to the pistol and not being able to fire
    * AMD Crossfire flickering on certain objects/shadows (Even with latest AMD 16.10.2 drivers, which states that this issue was fix. I know, must be an AMD issue.)

    Anyone else experience these bugs?

    • piercehead says:

      There are still plenty of legacy bugs such as being revived screwing up firing/scoping animations. Switch weapon still fixes it pretty much 100% of the time.
      Not had any of the other bugs you mention, but I do have graphics driver crashes about every couple of hours.

      Not played since the patch but hoping the “Loadout 1 for all classes resets to default when opening a battlepack” is fixed.

    • TheOx129 says:

      * Player not being able to aim down sights/scope with no gas mask on (seems to be a bug with the gas mask, have to spam T a few times to fix it)

      I’m fairly sure that’s WAD. There needs to be some sort of downside to wearing a gas mask, or else players would simply wear them all the time.

      The bug I’ve run into with gas is that the game can be inconsistent in giving the text and sound indicators that you need to put a gas mask on. Sure, if you’re surrounding by green gas and your vision’s going blurry, you can tell regardless, but there have been a handful of times when things got so chaotic that the lack of a UI indicator killed me.

      • Ayasano says:

        The bug is that you still can’t ADS/scope AFTER you take the gas mask OFF.

        The main bug I’ve been getting is with sound cutting out until I restart the game. (Alt-tabbing doesn’t fix it, just makes a popping sound)

    • April March says:

      The next patch will have a fix:
      Fixed issue where players will miss a player in their crosshairs with a bayonette charge. It still happens, but now a sad trombone plays.

  2. ran93r says:

    and I hope they never fix this: link to imgur.com
    Only in Battlefield.

    • Unclepauly says:

      I’m sure some people in WW1 thought armageddon was upon us, and that wouldn’t have put any thoughts to rest at all.

  3. Pizzzahut says:

    Nothing about inclusion of in-game admins or a boost to the anti-cheat software? They’ve got to address both of those before I’d ever consider this version of BF.

  4. JustAchaP says:

    A lot of the time when I get revived I can’t fire my gun and have to switch to the other weapon to fix it. Don’t know if its meant to be that way or not.

Comment on this story

XHTML: Allowed code: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>