Search Issue Tracker
By Design
Votes
0
Found in
6000.0.47f1
6000.1.0b15
6000.2.0a9
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-103058
Regression
No
UGUI Shader Sample uses old Input System causes errors in the Console
Steps to reproduce:
- Create new Unity Project
- Make sure Shader Graph package is imported to the project
- In Package Manager select Samples
- Import UGUI Shaders Sample
- Open "UISampleScene" (Assets > Samples > Shader Graph > 17.0.4 > UGUI Shaders > Scenes
- Enter the Play mode and observe the Console
Actual results: "InvalidOperationException" errors are spammed in the Console
Expected results: No errors, UGUI Sample should be working without any issues
Reproducible with versions: 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Can’t test with versions: 2022.3.61f1 (UGUI Shader sample not available)
Tested on (OS): Windows 11 (22H2)
Notes:
- 6000.0.47f1 uses Active Input Handling > Both, but after switching to New Input System in Player settings, errors are spammed in the Console. On higher U6 versions, you need to switch to old Input System for Sample to work, because it is using New Input System.
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
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
Resolution Note:
There is a Note in the sample itself that provides an explanation to why this happens and how to rectify the issue.