1:50:30x13pixels Q: The
RemedyBG bug seen earlier with the MoveEntity() breakpoint happened because a function breakpoint, currently, is only added to the first valid location found. When hot reloading, two DLLs are loaded in the process: handmade_game_temp.dll and 1_handmade_game_temp.dll. The breakpoint ends up getting added to the DLL that is still loaded but not executing any code. Looks like this is intentional in
Handmade Hero (Win32Unloaded doesn't call FreeLibrary). In any case, my apologies for the inconvenience
🗪
1:50:30x13pixels Q: The
RemedyBG bug seen earlier with the MoveEntity() breakpoint happened because a function breakpoint, currently, is only added to the first valid location found. When hot reloading, two DLLs are loaded in the process: handmade_game_temp.dll and 1_handmade_game_temp.dll. The breakpoint ends up getting added to the DLL that is still loaded but not executing any code. Looks like this is intentional in
Handmade Hero (Win32Unloaded doesn't call FreeLibrary). In any case, my apologies for the inconvenience
🗪
1:50:30x13pixels Q: The
RemedyBG bug seen earlier with the MoveEntity() breakpoint happened because a function breakpoint, currently, is only added to the first valid location found. When hot reloading, two DLLs are loaded in the process: handmade_game_temp.dll and 1_handmade_game_temp.dll. The breakpoint ends up getting added to the DLL that is still loaded but not executing any code. Looks like this is intentional in
Handmade Hero (Win32Unloaded doesn't call FreeLibrary). In any case, my apologies for the inconvenience
🗪