[4.7.6] Many problems with the Blueprint debugger

anonymous_user_c0687f281 · June 10, 2015, 9:08am

I often got problems with the blueprint debugger:

The keyboard shortcut for ‘next step’ (F10) doesn’t work while the button isn’t always at the same place
Variables are often reported as out-of-scope when they clearly are not

Return values of functions aren’t reported (on mouse-over it only gives the type of the variable)

It’s the same with current variables of the event graph:

Many calls in the stack trace are doubled (or are they really all called twice?!):

There are some basic features missing, too:

There is no keyboard shortcut for ‘resume’
There is no ‘step-in’, step-over,‘run until here’ etc. which makes debugging unnecessary clunky
There is no ‘watch’ window which shows the values of all variables currently in scope (or only locals)
A little more sophisticated: There are no conditional breakpoints (‘stop if condition X is true’)

Many thanks,

anonymous_user_b9532c9a · June 10, 2015, 6:05pm

Hi ,

Thank you for your report. I have been able to reproduce almost everything here and have entered several bug reports, UE-16804, UE-16809, UE-16813, UE-16814, UE-16817, UE-16824 to be assessed by the development staff. The only piece I could reproduce in 4.7.6 but not in 4.8 was watching values, I did not see any that remained out of scope, however if you have additional steps I can take to reproduce this on my end I’d be happy to take another look.

anonymous_user_c0687f281 · June 11, 2015, 7:15pm

Ok, thank you, I will report back if this happens in UE 4.8.
BTW: How to check the status of bugs, is there anything I can do with this UE-XXXXX IDs (got already about 40 of them or so but no place to looks them up)

anonymous_user_b9532c9a · June 11, 2015, 7:37pm

At the moment it is a bit limited as we don’t have a public bug tracker currently available. What you can do is ask for an update on whichever number you are interested in and we’ll be happy to pull up the information on that particular report for you.

anonymous_user_c0687f281 · June 11, 2015, 9:07pm

Ok, thank you

anonymous_user_b9532c9a · June 12, 2015, 9:52pm

Hi ,

Just a quick update: There is already a resume shortcut, all you should have to do is assign it a key and you’ll be good to go! To find this go to Editor Preferences>Keyboard Shortcuts and type in “Resume” in the searchbar.

anonymous_user_c0687f281 · June 12, 2015, 10:45pm

Hi ,

thanks for the tip, this will save me quite some time when debugging.

anonymous_user_f3fb80e6 · October 9, 2015, 3:37pm

Hey guys, I am experiencing the same issues in UE4.9.2. Are there any news / ETA on that?

anonymous_user_b9532c9a · October 9, 2015, 3:42pm

Hi ,

Currently, most of these are lower priority as our resources are dedicated elsewhere. Unfortunately, I do not have a timeframe of when any of the bugs listed will be addressed.

anonymous_user_f3fb80e6 · October 9, 2015, 3:46pm

That’s sad to hear, as in my opinion debugging is one of the most essential features there is. It’s quite surprising that this is considered low prio at Epic

anonymous_user_c0687f281 · October 11, 2015, 12:44pm

Well, it’s quite depressing to read this low-priority-thing over and over again when it comes to fixing bugs in UE4, months after they have been officially reported.

The Blueprint debugger is a crucial tool which is used every day by anyone who actually tries to work with Blueprints. How can this still (!) be of low priority, even after more than 4 months of waiting?

anonymous_user_e690b31d · November 14, 2015, 11:56am

I’m also quite frustrated with the this issue:

Variables are often reported as out-of-scope when they clearly are not

What is the status of this? (Tried 4.10 still not resolved)

anonymous_user_b9532c9a · November 16, 2015, 6:25pm

Hi deenigeechteik,

Most of the out of scope variable errors have been addressed as of 4.8, though there are two feature requests in the editor for watching local variables within scope. Are there specific times you are seeing variables out of scope?

anonymous_user_e690b31d · November 16, 2015, 6:29pm

After I posted this I realized they might really have been out of scope. I’ll let you know if I find a recurrence of this issue.

anonymous_user_c0687f281 · November 17, 2015, 9:00am

AFAIK the problem lies in the deferred evalution of the input nodes. The break statement currently stops before they are evaluated and not after that. Actually we would need two breakpoint-“slots” in blueprint (early/late), maybe visualized in a red dot in the title bar on the left (before evalution) or right (after evalution).

anonymous_user_deecf88c · March 14, 2017, 6:14pm

Unfortunately I’m still seeing a lot of issues with BP debugging in 4.12.5

Sachin