Search Issue Tracker
Fixed
Fixed in 6000.4.0b1, 6000.5.0a3
Votes
0
Found in
6000.4.0a4
6000.5.0a1
Issue ID
UUM-125858
Regression
Yes
Errors “ArgumentNullException: Value cannot be null.“ and “NullReferenceException: Object reference not set to an instance of an object“ are present when clicking "Fix All" in the HDRP Wizard window
Reproduction steps:
1. Create and open a new project
2. Open Package Manager (Window > Package Manager)
3. Install “High Definition Rendering Pipeline“
4. Open HDRP Wizard (Window > Rendering > HDRP Wizard)
5. Click “Fix All“
Expected result: No Errors exist
Actual result: Errors “ArgumentNullException: Value cannot be null.“ and “NullReferenceException: Object reference not set to an instance of an object“ are present
Reproducible with: 6000.4.0a2, 6000.4.0a4
Not reproducible on 6000.0.62f1, 6000.2.10f1, 6000.3.0b7, 6000.4.0a1
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- “Create or Load HDRenderPipelineAsset” prompt is not present
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.