Blueprint Debugging - F10 Step Key Does not work
When debugging blueprints the "Step to the Next Node" using the F10 key does not work on OSX or Windows, using UE4 4.7.3.
asked Mar 25 '15 at 10:03 AM in Bug Reports
Was this ever fixed?
answered Apr 11 '17 at 12:12 AM
Thank you for letting us know that F10 doesn't work when a breakpoint is added to the node. I have reproduced this issue in-house and verified that the issue was already entered into our system. If for any reason you need to reference this bug, please refer to: UE-9771
If you have any further questions, please do not hesitate to submit a new question to AnswerHub!
answered Mar 25 '15 at 03:18 PM
Here we are 7-17-17, 845 days later. 581 Work Days. 4,648 work hours. Is this still a priority 3 bug? Can we assume now Priority 3 means, "Meh, not going to bother with it?"
answered Jul 17 '17 at 06:49 PM
Hey... Are you selecting the right instance to be debugged?
I find out that if you have a wrong instance selected, it will not stop in your breakpoint. Make sure you specify the right instance, or at least don´t specify any if you don't know or you want any...
Also, keep in mind that when you debug one instance, probably the instance selection will set to that instance automatically, and this could be a confusion because you believe that you have it in "Any".
answered Jul 17 '17 at 06:54 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here