[kamicoder]

Objective

• Removing AutoExposure from a camera leaves the auto-exposure effect still applied.
• It only disappears if the camera is recreated.

Solution

• Two worlds exist: the main world and the render world. Each camera is assigned a different ID in each.
• The buffer table is indexed by render-world IDs.
• Removal events arrive using main-world IDs (via RemovedComponents); consequently, the lookup fails, and the buffer persists.
• Additions work correctly because they go through RenderEntity. Only removals were missing the necessary ID translation.
• The fix: retain only those buffers whose corresponding render entity still possesses an AutoExposure component (checked via a view query).
• This works because SyncComponentPlugin already removes the component from the render entity.
• Bonus: when a camera is destroyed, it is no longer present in the views, so its buffer—which was previously leaking—is also cleaned up.

Testing

• Verified in my own engine; the image returns to a neutral state.
• Validated on Bevy 0.19 using a copy of the module; the PR applies this same change to the main branch.
• To reproduce: add AutoExposure to an HDR camera, then remove it during runtime.

AI Disclosure

The AI ​​found the root cause within the Bevy source code and wrote a patch, which I validated in my own engine and reviewed, while ensuring I fully grasped all the implications.

[github-actions]

Welcome, new contributor!

Please make sure you've read our contributing guide, as well as our policy regarding AI usage, and we look forward to reviewing your pull request shortly ✨

[alice-i-cecile]

This is a lot less complex and more reliable: good!