Search Issue Tracker
Fixed in 10.1.0
Votes
0
Found in [Package]
9.0.0-preview.33, 8.2.0, 8.1.0, 8.0.1, 7.4.1, 7.3.1.
Issue ID
1262990
Regression
No
[HDRP] "New Environment Library" is not set by default in the "Look Dev" window when its opened from Inspector
On the opening "New Environment Library" in "Look Dev" window from the Inspector then it is not set by default in the "Library" input field and the input field is always set as "None" but the empty environment can be added under Environment Library in the Look Dev window, refer attached video
Steps to repro:
1. Create a new project with HDRP Template
2. Project window > Create > Look Dev > Environment Library
3. Project > New EnvironmentLibrary > Inspector > Open in Look Dev window
Actual Result:
Selected "New Environment Library" is not set by default in Library input field when Look Dev window is opened from Inspector
Expected Result:
Selected "New Environment Library" should be set as default input field of Library in the Look Dev window
Reproducible in:
2020.2.0a18, 2020.1.0b16, 2019.4.3f1, 2019.3.15f1 with Package Version 9.0.0-preview.33, 8.2.0, 8.1.0, 8.0.1, 7.4.1, 7.3.1.
Environment:
Occurring on Windows 10 & macOS 10.15
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment