Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.57f1
Issue ID
UUM-96416
Regression
No
ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
Reproduction steps:
1. Open the attached “IN-93800” project
2. In the Assets/Bug folder open the “BugScene” Scene
3. In the Hierarchy select the Directional Light GameObject
4. In the “Umbra Soft Shadows” Script component make sure the “Overlay Shadows” option is enabled
5. Open the Scene view
6. In the Hierarchy select the Main Camera GameObject
7. Observe the Console
Expected result: No errors appear in the Console
Actual result: 1 “ArgumentNullExceptionError” and 1 “Assertion Failed error” appears
Reproducible with: 2022.3.7f1, 2022.3.57f1
Not reproducible with: 6000.0.0b11, 6000.0.36f1, 6000.1.0b5, 6000.2.0a2
Could not test with: 2021.3.48f1, 2022.3.0f1, 2022.3.6f1, 2023.1.0a1, 2023.3.0b10 (Multiple “does not contain a definition for”, “could not be found” errors)
Reproducible on: Windows 11, macOS 14.5(Silicon) - user’s
Not reproducible on: No other environments tested
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.