When using Convolution Bloom and Local Exposure (with high Detail Strength values), the bloom gets a lot of popping/flickering/artifacts. Setting r.Bloom.ApplyLocalExposure=False eliminates these artifacts regardless of your bloom and local exposure settings.
But after doing this, the editor will frequently experience this crash with this assert:
Assertion failed: bLocalExposureEnabled || bThresholdEnabled [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Renderer\Private\PostProcess\PostProcessBloomSetup.cpp] [Line: 129]
The crashes occur at random, even while the editor is idle or simply moving your mouse around the UI.
If left at its default r.Bloom.ApplyLocalExposure=True, then this crash will never occur.
I have been experiencing this throughout 5.x as more local exposure settings were added that had issues with convolution bloom.
Steps to Reproduce
Crashes are difficult to reproduce as they occur at random, even when the editor is sitting idle or moving the mouse around the UI.
But the crashes *only* occur after r.Bloom.ApplyLocalExposure is set to False while Bloom Method is set to Convolution (haven’t tried Standard).
If r.Bloom.ApplyLocalExposure is left to its default True, then this crash never occurs.
Hello,
Thank you for reaching out.
I’ve been assigned this issue, and we will be looking into this check() inside of bloom for you.
Hello,
Thank you for reporting this.
This issue has already been fixed as part of Unreal Engine 5.6. You can find the fix in CL: 38191326 on //UE5/Main.
CL Description:
Fix editor crash when using r.Bloom.ApplyLocalExposure=0
Please let us know if this helps.
Hi Stephen,
Thanks so much for the quick replies and for looking into this issue!
That’s great to hear that this has already been fixed for the 5.6 release. We will wait for the 5.6 preview release to verify this fix. If we are still running into the same problem, I will revive this thread. Otherwise, happy to consider this matter resolved for now!
Thanks again!
Cheers,
Chris
Hello,
I will close this ticket for now. Please feel free to re-open the case if you have additional questions.