Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.3.0b9
6000.0.0b11
Issue ID
UUM-48128
Regression
No
Fog Pass is missing when Scenes are in the Asset Bundles
How to reproduce:
1. Open the attached project “URPRendererTest.zip“
2. Open the “ExampleScene” Scene
3. Open the Build Settings (Edit > Build Settings…)
4. Make sure the “GameCore - Xbox Series” platform is selected
5. Open the Addressables window (Window > Asset Bundles > Addressables > Groups)
6. Build the Addressables (Build > New Build > Default Build Script)
7. Open the Build Settings then Build and Run
8. Open the Frame Debugger (Window > Analysis > Frame Debugger)
Expected result: The Deferred Fog count is 1
Actual result: The Deferred Fog count is 7
Reproducible with: 1.21.9 (2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6)
Couldn’t test with: 1.21.9 (2020.3.46f1) - due to errors in the Console window
Reproduced on: Windows 11 Pro
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.