Debug updater not compatible with new input system

I just tried to make an URP project and ran into this issue:

InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings.
UnityEngine.Rendering.DebugManager.SampleAction (System.Int32 actionIndex) (at Library/PackageCache/com.unity.render-pipelines.core@7.1.6/Runtime/Debugging/DebugManager.Actions.cs:111)
UnityEngine.Rendering.DebugManager.UpdateActions () (at Library/PackageCache/com.unity.render-pipelines.core@7.1.6/Runtime/Debugging/DebugManager.Actions.cs:168)
UnityEngine.Rendering.DebugUpdater.Update () (at Library/PackageCache/com.unity.render-pipelines.core@7.1.6/Runtime/Debugging/DebugUpdater.cs:18)

I am trying to see how the new input system works for version 2019.3.0f1 and due to this I get 1000 errors in record time in the console… Is this a compatibility issue between the 2? There doesn’t seem to be an update to either of the packs I can install and this is leaving me rather confused. Has anyone encountered this issue? And if so, what can I do about it? Is this something because of the preview?

What I assume is happening is that the URP does not have an implementation of the new input system yet, which is causing it to throw this error.

5262527--526499--upload_2019-12-9_16-41-16.png

I tried uninstalling the URP package and now the errors are gone, so it must not be compatible yet. Can someone confirm this?

Having the same issue here; I think you are correct. Deleting the [Debug Updater] gameobject that the URP scripts create fixes the issue; I’d assume (but haven’t yet tested) that this wouldn’t be an issue in release builds. But… it is horrible.

Same Issue, I was about to report the issue but this thread came up in the Bug Reporter search box. Since the debugging tool it should be provided elsewhere for those that need to debug rendering and avoid breaking compatibility between packages.

This sort of blocking issue prevents people from reviewing the InputSystem and giving valuable feedback.

Same issue here. So far, I’ve been able to fix this by changing “Project Settings > Player > Active Input Handling” to Both. Not sure if this is a full solution, but the error disappeared for now.

1 Like