sodcalculator

10 Tech How-To

Battlefield 6 PC Fix: High CPU Usage With a Simple User.cfg

Guide 10-48577 · Updated · Step by step

If you’re experiencing high CPU usage in Battlefield 6 on PC, a simple user.cfg file can help by forcing specific engine and rendering settings that reduce processor load. This article explains what user.cfg does, which settings actually matter, and how to create and test your own configuration file safely.

What Is user.cfg and Why Does It Affect CPU Usage?

user.cfg is a plain text configuration file that Frostbite engine games (including Battlefield titles) read at startup. It lets you override or add console commands that are normally set through the in-game menu. Some of these commands control how many CPU threads the game uses, how much work is offloaded to the GPU, and how aggressively the engine culls objects. Because Battlefield 6 is designed to scale across many cores, a poorly configured default or a system with a slower CPU can end up with threads saturated, causing 90-100% usage and stuttering.

The key is not to disable CPU work entirely—that would hurt performance—but to limit redundant tasks, cap frame rates to a level your CPU can sustain, and adjust rendering features that disproportionately tax the processor. A well-written user.cfg can lower CPU usage by 10-30% in CPU-bound scenes, depending on your hardware and settings.Note: Battlefield 6 is a recent release, and the exact command names can change with patches. The commands below are based on Frostbite conventions and community testing, but you should verify them in your version.

How to Create and Place user.cfg

  1. Close Battlefield 6 completely.
  2. Open Notepad (or any text editor) and create a new file.
  3. Type or paste the commands you want (see the next section for a recommended set).
  4. Save the file as user.cfg (make sure it is not user.cfg.txt).
  5. Place the file in the game’s root folder, where the executable (e.g., bf6.exe or Battlefield.exe) is located. This is usually C:\Program Files\EA Games\Battlefield 6 or your Steam/Epic install folder.
  6. Launch the game. The commands will apply automatically.

If you’re not sure where the executable is, right-click the game in your library (Steam, Epic, EA app) and choose “Manage” → “Browse local files.”

Recommended user.cfg Settings for Lower CPU Usage

Below is a set of commands that commonly help reduce CPU load without sacrificing much visual quality. Copy and paste, then adjust the numbers to your hardware.

// Limit frame rate to reduce CPU work
GameTime.MaxSimFps 60
// Force thread count (0 = auto, 1-8 = specific cores)
Thread.ProcessorCount 0
// Reduce physics and particle CPU load
World.MaxAnisotropy 8
// Disable motion blur (reduces per-object processing)
PostProcess.MotionBlurEnable 0
// Lower shadow quality (shadows are CPU-heavy in Frostbite)
World.ShadowQuality 1
// Cap the number of dynamic lights
World.MaxDynamicLights 4

Let’s break down what each does:

  • GameTime.MaxSimFps: This caps the simulation (CPU) frame rate. If your CPU is the bottleneck, letting it run at 120 FPS when your GPU can’t deliver that just wastes CPU cycles. Setting it to 60 or 75 matches your monitor’s refresh rate and stops the CPU from working ahead.
  • Thread.ProcessorCount: Forces the engine to use a specific number of CPU threads. Setting it to 0 lets the game decide. Some users find that limiting to 6 or 8 threads on a 12-core CPU reduces overhead from thread management. Test values like 4, 6, or 8.
  • World.MaxAnisotropy: Anisotropic filtering is mostly GPU, but lowering it from 16 to 8 can reduce texture sampling load on the CPU in some scenes.
  • PostProcess.MotionBlurEnable: Motion blur requires per-object calculations. Disabling it reduces CPU work.
  • World.ShadowQuality: Shadows are one of the heaviest CPU costs in Frostbite. Setting it to 1 (low) or 2 (medium) can yield a big CPU usage drop.
  • World.MaxDynamicLights: Limits the number of dynamic lights that cast shadows. Fewer lights means fewer draw calls and shadow map updates.

How to Test and Tune the Settings

After creating the file, launch the game and monitor your CPU usage with Task Manager (Ctrl+Shift+Esc) or a tool like MSI Afterburner. Play a typical match for 10-15 minutes, then note the average CPU usage and any stutters.

