#Rewired unity forums code
#Rewired unity forums windows

If you think exposing a way to forward the Raw Input messages back to Unity is feasible, I would be open to using it.

#Rewired unity forums code

Not that it's important, but Rewired's Raw Input implementation is fully C# managed code using P/Invoke.

Unity's message pump dispatches the messages, Rewired's WndProc receives them, then Rewired forwards the message to Unity by calling its WndProc manually using CallWindowProc. It creates a message window and registers to receive the Raw Input messages for devices to that HWND. Rewired does not actually have its own message pump at present. I did notice in my testing that Unity's legacy input system's mouse button events still work however, leading me to conclude Unity is using some other means for that information like WM_LBUTTONDOWN. Even though Unity's mouse input is now broken, Rewired's now works again. Rewired receives the Raw Input event before Unity, empties the buffer, then sends the event to Unity which results in the reverse problem of Unity's mouse input only receiving the first event and missing all the rest. The only solution I can see would be to change Rewired to no longer forward the messages to Unity and just break Unity mouse support when using Rewired.Ĭlick to expand.Thanks for the code example! There are a number of features in there I wasn't aware of like PlayerLoopSystem.Īs a test, I implemented GetRawInputBuffer in Rewired and it works as I expected it would.

Rewired processes the first message, then forwards it to Unity, at which point GetRawInputBuffer is called, consuming all the remaining Raw Input events for the mouse for that frame.īecause Unity is consuming all the Raw Input messages from the queue, Rewired doesn't receive anything after the first event, and therefore misses many events. (And the forwarding trick fails in the new input system because of threading.)Ĥ. Keyboard and HID device events are not forwarded because Unity does not use them (in the legacy input system). Rewired processes the mouse event, then forwards it to Unity's WncProc so Unity can use the event also so Rewired doesn't break Unity's mouse input. This prevents Unity from receiving those events because only one Window may receive events per application.ģ. Rewired registers with Raw Input to receive mouse, keyboard, and HID controller events. Rewired creates a hidden message window.Ģ. How do you implement raw input? Do you spawn your own invisible window that you register for raw input notifications (like DirectInput)? Or are you piggybacking off Unity's WndProc?Ĭlick to expand.That is definitely the cause.ġ. Could you try using 2021.2.0b.2.0b9 to see if it started happening in b9?

#Rewired unity forums windows

Using that API removes these events from Windows event queue so they no longer arrive through the WndProc. The fix was to use the GetRawInputBuffer() API instead, which allows processing all queued raw input events at once without pumping them through the Windows message loop. I could reproduce this issue even in an empty win32 app that did practically nothing (no Unity involved). The bottleneck was between PeekMessageW() and GetRawInputData() Windows APIs - it would acquire a mutex inside the kernel every time you tried to retrieve a raw input message, and with 8000 events per second the contention was just too high. We found that when using very high input polling rate mice (tested with 8000 Hz), the framerate would drop dramatically, to the point where processing mouse events was taking longer than receiving them. The only thing I can think of that could have caused this is this fix: