mirror of
https://github.com/bevyengine/bevy
synced 2024-11-26 22:50:19 +00:00
3df7f895f4
# Objective Currently, if we have two cameras with the same output texture, one with `CameraOutputMode::Write` and one with `CameraOutputMode::Skip`, it is possible for the `CameraOutputMode::Write` camera to be assigned alpha blending (which is the fallback blending when multiple cameras write to the same output texture), although it is the only camera writing to the output texture. This may or may not happen every restart of the app, because the camera iteration order in prepare_view_upscaling_pipelines isn't consistent. Since this is random behaviour I consider this a bug and didn't add a migration guide. ## Solution In `prepare_view_upscaling_pipelines` make sure we don't consider cameras with CameraOutputMode::Skip to be outputting something to the output texture. ## Testing I ran a few examples to make sure nothing obvious is broken. There is no example using CameraOutputMode::Skip, so I only tested the change in my own App where this was relevant, which however isn't public. |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
Bevy Core Pipeline
