Hi,
it seems like every time a Node like “Set Input Mode Game and UI” is called, it’s called on top of each other.
If I call “Set Input Mode Game only” as next, the “Game” will get back the control.
However, if I call “Set Input Mode Game and UI” and then again “Set Input Mode Game and UI” for a different Widget, I have to call “Set Input Mode Game only” twice to get back the control. If you call “Set Input Mode Game and UI” 20 times, you have to call “Set Input Mode Game only” 20 times aswell too to gain back the control.
Hello ,
I was unable to reproduce this issue with the information provided. I have a few questions that will help narrow down what issue it is that you are experiencing.
Quick questions:
- Can you reproduce this issue in a clean project?
- If so, could you provide a detailed list of steps to reproduce this issue on our end?
- Could you provide a screen shots of any blueprints that may be involved with this issue?
Apparently it appears that the “Set Ignore Look Input” node is responsible for this.
While I’m certain that I’ve tested negative for this node before my report, I’m unable to reproduce it today. In addition there is a Bug report for the “Ignore Look Input” node, showing the exact same behavior I reported. So I probably made some mistake at my test setup and my Issue is related to the “Set Ignore Look Input” node. It is tracked at Bug? Ignore look input doesn't behave like a bool - Programming & Scripting - Epic Developer Community Forums