I’ve just noticed this too (4.22).
- If you had an analog input axis held when “set input mode UI only” got turned on, then it will keep passing through that axis value while the mode is on. You can manually filter this out with “Set ignore move input” or with your own “Input Is Enabled” bool in your playercontroller. BUT
- Even if you do that, when you turn back on “input mode game”, the input axis still triggers events with a non-zero value for a while afterward… (like it has “saved up the events” during the UI-only input mode time) not sure how to get around this in blueprint just yet
If I ever get close to shipping the game, will most likely have to fix it in C++