Controller input locks up after intense RUMBLE.

[NUK3TH3WHAL35]

Using 8bitdo's N64 Modkit, Betterjoy recognizes the pad as a Pro Controller when using the "Add Controller" feature. However, in game, when moderate RUMBLE is active, input is killed. The controller is still "active" as RUMBLE will continue to occur as expected (getting shot or crashing Arwing in Star Fox 64) it's just that input is dead and the pad "locks up" and is stuck in the last known input. Not just within a particular program, but rather across Windows as a whole. Only option is to turn off controller and turn back on. However, the problem persists.

The expected behavior of course is for this NOT to happen. This ONLY occurs through the use of Betterjoy as emulators that allow native use of the N64 pad and don't need to be veiled as an XBOX 360 controller, behave as normal with expected behavior. However, some emulators will need the use of Betterjoy for full functionality. Project64 for example will need betterjoy to have RUMBLE function with it's NRage v2.0 XINPUT plugin.

The controller being used is 8bitdo's N64 Modkit (BTW, the PC identifies the pad as N64 Controller just as it sees the official N64 NSO controller).
The "emulated" designation is as a Pro Controller within Betterjoy itself.

This is connected wirelessly through BT and it occurs whether its 4.0+ or 5.0+.

Official N64 NSO controllers are not affected by this bug.