Search Issue Tracker
By Design
By Design in 6000.2.X
Votes
1
Found in
2021.3.46f1
2022.3.54f1
6000.0.31f1
6000.1.0a8
6000.2.0a1
Issue ID
UUM-90458
Regression
No
Additive Scene is not being rendered when Render Graph Compatibility Mode is turned off in the Project Settings
How to reproduce:
1. Open the attached “IN-89821.zip” project
2. Open the “A” Scene
3. Enter Play Mode and observe the Game View
4. Exit Play Mode
5. Turn off the Render Graph “Compatibility Mode” setting (Edit → Project Settings → Graphics → Render Graph section)
6. Enter Play Mode and Observe the Game View
Expected result: The Camera is rendering the Additive Scene “B” both in the Camera Preview and Game View
Actual result: The Additive Scene “B” is not being rendered
Reproducible with: 2021.3.46f1, 2022.3.54f1, 6000.0.31f1, 6000.1.0a8
Reproducible on: macOS 15.1.1 (Intel), Windows 11
Note: Issue is also reproducible in Standalone and Android builds
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
The repro project uses two base cameras, one in each additive scene. One base camera has set it's background to uninitialized. With Compatibility Mode enabled, the unitialized background of this camera happens to be what the first camera drew previously, which is why both camera's output is visible. This is incidental behavior, that should not be relied upon. "Uninitialized" means the frame buffer can contain anything. When trying to render two cameras on top of each other, setting the top camera to "Uninitialized" is not the correct approach. Instead, camera stacking should be used, and the top camera should be configured as an overlay camera. Please refer to https://docs.unity3d.com/6000.0/Documentation/Manual/urp/cameras/camera-stacking-concepts.html for more information
Resolution Note (6000.2.X):
The repro project uses two base cameras, one in each additive scene. One base camera has set it's background to uninitialized. With Compatibility Mode enabled, the unitialized background of this camera happens to be what the first camera drew previously, which is why both camera's output is visible. This is incidental behavior, that should not be relied upon. "Uninitialized" means the frame buffer can contain anything. When trying to render two cameras on top of each other, setting the top camera to "Uninitialized" is not the correct approach. Instead, camera stacking should be used, and the top camera should be configured as an overlay camera. Please refer to https://docs.unity3d.com/6000.0/Documentation/Manual/urp/cameras/camera-stacking-concepts.html for more information