Blue Protocol: Best GameUserSettings for World Boss FPS

The most effective way to stabilize your FPS during world boss encounters is to limit the number of high-quality character models and skill effects rendered at once. In 2026, the game’s engine struggles with “Effect Saturation,” so we target the sg.EffectsQuality and player count variables specifically.

File Path

The configuration file is located in your local app data folder. You should back this file up before making manual edits.

%LOCALAPPDATA%\BPSR\Saved\Config\WindowsNoEditor\GameUserSettings.ini

Technical Note: To truly unlock your performance, find the bUseVSync line and set it to False. Then, ensure your Windows Graphics Settings has “Hardware-accelerated GPU scheduling” turned ON to help the CPU manage the massive draw calls during raids.

Optimized “Raid Performance” Configuration Block

Search for the [ScalabilityGroups] and [/Script/BPSR.BPSRGameUserSettings] sections. If these lines don’t exist, you can add them to force these overrides.

Parameter	Recommended Value	Technical Purpose
sg.EffectsQuality	0 (Low)	Critical. Reduces particle density of other players’ skills.
sg.ShadowQuality	1	Keeps essential shadows for boss telegraphs but removes soft edges.
MaxPlayersOnScreen	5 to 10	Limits high-poly models; other players will appear as low-poly proxies.
bUseDynamicResolution	True	Automatically lowers resolution during the most intense boss phases.
FrameRateLimit	120.0	Prevents the GPU from overworking during downtime to reduce heat.

[ScalabilityGroups]
sg.ResolutionQuality=100.000000
sg.ViewDistanceQuality=2
sg.AntiAliasingQuality=1
sg.ShadowQuality=1
sg.PostProcessQuality=0
sg.TextureQuality=2
sg.EffectsQuality=0
sg.FoliageQuality=1
sg.ShadingQuality=1

[/Script/BPSR.BPSRGameUserSettings]
bUseVSync=False
bUseDynamicResolution=True
ResolutionSizeX=1920
ResolutionSizeY=1080
MaxPlayersOnScreen=10
SkillEffectSelf=0 ; 0 = All, 1 = Simplified, 2 = Minimal
SkillEffectAlly=2 ; Setting to Minimal is a 15% FPS boost in raids
SkillEffectEnemy=0 ; Keep at 0 to see boss telegraphs clearly

HowTo: Engineering Maximum Raid Stability

Follow these GameEngineer.net technical steps to maintain a smooth 60+ FPS during the world boss crusade:

1. The “Max Players” Slider: Even with .ini tweaks, go to the in-game System Settings > Graphics and set “Max Players on Screen” to the lowest comfortable value (usually 5 or 10). This prevents the CPU from choking on player data $D_{poly}$.
2. Skill Effect Filtering: In the “Battle” or “Other” settings, set Ally Skill Effects to Minimal. You only need to see the boss’s effects to survive; seeing 19 other players’ fireworks is the #1 cause of “Raid Lag.”
3. Low Latency Mode: If you have an NVIDIA GPU, set Low Latency Mode to Ultra in the Control Panel. This helps synchronize the “Game Thread” and “Render Thread” during high-load scenarios.
4. The “Fullscreen” Trap: Always play in Exclusive Fullscreen. While “Borderless” is convenient for alt-tabbing, it introduces a Desktop Window Manager (DWM) overhead that can cost you 5–10 FPS during crowded encounters.
5. Character Outline Toggle: Disable the Character Outline in the graphics menu. In a world boss fight with 20+ people, calculating the “ink line” for every character model adds an unnecessary layer of post-processing.

Technical Explanation: Effect Saturation and CPU Bottlenecks

Blue Protocol uses the Unreal Engine to handle massive multiplayer instances. In a world boss fight, the engine must calculate the physics and light-emission for every particle in every player’s skill. This is a linear growth complexity: $O(n \times s)$ where $n$ is players and $s$ is skill effects.

By setting sg.EffectsQuality=0 and SkillEffectAlly=2, we effectively remove the most expensive particle calculations from the pipe. This allows the CPU to spend its cycles on the Network Thread and Animation Thread, ensuring that your dodges remain responsive even when the screen is full of characters. Using bUseDynamicResolution=True acts as a safety net, dropping the internal pixel count slightly if the frame-time ($T_{frame}$) exceeds $16.6\text{ms}$, keeping you at a consistent 60 FPS.