Search Issue Tracker
Fixed in 2022.2.X
Votes
5
Found in
2019.4
2020.3
2020.3.21f1
2021.1
2021.2
2022.1
Issue ID
1377839
Regression
No
[URP] Motion blur applies on non-moving cameras when using different Volume Masks
Reproduction steps:
1. Open user-submitted project
2. Open Game View Tab
Expected result: Motion Blur is not applied to either of the cameras
Actual result: Motion Blur is applied to both cameras
Reproducible with: 7.7.1 (2019.4.32f1), 10.7.0 (2020.3.22f1), 11.0.0 (2021.1.28f1), 12.1.0 (2021.2.1f1), 13.1.0 (2022.1.0a14)
Comments (1)
-
miracletechteam1
Nov 13, 2021 06:01
Really need this if we make local multiplayer games
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.2):
Fixed in 14.0.3 (2022.2.0a16)
Multiple cameras are now able to be used at the same time with motion blur applied.