If CPU usage is still high, try these adjustments one at a time:

  • Lower GameTime.MaxSimFps to 50 or 45.
  • Change Thread.ProcessorCount to 4 or 6.
  • Set World.ShadowQuality to 0 (off).
  • Add World.RenderSky 0 to disable sky rendering (saves some CPU).
  • Add Render.DrawFps 1 to see your FPS in-game (this is a console command, but it works in user.cfg).

Remember: every system is different. A setting that helps one player may hurt another. Always test one change at a time so you know what works.

Common Mistakes and Misconceptions

Mistake 1: Using commands from older Battlefield games. Some commands like RenderDevice.Dx11Enable or World.HighQualityMaterials may not exist in Battlefield 6 or may be renamed. If a command is invalid, the game will ignore it or crash at startup. Always back up your previous user.cfg.

Mistake 2: Confusing CPU usage with GPU usage. High CPU usage is not always a problem. If your GPU is at 95-100% and your CPU is at 70%, you’re fine. If your CPU is at 100% and your GPU is at 60%, you’re CPU-bound. The goal is to balance the load.

Mistake 3: Believing that disabling all CPU features will help. Some users set every quality to 0, which can actually increase CPU usage because the engine spends more time on culling and fallback paths. Keep settings reasonable.

Mistake 4: Not updating the file after game patches. Game updates can change command names or behavior. Re-check your user.cfg after each major patch.

When user.cfg Won’t Help

If your CPU usage is high because your CPU is genuinely weak (e.g., a dual-core or old quad-core), user.cfg can only do so much. In that case, you may need to lower the game’s resolution scale (which reduces both CPU and GPU load) or close background applications like browsers and streaming software.

Also, if the high CPU usage is caused by a memory leak or a bug in the game itself, no configuration file will fix it. Check the game’s official forums or patch notes for known issues.

Alternatives to user.cfg

If you prefer not to edit files, you can achieve similar results through the in-game settings menu:

  • Limit the frame rate (if the game offers that option).
  • Lower shadow quality and dynamic light settings.
  • Disable motion blur.
  • Turn off ray tracing, which is notoriously CPU-heavy.

Another alternative is to use your graphics card driver’s control panel (NVIDIA Control Panel or AMD Software) to set a global frame rate cap for the game. This works without touching the game files.

Safety and Backup Tips

Before you start, copy your existing user.cfg (if you have one) to a safe place. If the game crashes or behaves oddly, you can restore it. Also, be aware that some anti-cheat systems may flag modified configuration files if they contain commands that give an unfair advantage. The commands listed here are standard performance tweaks, but if you’re unsure, check the game’s official policy.

Never download a user.cfg from a random website—it could contain malicious commands. Always write your own, based on official documentation or trusted community sources.

Frequently Asked Questions

Q: Will user.cfg get me banned?
No, as long as you use standard performance commands. Anti-cheat systems typically ignore these, but if you use commands that alter gameplay (like increased view distance or wallhacks), that’s a bannable offense. Stick to the settings above.

Q: I put the file in the right folder, but nothing changed. Why?
Make sure the file is named exactly user.cfg (no .txt extension). In Windows, you may need to enable “File name extensions” in File Explorer to see the full name. Also, check if the game has a separate “Documents” folder for configs—some Frostbite games read from there instead.

Q: Can I use user.cfg to increase FPS instead of lowering CPU usage?
Yes, many of the same commands can boost FPS if your CPU is the bottleneck. Lowering CPU usage often results in higher, more stable FPS. Just be careful not to sacrifice too much visual quality.

Q: My game crashes after adding user.cfg. What should I do?
Remove the file and launch the game. If it works, add commands back one by one to find the culprit. The most likely crash-causers are commands that don’t exist in your version or invalid values (like setting Thread.ProcessorCount to 16 on an 8-core CPU).

Q: Is there a way to see if my user.cfg is being read?
Open the game’s console (usually the tilde key ~) and type exec user.cfg. If it runs without errors, the file is being read. You can also type render.drawfps 1 to see if that command takes effect.

Q: Does user.cfg work in multiplayer?
Yes, it works in all modes. However, some online servers may enforce their own settings or disallow certain commands. If you get disconnected, remove the file and try again.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →