Breathedge 2 Low FPS & Stuttering Fix: Engine.ini Tweaks Guide (2026)

If you have been playing Breathedge 2 on PC and thought, “Why the hell does this game stutter when my hardware should be handling it?”, you are definitely not alone.

I have spent enough time tweaking Unreal Engine games to know the difference between genuinely demanding graphics and a game simply wasting performance. Breathedge 2 can look fantastic, especially when you are drifting through huge space environments filled with debris, stations, lighting effects, physics objects, and constantly loading assets. The problem is that all of that visual ambition can come with some seriously ugly frame-time spikes.

Average FPS is only half the story.

You can have 80, 100, or even 144 FPS on the counter and still feel the game hitch every few seconds. That annoying little pause when entering a new area, turning toward a dense debris field, or triggering a new visual effect is exactly the kind of thing that ruins an otherwise smooth session.

The good news? There are several Unreal Engine configuration settings worth testing.

By editing Engine.ini, you can adjust texture streaming, anti-aliasing, shadows, post-processing, shader behavior, and several rendering options that are not always exposed through the normal graphics menu.

This guide walks through the configuration I would personally start with in 2026, explains what the important commands are doing, and covers a few Windows-side changes that can help stabilize frame pacing even further.

Important: Engine.ini tweaks can behave differently depending on your hardware, GPU driver, game build, and Unreal Engine version. Treat the configuration below as a performance-oriented baseline rather than a magical one-click FPS button. If a particular setting causes visual problems, remove that line and test again.

Where Is Breathedge 2’s Engine.ini Located?

Before changing anything, you need to find the game’s configuration directory.

Windows normally keeps the Local AppData folder out of sight, so the quickest method is to use the Run command.

Press Windows Key + R, then enter:

%localappdata%

Press Enter.

You should now be inside your local Windows application-data directory. From there, look for the folder associated with Breathedge 2.

Depending on the version you installed and how the game stores its configuration files, the exact directory can vary. A common structure to check is:

Breathedge2\Saved\Config\Windows

You may also encounter configuration folders such as:

WindowsNoEditor

or another platform-specific configuration directory.

Once you reach the appropriate folder, look for:

Engine.ini

If the file already exists, make a backup before changing anything. Seriously. It takes seconds, and it gives you an easy way back if something goes sideways.

Can’t Find Engine.ini?

If Breathedge 2 has not created the file yet, you can create it manually.

Right-click inside the configuration folder and choose:

New → Text Document

Rename the new file to:

Engine.ini

Make absolutely sure Windows has not left the .txt extension attached.

If your file is actually called:

Engine.ini.txt

the game will not treat it as the intended configuration file.

If Windows is hiding extensions, open File Explorer’s folder options and enable File name extensions so you can verify the filename properly.

Recommended Breathedge 2 Engine.ini Performance Configuration

Open Engine.ini with Notepad or another plain-text editor.

If you already have custom settings inside it, don’t blindly delete everything unless you know what those entries are doing. If the file is clearly corrupted or contains old experimental tweaks, creating a clean backup and rebuilding the relevant sections can be easier.

Add the following configuration:

[SystemSettings]
r.Streaming.PoolSize=0
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=128
r.Streaming.Boost=1
r.DefaultFeature.AntiAliasing=2
r.PostProcessAAQuality=4
r.TemporalAACurrentFrameWeight=0.2
r.TemporalAASamples=4
r.TemporalAA.Algorithm=1
r.MaxAnisotropy=16
r.Shadow.MaxResolution=1024
r.Shadow.CSM.MaxCascades=2
r.ShadowQuality=3
r.DistanceFieldShadowing=1
r.AmbientOcclusionLevels=2
r.LightMaxDistanceScale=1.0
r.DynamicBlurRadius=0
r.MotionBlurQuality=0
r.MotionBlur.Max=0
r.BlurGBuffer=0
r.DepthOfFieldQuality=0
r.BloomQuality=1
r.LensFlareQuality=0
r.SceneColorFringeQuality=0
r.VignetteImitationQuality=0
r.Tonemapper.Quality=3
r.Tonemapper.GrainQuantization=0
r.GpuCrashDebugging=0
r.CompileShadersForDevelopment=0
r.Shaders.Optimize=1
r.CreateShadersOnLoad=1
r.XGEShaderCompile=1
r.HZBOcclusion=1
r.AllowOcclusionQueries=1
r.FinishCurrentFrame=0
bUseVSync=False

