Breakpoints + Stepping Through Code! | How To DEBUG Your UE4 Game! | Unreal and C++ Tips, Part 2

Here is the second installment of the Unreal Engine 4 and C++ debugging series. In this episode, I go over stepping through code, attaching the Visual Studio debugger to our Unreal Engine process, and looking at values in code when a breakpoint is hit.

Debugging is insanely useful in programming and game development, as it helps speed up your workflow, fix bugs, and better understand how coding works behind the scenes!

Thanks for watching my video. Please let me know your thoughts and feel free to reach out to me!

OTHER PROGRAMMING VIDEOS:

JOIN MY CHANNEL:

FOLLOW MY OTHER CHANNELS:

A HUGE THANKS TO:

► Character Avatar: David Marshall (MalthaelsMight).
► Music: Mitchell Hartwell.

CONNECT WITH ME:

PLAY MY GAMES:

#DebugUE4 #Debug #Debugging #CodingPractices #MadeWithUnreal #MadeWithUE4 #Shawnthebro #STB

[blaaablooo]

the only true UE Debugging tutorial outhere

[scoreciastudios]

Hi Bro,
I'm back with your tutorials, everything you do to teach is great, and for that I thank you very much, but I would like to take the opportunity to ask you a couple of questions. The first is that I am having an error when launching the project for mobile, with TakeDamage and it does not allow me to build it to do some tests. The error message shows the following:
Error: C: / Users / Unreal Projects / FightingGame / Source / FightingGame / FightingGameCharacter.h (145, 8): error: 'AFightingGameCharacter :: TakeDamage' hides overloaded virtual function [-Werror, -Woverloaded-virtual] and I don't know how fix it. And the second thing is that I had to give up putting the inputs on the screen because after doing the fourth part of the input commands buffer tutorial I never opened the project again, it stayed on the loading screen at 75% and it happened to me in both versions that I am doing in UE4.24 and UE4.25 so I decided to discard it, instead I used the pluggin "Input buffer Basic" that is in the market place and in principle it seemed to work but it resulted in a new crash so I think the input on screen are not my thing :(
So I would like to know if there is another possible way to do TakeDamage? Well, it tells me that from Pawn it is not possible to override and in Character.cpp line 238 the variable currentDistanceApart = abs (***); you could use maybe currentDistanceApart = fabs (***); ? That eliminates the possible error for me.
Thanks again and sorry for going over so long.