Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2020.2
Issue ID
1263851
Regression
No
[Editor] Preview-related functions are not producing correct visual results
Steps to reproduce:
1. Setup a new HDRP/URP project
2. Create a game object
3. Add an LOD Group component to it
4. Add the Cube itself as a renderer for LOD0
5. Click the LOD 0 button and observe the preview window
Expected result: the mesh is previewed with the correct materials and no visual issues.
Actual result: the mesh is not rendered (HDRP); the mesh has a pink (failed to compile) shader (URP)
Additional note: the Animation Preview window lighting is completely overblown when using HDRP.
Reproducible with: 2018.4.20f1, 2019.4.4f1, 2020.1.0b18, 2020.2.0a16
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
Add comment