New input system package does not send key events when launching with the "-parentHWND" argument

I'm hosting a Unity application into a WPF "HwndHost". Unfortunately when doing this, the new input system package does not send any keyboard events.

However, using the old input system works without any issues. I have also tested this with the "EmbeddedWindow" project found in the documentation (https://docs.unity3d.com/Manual/CommandLineArguments.html).

Is there something I have to do to get this working or is this simply a bug / not supported?

 

I am having the exact same problem. Would be very glad to know if there is a way around that, or if we need to wait for a fix in the future...

 

I meet this same problem , do you guys find any solution to fixed it ??

 

Hi everyone,

In the post of Lunatix, there is talked about "the old input system works".. Can someone show me a link or some code to tell me what this "old input system" is about?

I am the author of this post on StackOverflow and also very much interested in the problem with the keyboard events. https://stackoverflow.com/questions/54335893/embed-unity3d-app-inside-wpf-without-having-it-take-up-the-whole-window/65995250#65995250 .

Regards,
Joachim

 

https://docs.unity3d.com/ScriptReference/Input.html

 

Have the same issue. When Unity start, the new input system works fine. When it lose the focus, it just stop responding and I tried several ways to give back the focus to Unity and it just won't happen.

Until I find a fix, I am passing key input through a two way named pipeline and the mouse input from the Unity Input system.