Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Should not get here" spam when switching Input Action Maps #757

Closed
Chifilly opened this issue Aug 2, 2019 · 1 comment
Closed

"Should not get here" spam when switching Input Action Maps #757

Chifilly opened this issue Aug 2, 2019 · 1 comment
Labels
bug Issues where existsing functionality misbehaves

Comments

@Chifilly
Copy link

Chifilly commented Aug 2, 2019

I have an issue that when I switch from my Player input actions to my UI input actions and back again, I get endless spam whenever I move my mouse.

It's spamming the following error repeatedly:

Should not get here
UnityEngine.InputSystem.LowLevel.<>c__DisplayClass7_0:<set_onUpdate>b__0(NativeInputUpdateType, NativeInputEventBuffer*)
UnityEngineInternal.Input.NativeInputSystem:NotifyUpdate(NativeInputUpdateType, IntPtr)

This only started happening when I used InputSystemUIInputModule, and it causes the editor to slow to a crawl, since it throws an error every frame I move my mouse.

I use the code inputScript.SwitchCurrentActionMap("UI"); to switch to the UI input actions, and then when I go back into play mode I use inputScript.SwitchCurrentActionMap("Player");. It's only after I've switched from UI to Player (or to any other input action) that this issue starts.

EDIT:
Just found out that all actions cause the spam, not just the mouse, I just hadn't noticed it before since WASD are an "on-off" system whereas mouse movement is pretty much triggers constantly when moving the mouse

After more testing, it doesn't happen if I start on the UI map, then switch to Player, I can do this as much as I want and it's fine, but if I start on Player then switch to UI then back to Player, the issue happens

@Rene-Damm Rene-Damm added the bug Issues where existsing functionality misbehaves label Aug 12, 2019
@Rene-Damm
Copy link
Contributor

Should be fixed in 1.0.0-preview.1 by #883. Some state was set up incorrectly when composites were used and there was more than one map.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues where existsing functionality misbehaves
Projects
None yet
Development

No branches or pull requests

2 participants