Battlefield 1 – Official PC Requirements

DICE and Electronic Arts have revealed the official PC requirements for Battlefield 1. According to the PC specs, PC gamers will need an Intel i5 6600K or an AMD FX-6350, 8GB of RAM, a 64-bit operating system and an nVidia GeForce GTX 660 or an AMD Radeon HD 7850. You can view the full PC specs for Battlefield 1 below.

Battlefield 1 PC Requirements:

MINIMUM SPECS

  • OS: 64-bit Windows 7, Windows 8.1 and Windows 10
  • Processor (AMD): AMD FX-6350
  • Processor (Intel): Core i5 6600K
  • Memory: 8GB RAM
  • Graphics card (AMD): AMD Radeon™ HD 7850 2GB
  • Graphics card (NVIDIA): nVidia GeForce® GTX 660 2GB
  • DirectX: 11.0 Compatible video card or equivalent
  • Online Connection Requirements: 512 KBPS or faster Internet connection
  • Hard-drive space: 50GB

RECOMMENDED SPECS

  • OS: 64-bit Windows 10 or later
  • Processor (AMD): AMD FX 8350 Wraith
  • Processor (Intel): Intel Core i7 4790 or equivalent
  • Memory: 16GB RAM
  • Graphics card (AMD): AMD Radeon™ RX 480 4GB
  • Graphics card (NVIDIA): NVIDIA GeForce® GTX 1060 3GB
  • DirectX: 11.1 Compatible video card or equivalent
  • Online Connection Requirements: 512 KBPS or faster Internet connection
  • Available Disk Space: 50GB

