Search Issue Tracker
Active
Fixed in 7.5.2, 8.3.1
Votes
4
Found in [Package]
9.0.0-preview.0
Issue ID
1224369
Regression
No
[URP] 'Uninitialized' camera background type does not match between the Build and Game view
How to reproduce:
1. Open the attached project named "Case_1224369"
2. Open the SampleScene
3. Select the Main Camera and observe that the Background Type under the Environment settings is set to "Uninitialized"
4. Open the Game view. The background is Lime green(The last set Solid Color before Type was switched to Uninitialized)
5. Build and run the project
6. Observe the screen
Expected result: The Build and Game view match
Actual result: The background is not set in the Build indicating the mismatched behavior
Reproducible with: 2019.3.6f1, 2020.1.0b3, 2020.2.0a4
Could not test with: 2017.4.38f1(No Package Manager), 2018.4.19f1(Uninitialized type is missing)
Reproducible with package versions: 7.1.2, 7.2.1, 9.0.0-preview.0
Notes:
- Uninitialized background type became available in URP 7.1.2 (2019.3.0b4)
Comments (11)
-
const_cast
Jan 26, 2021 21:26
Still happening in URP 8.3.1 on iOS. Using Unity 2020.1.17f1. Works fine in editor but not on iOS.
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 8.3.1):
Fixed in URP 8.3.1 which is available in Unity 2020.1
Resolution Note (fix version 7.5.2):
Fixed in URP 7.5.2 which is available in Unity 2019.4