It’s from Visual Studio, it’s ■■■■.
It’s the intelisense garbage stored in the DB that is causing you problems.
They made this database that stores information there to rethink things, go thru them (Cycle over and over) on some objects of your code, when the compiler is not sure so there are no header errors for the compiler.
Intelisense is causing you this problems by making recursions on your code over and over, and the compilation time increases, it pulls from this database things to compare stuff for the header, and if it thinks it needs to check again then it will check again and again in a recursive patern.
Not only that but this data base stores information that go’s who know’s where, people were complaining that this DB killed their hard drive, ate all the free space. Now when you run your program again and make changes it will look inside this database and compare things.
This whole thing “they say” is for the headers not to make errors and compile the code in a correct manner, so it needs to make recursions, to double check. I doubt it, I think it’s to collect information from people who they think they are "WORTHY ) to see what they are up to.
So just compile manual from command prompt without visual studio running and see the time.
You can compile your UE project manually without VS either by command prompt or going into the editor and simply hitting compile, this should give you an idea to see if it’s intelisense problem.
I use either the editor inside unreal, or NotePad ++ and sometimes after the first compilation it takes 30 or more seconds or so if my resources are availible and I close down everything, browser and so on.
Go to your hard drive click and open task manager , then open up resource monitor in task manager, go to disk activity and while it’s compiling see what is writing to disk.
If you see something labled with DB that tops disk activity then that is your problem
You will see the processes in Disk activity and know where your problem is anyway, it shows what active files are writing to and reading to and if there are recursions.