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
-
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!
-
Snigros
Jan 29, 2020 03:49
...and still appears to be there in 2019.3.0f6!
-
Din0m1te
Jan 28, 2020 14:06
Issue still exists in URP 7.1.8. Common guys, this needs to be fixed.
-
FIGURAMA
Jan 24, 2020 08:41
Why URP depends on Input???
-
Jichaels
Dec 30, 2019 10:05
Bump, still present in 2019.0.3 RC4 / URP 7.1.7. It is really annoying and shouldn't be hard or long to fix, please !
-
stephanedupont
Dec 29, 2019 08:29
The fix mentioned by MisterRogers allows to get rid of errors, but it is not an ideal solution and the problem still remains that HDRP/URP should not throws these errors in the first place.
-
MisterRogers
Dec 28, 2019 20:39
Hi, the 'fix' is
'Yup, starting with 2019.3, anything that uses the old input system when "Active Input Handling" is set to "Input System" in the player settings (which installing the input system package does from the dialog it pops up) will lead to errors as the old input system backends are disabled.
You can set "Active Input Handling" to "Both" to get rid of the errors'
this had been addressed only here.
https://github.com/Unity-Technologies/InputSystem/issues/896 -
stephanedupont
Dec 20, 2019 14:53
Still not fixed in URP 7.1.7
-
The-Oddler
Sep 01, 2019 15:39
Also reproducible with 2019.3.0b1 (package version 7.0.1)
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
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:
Fixed in 2019.3.15f1 and URP 7.3.1