Search Issue Tracker
Fixed
Fixed in 6000.3.14f1, 6000.4.4f1, 6000.5.0b5, 6000.6.0a3
Votes
0
Found in
6000.5.0a5
6000.6.0a1
Issue ID
UUM-130711
Regression
No
Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
Steps to reproduce:
1. Create new Unity project using High Definition 3D Template
2. Open Package Manager window
3. Find and select High Definition Render Pipeline package
4. Select “Samples” tab
5. Import Fullscreen Samples
6. Open Project Settings window
7. Select Graphics tab
8. Find Default Profile or LookDev Profile
9. Change Profile to “NightSkyRenderingSettings Profile (Volume Profile)”
10. Observe Console window
Actual results: Error “KeyNotFoundException: The given key 'NightSkyRenderingSettings Profile (UnityEngine.Rendering.VolumeProfile)' was not present in the dictionary.” is thrown in the Console window
Expected results: No errors are thrown in the Console window
Reproducible with versions: 6000.0.64f1, 6000.2.15f1, 6000.3.2f1, 6000.4.0b2, 6000.5.0a3
Tested on (OS): Windows 11, macOS Tahoe 26.1 (M1)
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note (fix version 6000.5.0b5):
Fixed in 6000.5.0b5
Resolution Note (fix version 6000.4.4f1):
Fixed in 6000.4.4f1
Resolution Note (fix version 6000.3.14f1):
Fixed in 6000.3.14f1