• Skip to main content
  • Skip to header right navigation
  • Skip to site footer
Gameranx

Gameranx

Video Game News, Lists & Guides

  • News
  • Features
  • Platforms
    • Xbox Series X
    • PS5
    • Nintendo
  • Videos
  • Upcoming Games
  • Guides

DICE Employee Explains Thread Safety Is The Main Technical Issue With Battlefield 4

December 21, 2013 by Ryan Parreno

DICE’s desire to push their key FPS franchise to the newer consoles has worked against them.

An employee of DICE on a Swedish gaming site sought to explain why Battlefield 4 has become notorious for its unstability, citing thread safety.

First off, we need to tackle that idea head on: what even is thread safety? In the programming world, a sequence of instructions is referred to as a thread. Threads can be handled inside or outside a process, and when multiple threads are handled in a single process, this is referred to as multithreading.

Now, thread safety relates directly to multithreading. A piece of code is called thread safe if it works in such a way that it guarantees safe execution of multiple threads at the same time. Thread safety is a relatively recent concern, since it was not until the 90s that operating systems even used multiple threads to execute code.

And this is precisely the kind of change the anonymous DICE employee (posting under the name HonK_sWeMoB) alludes to. As we know, DICE made the call to iterate on Battlefield’s engine Frostbite in the process of developing BF4. They also decided that Frostbite 3, their latest game engine, should make use of 8th generation console hardware more efficiently, and so it is with this line of thought that they enabled multithreading.

Simply put, the code they came up with for BF4 is not thread safe. However, the crashes and general instability is apparently a coincidence. Threads can run on independent schedulers, or timers, if you’d like. Different hardware with different operating systems and background processes have different timers within them. This is at the crux of the game’s quality control issues.

Now, to be clear, this is not the complete explanation some Battlefield players may be looking for. However, it is the necessary technical explanation, which explains what the particular nature of the setback is, as well as what exactly DICE is doing now: playtesting the game in different setups to ensure the game works well on all of them. As always, DICE claims they are working around the clock to fix these issues, and this employee concurs that they needed more time. It’s a shame that DICE is now caught up in the firestorm of controversy, but at least for the players, I hope they can resolve these issues sooner rather than later.

Share this post:

FacebookTwitterLinkedInPinterest

Recent Videos

GTA 6: 20 MISTAKES YOU SHOULDN'T MAKE

GTA 6: 20 MISTAKES YOU SHOULDN'T MAKE

GTA 6: 10 Things The Game DOESN'T TELL YOU

GTA 6: 10 Things The Game DOESN'T TELL YOU

GTA 6 - Before You Buy

GTA 6 - Before You Buy

10 HUGE Moments That Shaped GTA 6

10 HUGE Moments That Shaped GTA 6

Bodycam Zombie Game is INSANE

Bodycam Zombie Game is INSANE

20 Worst Video Game Adaptations EVER

20 Worst Video Game Adaptations EVER

GTA 6: 25 Things You NEED TO KNOW

GTA 6: 25 Things You NEED TO KNOW

NEW GTA6 GAMEPLAY,  TWO NEW ASSASSIN'S CREED GAMES LEAKED? & MORE

NEW GTA6 GAMEPLAY, TWO NEW ASSASSIN'S CREED GAMES LEAKED? & MORE

20 NEW Zombie Games That Are Trying Something DIFFERENT

20 NEW Zombie Games That Are Trying Something DIFFERENT

Category: Updates

Sidebar

Recent Posts

  • Cyberleek Is Leaking GTA 6’s XBOX Build – To Raise His Crypto To 15 Million
  • Rockstar: PS5 Pro Is Not Powerful Enough To Run GTA 6 At Higher Frame Rates
  • The Game Awards Just Leaked Manni L. Perez For GTA 6 – By Nominating Her
  • GTA 6’s 2022 Hacker Arion Kurtaj Has Officially Pled Guilty In Court
  • Physical GTA 6 Buyers Are Claiming They Aren’t Getting The Codes In Boxes

Copyright © 2026 · Gameranx · All Rights Reserved · Powered by Mai Theme