Hi, Very simple issue, I have a printstring triggered by pressing down on the gamepad’s d-pad. The printstring has a breakpoint enabled on it - I used to use this as a hack way to freeze the blueprint execution. However, this breakpoint is being ignored and I am completely baffled as to why this no longer works for me. I went through various posts and dug into whatever settings I could find related to input but no dice so far.
Hello,
I have attempted to reproduce the issue that you are experiencing, but I was unable to do so. I created an InputAction using an ‘E’ key press, and placed a print string with a breakpoint on it. After pressing E, my blueprint execution was paused successfully. Have you been able to reproduce this issue in a clean project?
Hello,
I am marking this topic as resolved as I have not heard back from you in a few days. If the problem is still occurring, feel free to respond to this answer and I’ll be glad to help.
Ah I believe what was happening here was the input was being consumed by something higher up the input chain. Thanks for your time!