[/Script/Engine.RendererSettings]
r.TextureStreaming=True
r.D3D12.XGECompilation=1
r.D3D11.UseMultiThreadedDevice=1
r.D3D12.UseMultiThreadedDevice=1
r.bAllowAsyncComputeShaderCalculations=1

[XAudio2.XAudio2DeviceWindows]
bDisableMasterEQ=True

[/Script/Engine.LocalPlayer]
AspectRatioAxisConstraint=AspectRatio_MaintainYFOV

Save the file.

But don’t expect the FPS counter to suddenly double. That’s not really what this kind of tweak is about.

The biggest potential benefit is better frame-time consistency. In other words, fewer moments where the game suddenly feels like it has hit an invisible wall.

What These Engine.ini Settings Actually Do

There is a lot going on in that configuration, so let’s separate the useful stuff from the lines that are more situational.

1. Texture Streaming and VRAM Management

These are some of the first settings I would look at when dealing with stuttering during exploration:

r.Streaming.PoolSize=0
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=128
r.Streaming.Boost=1

Breathedge 2 throws plenty of assets at your PC while you move through its environments. Textures, objects, materials, effects, and environmental details can all be streamed as you travel.

When streaming doesn’t behave nicely, you can get the classic “game runs perfectly until I turn around” situation.

The r.Streaming settings are intended to give Unreal’s texture-streaming system more room to work with available graphics memory.

The particularly interesting line is:

r.Streaming.PoolSize=0

This is often used as a way to let the engine determine the appropriate streaming pool instead of forcing a small fixed value.

That does not mean infinite VRAM. Your GPU still has physical limits, and r.Streaming.LimitPoolSizeToVRAM=1 keeps the configuration tied to available video memory.

If you have a GPU with limited VRAM, don’t expect miracles from this section. In fact, pushing texture memory too aggressively can create a different kind of problem if the system starts running out of resources.

2. Cut the Post-Processing Junk

I’ll be honest: this is one of my favorite categories of PC tweaks.

I don’t need motion blur making my screen look like someone smeared petroleum jelly over the monitor. I don’t need excessive depth of field when I’m trying to see what’s happening in front of me either.

The configuration disables or reduces several of those effects:

r.MotionBlurQuality=0
r.MotionBlur.Max=0
r.DepthOfFieldQuality=0
r.LensFlareQuality=0
r.SceneColorFringeQuality=0
r.VignetteImitationQuality=0
r.Tonemapper.GrainQuantization=0

The direct FPS improvement from these individual commands can vary considerably.

The bigger win for many players is image clarity.

With motion blur disabled, camera movement feels cleaner. Removing chromatic-style fringe effects also makes the image look less processed. Depth of field is another effect I would happily sacrifice when chasing competitive or exploration-focused clarity.

If you’re already struggling to maintain stable performance, these cinematic effects are not where I would spend precious GPU resources.

3. Anti-Aliasing and Image Quality

The configuration doesn’t simply turn anti-aliasing off.

Instead, it uses:

r.DefaultFeature.AntiAliasing=2
r.PostProcessAAQuality=4
r.TemporalAACurrentFrameWeight=0.2
r.TemporalAASamples=4
r.TemporalAA.Algorithm=1

The idea is to maintain a reasonable temporal anti-aliasing setup while keeping image stability under control.

Temporal AA can be a strange beast. Too aggressive and the image becomes soft. Too weak and you start seeing shimmering around geometry, cables, station structures, and other high-contrast objects.

That’s why I prefer testing AA changes alongside the game’s internal resolution scaling or upscaling options rather than judging them in isolation.

If the image suddenly looks smeared after applying the configuration, this is one of the first sections I’d experiment with.

4. Shadows: A Sensible Middle Ground

Shadows are expensive.

Really expensive in the wrong scene.

This configuration uses:

r.Shadow.MaxResolution=1024
r.Shadow.CSM.MaxCascades=2
r.ShadowQuality=3
r.DistanceFieldShadowing=1

Instead of nuking shadows completely, the settings aim for a middle ground.

