Search Issue Tracker
Fixed
Fixed in 2022.3.11f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a4
Votes
1
Found in
2022.3.3f1
2023.1.2f1
2023.2.0a21
2023.3.0a1
Issue ID
UUM-40770
Regression
Yes
Post-Processing behaves differently when used on different Cameras
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/TestPPAA.unity” Scene
3. Enter the Play Mode
4. In the Hierarchy Window, select “TestingCode” GameObject
5. In the Inspector Window, under the “Test Pp Aa (Script)” Component, check and uncheck various properties
Expected result: Post-Processing is applied the same, regardless of the Camera
Actual result: Post-Processing is applied differently for each camera and if Anti-Aliasing is disabled, PP only works for the last Overlay Camera
Reproducible with: 2022.2.15f1, 2022.3.3f1, 2023.1.2f1, 2023.2.0a21
Not reproducible with: 2021.3.27f1, 2022.2.14f1
Reproducible on: Intel MacOS 13.4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Video preview in the Inspector freezes shortly after the first play and does not recover until paused and replayed
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
Add comment