Search Issue Tracker
By Design
Votes
2
Found in
2021.3.15f1
2022.1.24f1
2022.2.1f1
2023.1.0a22
2023.2.0a1
Issue ID
UUM-21126
Regression
No
HDRP shader variant does not appear in Build when used by Addressables
Reproduction steps:
1. Open the attached “TestHDRPBug.zip“ project
2. Open “SampleScene” scene
3. Build and Run the project
4. Press the 'S' key which changes the current HDRenderPipeline and observe the Build window and Development Console
5. In Editor find GameObject "TestBugCube" and add HDRenderPipeline asset "TestHDRPAsset" to "TestHDRP Bug Script" Component field "Empty Slot For Hd Render Pipeline"
6. Build and Run the project
7. Press the 'S' key and observe the Build window and Development Console
Expected result: All objects are visible in Build
Actual result: Objects are not visible, Build window is black and there are errors in Development Console
Reproducible with: 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22
Could not test with: 2020.3.42f1 (Due to errors in Development Console)
Reproduced on: macOS Monterey 12.6 (Intel)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This usage is currently not supported.
We can't have in an asset bundles HDRP Asset with different settings than what have been used for the player - shader variant will not exist. Only way to make this working is to have all possible settings case inside the Player to force all shader variants generation.