A 1024 shadow resolution can significantly reduce the amount of rendering work compared with extremely high shadow settings, while two cascades keep the overall shadow system from becoming unnecessarily expensive.

For a game like Breathedge 2, where you’re often surrounded by large environmental structures and lighting effects, shadows can become one of those hidden GPU drains that isn’t immediately obvious from the graphics menu.

If your GPU is already near 99% utilization, reducing shadow quality is still one of the first normal in-game adjustments I’d make.

5. Shader Compilation and Stuttering

This is where things get more interesting.

Shader compilation is one of the most annoying causes of hitching in modern PC games.

You can be cruising along smoothly and then suddenly hit a new effect, material, lighting situation, or environment that causes a nasty frame-time spike.

The configuration includes:

r.CompileShadersForDevelopment=0
r.Shaders.Optimize=1
r.CreateShadersOnLoad=1
r.XGEShaderCompile=1

The goal is to encourage optimized shader handling and reduce some of the situations where expensive work gets pushed directly into gameplay.

There is an important caveat here: Engine.ini settings cannot magically eliminate every shader-compilation hitch.

Some shader behavior is controlled by the game’s build, Unreal Engine version, driver, and shader cache system. If your first launch after a driver update stutters, subsequent launches can sometimes behave differently once caches have been rebuilt.

So don’t judge the configuration after five seconds.

Play for a while.

Visit the locations where the stutters normally happen.

That is the real test.

6. Multi-Threaded Rendering and Async Compute

The configuration also includes:

r.D3D11.UseMultiThreadedDevice=1
r.D3D12.UseMultiThreadedDevice=1
r.bAllowAsyncComputeShaderCalculations=1

The intention is to make better use of modern multi-core CPUs and asynchronous rendering/compute capabilities where supported by the game and renderer.

This matters because modern gaming PCs can have plenty of CPU horsepower sitting around while one or two threads become the limiting factor.

However, don’t fall into the trap of thinking that these commands automatically turn every game into a perfectly parallelized monster.

Unreal Engine’s workload distribution is considerably more complicated than simply “use all CPU cores.”

These settings are better viewed as experimental performance options that may help on one configuration and do very little on another.

That’s why benchmarking matters.

7. Occlusion and Frame Finishing

These commands are also present:

r.HZBOcclusion=1
r.AllowOcclusionQueries=1
r.FinishCurrentFrame=0

Occlusion systems can help the renderer avoid spending resources on objects that aren’t actually visible to the player.

That becomes useful in environments with lots of geometry.

The important part is that these optimizations are not about making textures prettier. They’re about reducing unnecessary rendering work.

And:

r.FinishCurrentFrame=0

helps avoid forcing the renderer into a behavior that can contribute to poor frame pacing.

Engine.ini Settings at a Glance

Should You Make Engine.ini Read-Only?

This is a common trick with Unreal Engine configuration files, but I wouldn’t blindly recommend locking the file immediately.

Yes, setting Engine.ini to read-only can prevent applications from writing changes back to it.

But there’s a trade-off.

If Breathedge 2 needs to update configuration values, generate settings, or write changes during an update, read-only permissions can interfere with that process.

If you want to test it anyway, save your configuration first.

Then:

1. Right-click Engine.ini.
2. Select Properties.
3. Find the Attributes section.
4. Enable Read-only.
5. Click Apply.
6. Click OK.

If the game stops saving graphics settings or behaves strangely afterward, simply remove the read-only flag.

Personally, I recommend keeping an untouched backup of the original file and only using read-only mode if the game repeatedly overwrites your custom configuration.

Windows 11 Tweaks Worth Testing

Engine.ini is only one part of the performance equation.

If Breathedge 2 still feels inconsistent after changing the configuration, take a look at Windows itself.

Hardware-Accelerated GPU Scheduling

On supported Windows 11 systems, you can test Hardware-Accelerated GPU Scheduling.

Go to:

Settings → System → Display → Graphics

Look for the Hardware-Accelerated GPU Scheduling option and enable it if available.

Restart Windows afterward.

Performance results can vary between hardware and driver versions, so treat HAGS as a test, not a guaranteed FPS boost.

If frametimes become worse after enabling it, turn it back off.

Force Breathedge 2 to Use Your Dedicated GPU

This one is especially important for gaming laptops and systems with integrated plus dedicated graphics.

Open:

Settings → System → Display → Graphics

