Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
1
Found in
6000.0.66f1
6000.3.6f1
6000.4.0b5
6000.5.0a6
Issue ID
UUM-133327
Regression
No
Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
How to reproduce:
1. Create a new HDRP Unity project
2. Go to Window -> Rendering -> Look Dev
3. Close the project and create a new HDRP project
4. Observe the newly created project
Expected results: No errors are spammed and the project has no issues
Actual results: Errors are constantly spammed as long as Look Dev window is opened, Look Dev window is empty and HDRP Wizard reports issues
Reproducible with: 6000.0.66f1, 6000.3.6f1, 6000.4.0b5, 6000.5.0a6
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
Note: Reproduced across all
First lines of errors:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.Rendering.LookDev.DisplayWindow.UnityEditor.Rendering.LookDev.IViewDisplayer.GetRect (UnityEditor.Rendering.LookDev.ViewCompositionIndex index) (at ./Library/PackageCache/com.unity.render-pipelines.high-definition@f53f75aa7f4a/Editor/Tools/LookDev/DisplayWindow.cs:507)
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 (6000.5.X):
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.