Search Issue Tracker
Won't Fix
Under Consideration for 6000.4.X
Votes
0
Found in
6000.4.0a1
Issue ID
UUM-119540
Regression
No
NullReferenceExceptions are constantly spammed when setting "Visual Effect" Active Target in Shader Graph
How to reproduce:
1. Create a new Unity project
2. In the Project window, right-click -> Shader Graph -> Blank Shader Graph
3. In the Graph Inspector -> Graph Settings, under the "Active Targets" click "+"
4. Select the "Visual Effect" and observe the Console
Expected results: No errors are spammed
Actual results: "NullReferenceException" errors are constantly spammed while the target is set
Reproducible with: 6000.4.0a1
Can't test with: 6000.57f1, 6000.2.6f1, 6000.3.0b2 (no such option)
Reproducible on: macOS Sequoia 15.6 (M1)
Not reproducible on: No other environment tested
First lines of error:
NullReferenceException: Object reference not set to an instance of an object
UnityEngine.Rendering.Universal.UniversalRenderPipeline.RenderSingleCameraInternal (UnityEngine.Rendering.ScriptableRenderContext context, UnityEngine.Camera camera, UnityEngine.Rendering.Universal.UniversalAdditionalCameraData& additionalCameraData, System.Boolean isLastBaseCamera) (at ./Library/PackageCache/com.unity.render-pipelines.universal@f90c9a894466/Runtime/UniversalRenderPipeline.cs:694)
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
- Terms of Service agreement checkbox is invisible under specific OS system themes (UI Accessibility)
- Tile Palette: "Create New Tilemap" dropdown area is displayed in several colors
- Input.mousePosition stops syncing to touch input when using "DownloadHandlerTexture" in WebGL build
- UI Builder canvas doesn't update element styling accordingly when changing Active Theme for some Editor Authoring elements
- Selector Value buttons are not aligned with parameters in UI Builder
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.