Use Browse to locate the Breathedge 2 executable.

A Steam installation may have a path resembling:

Steam\steamapps\common\Breathedge 2\

Select the game’s executable, then choose:

Options → High Performance → Save

This tells Windows to prefer the high-performance GPU for the game.

If your laptop has both an integrated GPU and a dedicated NVIDIA or AMD GPU, this is worth checking before you start messing with dozens of advanced settings.

Use a Sensible FPS Cap

Here’s another thing I’ve learned after years of PC gaming:

Maximum FPS isn’t always the same thing as maximum smoothness.

If your monitor runs at 144 Hz and your system is capable of staying comfortably above that number, an external FPS cap around 141 FPS can be a good starting point when using VRR technologies such as G-Sync or FreeSync.

For a 165 Hz display, you might test around 162 FPS.

The exact cap depends on your monitor, VRR implementation, driver behavior, and how consistently your PC can hold the target.

I’d rather play at a stable 90 FPS than watch the counter bounce wildly between 120 and 170 while frame pacing feels awful.

Disable in-game VSync if you’re deliberately using an external frame limiter and VRR configuration, then test the result.

Don’t Forget Your GPU Drivers

This sounds painfully obvious, but it gets overlooked constantly.

A new game build plus an old graphics driver is not a great combination.

If Breathedge 2 has recently received an update, check whether NVIDIA or AMD has released a driver with game-specific fixes or shader optimizations.

After installing a major driver update, allow the game some time to rebuild its shader caches.

The first run can sometimes be less representative of normal performance.

How to Test Whether the Fix Actually Worked

Don’t just launch the game, stare at the FPS counter for thirty seconds, and declare victory.

Use the same test route before and after applying the tweaks.

For example, measure performance while:

• Entering a dense space station.
• Flying through an area with lots of debris.
• Turning rapidly toward previously unseen geometry.
• Triggering effects-heavy gameplay sequences.
• Moving between areas that normally cause hitching.

Pay particular attention to 1% lows and frame-time graphs, not just average FPS.

If average FPS changes from 82 to 85 but frame pacing becomes dramatically cleaner, I’d call that a win.

If average FPS goes up but the game develops new visual glitches, crashes, texture pop-in, or unstable frame times, revert the offending setting.

How to Fix Breathedge 2 Crash on Launch, Black Screen, and Desktop Crashes on Windows PC

What I Would Change First

If you don’t want to throw the entire Engine.ini configuration at the game immediately, I’d test changes in stages.

First: deal with texture streaming and obvious post-processing overhead.

Second: test shader and rendering-related parameters.

Third: adjust shadows and image-quality settings.

Fourth: move on to Windows graphics settings and FPS limiting.

That approach makes troubleshooting much easier.

If you change 40 settings simultaneously and performance improves, you won’t know which setting actually helped. If something breaks, you’ll have no idea what caused it either.

That’s the classic PC tweaking rabbit hole.

How to Fix Breathedge 2 Crash on Launch, Black Screen, and Desktop Crashes on Windows PC

Final Thoughts

Breathedge 2 has the kind of PC performance profile that can make you question your entire setup. One moment everything feels perfectly smooth, and the next you get a tiny hitch that completely destroys the rhythm of exploration.

And when you’re playing at a high refresh rate, those little frame-time spikes are impossible to unsee.

The Engine.ini configuration above is designed as a performance-focused baseline, targeting texture streaming, rendering overhead, shadows, anti-aliasing, shader handling, post-processing, and multi-threaded rendering behavior.

Just keep expectations realistic.

There is no Engine.ini line that can turn a low-end GPU into a flagship card. If your hardware is genuinely below the game’s requirements, you’ll still need to lower normal graphics settings, resolution, or upscaling quality.

But if your PC should be capable of running Breathedge 2 comfortably and you’re mainly fighting micro-stutters, inconsistent frame pacing, asset-streaming hitches, and unnecessary visual effects, these tweaks are absolutely worth testing.

The biggest improvement may not show up as a giant number on the FPS counter.

It may simply be that the game finally feels smooth when you’re moving through space.

And honestly, that’s what I care about far more than seeing an impressive FPS number while the game still feels like it’s hitching every few seconds.

Breathedge 2 | Everything You Need To Know About Upgrades | Early Access