Search Issue Tracker
Fixed in 9.0.0
Fixed in 8.1.0
Votes
58
Found in [Package]
7.0.1
Issue ID
1176974
Regression
No
Errors are Constantly thrown when Active Input Handling is set to Input System Package
How to reproduce:
1. Create a new URP template project
2. Open Project Settings > Player > Active Input Handling and set it to "Input System Package (New)"
3. Play the Scene
Expected result: Editor plays the scene without any errors
Actual result: Editor is constantly throwing errors
Not reproducible with: 2018.4.7f1, 2019.2.2f1, 2019.3.0a5
Reproducible with: 2019.3.0a6, 2019.3.0a12, 2020.1.0a1
Could not test with: 2017.4(No Package Manager)
Reproducible with package versions: 6.5.3, 6.7.1, 6.9.1, 7.0.1
Workaround: Setting Active Input Handling to "Both"
Notes:
1. The issue only happens if Active Input Handling is set to "Input System Package (New)"
2. Can also be reproduced after removing URP/LWRP.
3. The issue seems to occur with every URP/LWRP version when 2019.3.0a6 or above is used
-
DemonFangZ
Jun 28, 2020 14:57
Fixed for me! Tested on 2019.4.1f1 with URP 7.3.1
-
Napoleonite
Jun 18, 2020 16:41
NOT fixed in 2019.4.1f1
-
aenerv7
Apr 21, 2020 02:54
It still exist after "re-import all". They only way to avoid it with using Input System is setting "Active Input Handling" to "Both". But may be there is some performance cost? I am not sure.
-
Marlonzockt
Mar 22, 2020 14:19
Also happens when using a Cinemachine Free Look Camera
-
FullMe7alJacke7
Mar 02, 2020 01:25
Reimporting the URP 7.2.1 package as suggested on a forum post seems to have resolved my issue.
-
FullMe7alJacke7
Mar 02, 2020 01:13
I'm in the process of switching over to new input system and this is popping up in my project now as well. I did not have UDP or HDRP installed in the project when I brought in the input system, it was only in the project prior but removed before input was changed.
-
JimmyCushnie
Feb 23, 2020 07:56
Never mind, the issue was fixed after a reimport all.
Unity's internal scripting define symbols do not get updated until the entire project is reimported. This is because the system was designed for platform dependent compilation, and when the editor switches platforms a reimport all is performed.
You can fix the issue with right click -> reimport all in the Project window or by deleting your project's Library folder.
-
JimmyCushnie
Feb 23, 2020 07:38
Still happening in URP 7.2.1. This is ridiculous, this is not a hard problem for Unity to fix.
-
Jedyte28351
Feb 12, 2020 19:42
Could it be this also causes the stacktrace every update? https://forum.unity.com/threads/ugui-throws-error-when-used-with-new-input-system.824361/
-
FlipperCanoe163
Feb 08, 2020 13:17
HDRP too!
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
- Warnings are missing when compiling for certain platforms (opengl)
- Scaling problem with PanelSetting set to ScaleWithScreen/Expand
- [Hub] Editor is shown in the "Installing" state indefinitely when the installation fails due to INVALID_DESTINATION error
- Searching packages on an ill-configured scoped registry targeting Google Unity API registry throws an error
- Not possible to deduce the source of 'Shader properties can't be added to this global property sheet.' error
Resolution Note (fix version 9.0.0):
We disabled the runtime inputs for projects that are only using the new input system. We'll make the debug menu work when the new input system will be out of preview.
Fixed in 2020.2.0a9 and URP 9.0.0. Please note that for the fix to work both Editor and Package versions must be matched.
Resolution Note (fix version 8.1.0):
Fixed in 2020.1.0b9 and URP 8.1.0
Resolution Note (fix version ):
Fixed in 2019.3.15f1 and URP 7.3.1