55 thoughts on “Battlefield 1 – Official PC Requirements”

  1. I5 6600 on minimum ??! I played the beta on an 2500k OC with a GTX970 (1080p Ultra) and the framerate never gone down the 60 fps bar

    1. Do you have 2500k overclocked to 4.0 ghz like me? Do you also have gtx 970 overclocked +100 mhz core+350 mhz memory like i have done? I have 1440p so it wil be more demaning but i believe it will still run max settings fine even if not 60 fps

      1. OC to 4.5, no OC for the GPU, i think it will run smooth even on 1440p, and you have almost complete graphic options menu, you can tweak it as you want^^

        1. I tryed it. If i oc it at anything higher than 4.2 ghz pc restarts after a frw minutes of games due to the stock cooler not being enough for such high overclock. I bough a big cooler but unforunately it dont fit on my case. The techician told me that he take my pc to his lab and open some new holes on the case for a big cpu fan to fit but i told him that it is not worth it so i will keep it and use it on the next cpu that i will buy

          1. AIO cooler cannot fit either? right now i’m using Corsair H80 with my 2500K oced to 4.5ghz. temps were decent

      2. I have it overclocked to 4.0 ghz and ram is 16 gb ddr 3 1600 mhz. But next year i will change cpu ram and motherboard and i will buy the fatest ram avaliable. Currnetly the fatest is ddr4 3200 mhz but they already announced ddr4 4400 mhz. If by the time i decide to upgrade 4400 mhz ram are avaliable then i will buy it

        1. To be fair though, the only map in the beta was a desert map which shouldn’t be all that problematic. I expect the full release to have way more complex maps, with much much much more buildings and environmental textures. This will be the real test for older CPU’s. My guess is that EA just want to go save with this.

          1. Well in the alpha, people had a different map and they had similar performance (comparing with my system). But you could be right.

    1. They don’t need to be comparable.

      In minimum settings if “DX11 version” so you need at least Core i5 6600 because DX11 use only one thread of CPU. DX11 can’t use more than one thread so it must be very fast.

      In recommended settings you have “Windows 10 and DX12” which use all threads of CPU. AMD FX 8350 Wraith have 8 cores. DX12 can use all of them. So single thread can be slower than single thread in Intel Core i5 6600 but whole CPU is faster.

      1. you seem to be ignoring that fact the recommend specs make no mention of DX12 and that DICE has a history of poorly implementing new graphical APIs

  2. For some reason my character kept moving by itself in the Open Beta at random times. Really fun when it decides to move in front of a full enemy squad…

    1. SP or MP?

      In MP it’s bad net coding, a staple feature of DICE Battlefield games as of their transition to Frostbite, in SP it’s just a glitch.

      Though, to be fair, I don’t know of any gloriously ridiculous netcode bugs in Battlefront, so I’d semi-confidently say it’s just one of those Beta things that’ll (probably) get resolved before launch, if not in the Day 0 Patch.

  3. [Insert AmigaBot 4000 quoting DICE developers on Twitter back in April 2015 in regards to DX12 exclusivity here]

    “because by that point, adoption rates will be high enough”, was it?

    So sorry, you were saying? >.>

      1. PS: No love for Windows 7 in recommended settings:

        RECOMMENDED SPECS
        OS: 64-bit Windows 10
        DirectX: 11.1 Compatible video card or equivalent (DX11.1 isn’t available in old Windows 7)

        1. Not really BF4 used it and one could see a slight boost in performance and no one suffered from it. Vulkan is the right choice imo for dev’s who need to stand up to Microsoft. Even if Vulkan wasn’t 100% as good as 12, one would think its still the superior choice since dev’s can work together to improve it.

          Right now we have the war on the 90’s when it comes to APIs will Microsoft win again?

      2. Except, overall Windows 10 migration did slow down after the end of the free period (by overall, I mean worldwide, according to rather more accurate statistics than those gathered by Steam).

        True, I was wrong about the Steam numbers immediately crumbling off, & I’ll probably be wrong about that % decrease by the end of the year that I called, but, overall, I stand by the fact that Windows 10’s exponential growth cannot be sustained. It will hit a wall, & it will happen sooner, rather than later.

        1. I don’t care about “overall Windows 10 migration”. I care about migration among gamers because I want to developers drop support of old DX11 and use new DX12. Now on Steam is more DX12 users than DX11 users (on Origin statistics are even better). We have some first exclusive DX12 titles such as Gears and Forza. I hope for more DX12 exclusives in 2017 after release of Xbox Scorpio. Future of PC is bright

          1. We have Microsoft DX12-exclusive titles, as mandated by Microsoft’s “force that sh*t down their throats” policies. There’s a difference.

            As others have already said; you keep talking about wanting them to drop DX11 support, but you advocate near-exclusively for DX12, which is Windows 10-bound, instead of DX12 &/or Vulkan, which doesn’t require an OS switch.

            That, is the primary problem. I myself want to see them move on from DX11 as well, since, as you yourself have said on multiple occasions – it is a rather old API, but moving on from DX11 in favour of DX12 & by extension, forced, mandatory Windows 10 upgrades is not a good thing, in any way, what-so-ever.

            If DICE had gone for Vulkan instead of DX12, they could, in line with your desires, have dropped all support for DX11, but they didn’t. As a result, they’re forced to support both the legacy DX11 API, and the “shiny new” DX12 API.

            Good sh*t, huh? Oh well, maybe next time, I guess – assuming those DICE engineers can unscrew their heads from Microsoft’s asscrack, I suppose.

          2. “If DICE had gone for Vulkan instead of DX12”

            DICE don’t care about Vulkan. They always use DirectX instead of OpenGL. Even on Mac OSX developers of DeusEx (Feral Interactive) don’t want Vulkan and choose Apple Metal. Developers always choose best API for each system.

          3. doesn’t matter how you spin it developer will not going to giving up on Dx11. the fact that FL11_3 exist shows that your master are not even going to drop DX11 development and yet here you preaching about DX12 replacing DX11 entirely. you should learn from your master more. don’t skip your lesson half way.

        2. It will still be the number one platform for PC gaming and this is coming from a person who wishes dev’s would just use Vulkan first then other APIs second.

          1. Arguably, probably, but, according to the id Software devs, porting from Vulkan to DX12 is a relatively easy affair.

            If that’s true, I could see them going for Vulkan just to drop the legacy support that is DX11. After all, no matter what, Windows 7 support isn’t going away in the near future, & unless Microsoft caves & ports DX11.3 &/or DX12 to Windows 7, the only remaining options are either DX11, or Vulkan. Needless to say which most people would prefer.

    1. That horse stuck in the building (0:25) reminded me of that scene from The New Guy (2002) where the football coach shouts “look at the horse’s @ss & run!”

      Epic.

      P.S. What. The. F*ck. I thought they fixed all this sh*t with Battlefront? >.>

  4. After playing that game i will say one thing.

    RIP the competition.

    No other engine/developper brings so much fun with such beautiful graphics without the need of a nuclear powerhouse.

    1. Direct X 12. Are you excited? You will be.

      What a joke. There is nothing to be excited about. Just an improved technology that fails to deliver what promised.

    2. Where’d you get that one from, 2014?

      No sh*t they queue’d up for DX12 before Vulkan. So did I, before Microsoft announced that “yes, we are indeed, actually, so stupid as to hold DX12 hostage for Windows 10 adopters only.”

      Once that happened, I left DX12 to its inevitable fate, spurred & assisted by the announcement of Vulkan.

  5. Mantle use HLSL as shader language. HLSL is also used in DX11 and DX12. So you can have single shader code between DX11, DX12, Mantle. Also Sony PS4 have auto translation HLSL->PSSL in their PS4 SDK. Vulkan can’t use HLSL, its based on SPIR-V and GLSL. GLSL is shared between OpenGL, OpenGL ES and Vulkan.

    If game use DX11 or Mantle it is easier to use DX12.
    If game use OpenGL it is easier to use Vulkan.

  6. i5 6600k minimum with the fx 6350 that is worst than the low end i5 3000 series…another hardware seller requirements…
    my old i7 3770k paired with my 980 ti in the beta maxed out 1080p gave me above 95 fps all the time so yea bullshit

  7. Hmmm… Planning to upgrade CPU+Mobo+RAM this fall… want to future proof for about… the next 1.5-2 years… what’s my best bet??

      1. Well, what specific i5 is what I am really asking. With Kaby Lake coming out, I’m a little unsure of what cpu will stand the test of time and still be providing the max horsepower for gaming after multiple GPU upgrades.

        I will build out from there with the mobo (usually go Gigabyte) and ddr4, but I want to make sure I start with the right part.

        1. Do you overclock? Then get the Quad i5 K. If not, then get the Quad i5. Highest model, without going into the Extreme lineup.

          Waiting for Kaby means waiting for Kaby Boards as well, since the higher-end boards usually come after the Chips themselves. Alternatively, you could just go with Intel’s 2015 lineup, & a board that came out relatively recently & still be on your merry way for the foreseeable future, really.

          CPU power really isn’t the bottleneck anymore, GPU power is, & unless you’re going to be running some kind of Quad-SLi setup, even a non-Overclocked i5 will serve you just fine for 3 years or so, at which point I recommend upgrading just on principle alone.

  8. I think you might be basing everything on the fact that the beta map included a desert to snipe from.

    The most popular BF maps have always been the mid-close range, (in some cases) cluttered maps where sniping is only semi-useful and good squad-play and infantry size engagement areas are the norm.

    You think that won’t be the case here? You really think they won’t be including a Stallingrad-style map? This is not going to be SWBattleFront.

Leave a Reply

Your email address will not be published. Required fields are marked *