OK, sadly, it seems the window causing this issue is not from the UnrealVS plugin but instead from something internal to VS2022 itself, none of my breakpoints were hitting upon the output activate calls when running my experimental instance. So I hope Microsoft fixes this annoying issue…
Hmm too bad.
I did notice a feedback page here, you might give that a try>
Your discovery helped me.
Thank you.
This is by far the most annoying thing I’ve seen in a long while. Holy cow.
1 Like