Closing Visual Studio and re-opening does sometimes make the problem disappear for a short time, but it certainly doesn't solve it.Here's what I tried for this iteration of the problem: This cost me a lot of lost time! I've been worked with Visual Studio for about 10 years, and this problem happens occasionally in every version. Closing the editor and compiling in VS even if you haven’t made any changes will show you on the Output window that hot reload binaries are being removed, too.After working for a few months, Intellisense suddenly stopped. Sometimes using Hot Reload doesn’t work even when the engine doesn’t crash as well, such as newly compiled binaries not being properly loaded over the old ones, so you’ll want to regularly compile without using Hot Reload anyway. If you change header files, close the editor and then compile from VS, then reopen the editor.

One more thing: Hot Reload works better for me on UE5 (5.0.2) than the new Live Coding. If both of those two things fail and so does refresh VS solution from within Unreal editor top menu bar, then delete the compiled Binaries and rebuild the project whilst Unreal is closed. With the RPC routines, you must compile before the rescan will solve the highlighting issues with it. Bear in mind, there’s security risks in doing this.įurthermore, compiling in VS2022 and then Right Click → Rescan → Rescan File helps a lot and often solves highlighting problems with things like RPC routines (e.g., UFUNCTIONs marked with Server, NetMulticast, Client - where the implementation has to have _Implementation at the end). Exclusions on VS processes and the folder for the project helps significantly. I’ve found that Windows Defender seems to significantly slow down VS syntax highlighting/IntelliSense.

Visual studio reset intellisense