Crash in WEBGL games builds using new input system

[Swing Wren]

After activating the new input system within the Dialogue System this crash shows in WEBGL builds:

Code: Select all

27eb72b1-b4ac-4697-82ac-4feef5c84fdc:8 ArgumentNullException: Value cannot be null.
Parameter name: statePtr
  at UnityEngine.InputSystem.InputControl`1[TValue].ReadValueFromState (System.Void* statePtr) [0x00000] in <00000000000000000000000000000000>:0 
 
(Filename: currently not available on il2cpp Line: -1)

Using unity 2019.3.13
Using Input system 1.0.0

Tried to build in development mode but the error just gets more generic.
What could be the cause?

[Tony Li]

Hi,

Can you try building a very simple scene? Here's one that works for me in WebGL with the new input system:

Test_DS_New_Input_2020-05-16.unitypackage

If that works, gradually add a few things from your own project until you find what breaks it.

[Swing Wren]

Tried importing the dialogue system in a new unity project, enabling new input system within unity, importing the dialogue system, enabling new input system in dialogue system, building in WEBGL but the problem persists.

[Tony Li]

Hi,

If you play in the editor, are there any warnings or errors in the Console window?

Please check the Dialogue Manager's Input Device Manager component. If any of the foldout lists reference keycodes that start with "Joystick", remove those keycodes.

[Swing Wren]

Hello!

I can't see any errors in neither in the windows standalone, mac nor WEBGL in the editor. The Dialogue Manager's Input Device Manager you provided in the package doesn't have any and I checked again to be sure. Just In case I changed the input device to Mouse in the Device Manager. After all this the problem persists.

Can you reproduce the error?

[Tony Li]

Hi,

I can't reproduce the error.

Here's a WebGL build: https://www.pixelcrushers.com/dialogue_ ... nput_test/

It uses Unity 2019.3.13f1, Input System 1.0.0, and Dialogue System 2.2.6.

I tested it with Chrome and Edge on Windows.

Can you send a copy of your project to tony (at) pixelcrushers.com?

[Swing Wren]

Your project has the crash too you don't see this error in the console? Tested in firefox, chrome, opera and safari in a windows and a mac computer. Maybe we can setup a call or something.

[Tony Li]

Hi,

That's unexpected. This is in Chrome on Windows 10,:



I'll test on other platforms, too, and let you know the results.

What operating system versions are you using on Windows and Mac?

The error certainly looks like it's coming from the Input System module, not from the Dialogue System. It may have something to do with your specific input devices. There are a few other reports of the same issue on the forums, but none of them include a resolution.

Would you please submit a bug report to Unity?

If you'd like to do a screen share, please feel free to contact me on discord. The Pixel Crushers discord server is: https://discord.gg/FwUaCNt

However, since this appears to be an Input Module bug, I doubt there will be anything I can do. It will probably need to be fixed by Unity.

[Tony Li]

Here's a forum post from a Unity dev with a possible workaround:

https://forum.unity.com/threads/new-inp ... st-5742868

[Tony Li]

What system language are you using in your OS? (English, Spanish, Korean, etc.) It's a long shot, but maybe the Input System has issues with some system languages.