Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Office Holiday

Epic Games' offices will be on holiday from June 22nd to July 7th. During this period support will be limited. Our offices will reopen on Monday, July 8th. 

VS 2015 Breakpoints just not working after 4.21

I have been working on my project in 4.17 for a while. However, recently I upgraded to 4.19, and then again to 4.21 soon after that.

For some reason, in both these versions VS debugging is just jerking me around in ways that it didn't in 4.17.

What I do is "Attach To Process" (ctrl + alt + P) to attach VS to the running UE4 editor. Then I hit a breakpoint. Sometimes the breakpoint doesn't work because, supposedly, the editor is not up to date with my latest build (even though that's patently wrong; I just compiled from VS and saw the hot reload working on the editor with the accompanying chirping sound). So I have to close my editor and open it again.

Then, when the editor is open and the breakpoint is hitting correctly, and I re-attached the process, the debugger simply doesn't stop where I placed the breakpoint. Even though I know the code is running where I hit the breakpoint.

In fact, what happens is that the debugging only works for some of my classes, but not all of them. I could, for example, put a breakpoint in a function in class A, where I know the debugging will work, and get to the debugging screen I desire. Then I can watch as it calls a function from class B. However, if I go to that exact function in class B and put a breakpoint there and run again, the debugger will simply skip that portion, but the code will run.

To get it to work in the specific class and function in which I want it to work, I have to close and open the editor again and re-attach it. Sometimes I have to do it multiple times. I have had to close and open and re-attach the editor 3 times for both the breakpoint to set, and for the debugger to actually stop at the breakpoint when the function runs.

I have no idea why this is happening. It never happened to me in 4.17. I was always able to debug seamlessly. I have had to do a lot of mental tracing through my code to figure out what's going on, because the debugger just won't let me actually trace the code. Does anybody know why this is happening in the newer versions?

Product Version: UE 4.21
more ▼

asked Dec 07 '18 at 08:22 PM in C++ Programming

avatar image

6 3 4

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

I have the same problem. Attaching VS while the Editor is already running doesn't work properly (as described above, breakpoints are not hit). Breakpoints are only hit when I start the editor from VS via run. Another symptom is that the diagnostic tools aren't working when I attach (showing nothing). This is happening on a new UE 4.21 project, it never happened on 4.18 or 4.15.

more ▼

answered Feb 15 '19 at 11:49 AM

avatar image


(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question