microsoft / vscode-cpptools

Official repository for the Microsoft C/C++ extension for VS Code.
Other
5.53k stars 1.56k forks source link

"browse.VC.DB" causing me problems, constantly writes to disk (Unreal Engine project) #7849

Closed pepsi112-dude closed 3 years ago

pepsi112-dude commented 3 years ago

Bug type: Language Service

Describe the bug

Steps to reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Code sample and logs

Screenshots

Additional context

I have been redirected here, they told me it is a extension problem and to ask here ?

Basicly "browse.VC.DB" keeps on writing to disk when my project is opened in VS Code. I setup VCcode with Unreal Engine on Win7. Unreal engine generates code project inside my VScode application, so I thought to find a way to avoid Visual Studio and use VScode.

All works fine, the project tree is loaded in VS code except that this "browse.VC.DB" file keeps on getting bigger and keeps on getting written.

It does not stop at all, it can go for hours, it is continues non stop writting and reading to this file, the hard drive go's off, you can hear it, and the file just gets bigger.

I went under my workspace for unreal, and there is only one unreal project that I created for this purpose, nothing else, this project has about 7 megs. There is nothing else there. except this project with it's main folder having 7megs. Unreal Engine is freshly installed , clean installation, I just installed VS code with it's dependencies for Microsoft Build Tools.

What is this "browse.VC.DB" ? it's part of itelisense ? Why does it constantly write to disk, it,s annoying , I can see it under Resource Monitor, you don't have to touch anything and it just continues to write at around 1.000.000 bites per second without me doing anything, if I keep it like this I can also damage the hdd if the hard drive constantly reads and writes all the time. I left it for 2 hours to see if it stops, it does not, "AMAZING" what does it write and read from there.

Also 1 GB for 7 meg project ? what can it possibly store inside there for 7 megs making it above 1 GB.

Can I get rid of it, disable it ? make it less noisy, limit it, I don't know, best is to disable it if I can get by it. Is it part of C++ dependency ? I use C++ for writing projects for Unreal Engine 4.

How can I get past this, Visual Studio does not do this, but I don't want Visual Studio because it costs HDD space, it's slow and I have limited PC resources, and I prefer something faster and litter.

Best if I can disable it, it's a DB storing what, project files ? what for. I'll be glad to disable it I don't need cache, I just save to disk when I'm done without this "Drama"

michelleangela commented 3 years ago

@pepsi112-dude, the file "browse.VC.DB" is a database file that stores symbols for browsing features such as "go to definition".

When opening a folder, the C++ extension will tag parse files for that folder. To see which files are parsed, enable the C++ logging (see instructions at https://code.visualstudio.com/docs/cpp/enable-logging-cpp#_enable-logging-for-the-language-server). To configure which files/folders the tag parser will parse, set these browser properties.

pepsi112-dude commented 3 years ago

I solved my problems by running the Unreal Engine as Administrator. It no longer does this, I think it was a permission problem and it retried to write inside the file db something to define it over and over again, retry. I don't know.

However I still am not found of VScode, since now other elements are popping up on my disk usage windows sdk10 , files from Vscode, files from my Unreal Engine project and so on, they are fluctuating on and off switching on my disk usage while I do nothing, overall my disk usage is constant, now that shuts off then that turns on and so forth as long as the project is loaded but I do nothing, if I close the project all this stops.

This leads me to believe that VCcode is live all the time and that it should not do this, it should come alive when you compile and that is it. Other litter Ides do not do this, you don't see them work while they do nothing at all while you don't do anything with the loaded project inside the window. Not VCcode.

VScode was an alternative to Visual Studio to offer something litter that has "no fuss" once again microsoft dissapoints by giving me "CIRCUS MODE" on my disk drive, not even Visual Studio does this and that is really heavy , and you think you got the liter version and all the sudden your hard drive starts fusssing around for nothing just to annoy you, you can't even work with the noise from the hard drive.

Worst for me for some reason Unreal Engine decided to play Microsoft all the way and you cannot compile with other Ides Unreal engine. It's like a chose windows over linux, but the rest from Microsoft as expirience I rather not say.

michelleangela commented 3 years ago

other elements are popping up on my disk usage windows sdk10 , files from Vscode, files from my Unreal Engine project and so on, they are fluctuating on and off switching on my disk usage while I do nothing, overall my disk usage is constant, now that shuts off then that turns on and so forth as long as the project is loaded but I do nothing, if I close the project all this stops.

Are these other disk usage caused by processes from the C++ extension or from VS Code client without the C++ extension?

Could you provide logs from the C++ extension's language server by following instructions at https://code.visualstudio.com/docs/cpp/enable-logging-cpp#_enable-logging-for-the-language-server? This will help determine what process and other work that is being done by the C++ extension that's causing disk usage.

For performance issues, please provide performance analysis logs to help us troubleshoot the issue. https://github.com/microsoft/vscode-cpptools/wiki/Troubleshooting-Performance-Issues#windows

pepsi112-dude commented 3 years ago

They are project related and windows related, windows sdk files, c++ tool files and project files from the loaded project, all bouncing around. This is when I only have my project open, but I'm not doing anything with it, it should not do this. I also find it strange that I have to run Unreal Engine as administrator to get the DB file not to write to it's self all the time. I will look into the logs later as you said.

pepsi112-dude commented 3 years ago

This is no longer in vscode latest vers." Open the Command Palette and choose Preferences: Workspace settings." I get preferences options but not with workspace. There must be some other order and I can't find the log option, I got the latest version of Vscode. I looked around but could not find the log option

The second log involves me installing visual studio and my hard drive is already full almost.

pepsi112-dude commented 3 years ago

I manage to find the log option under the preferences> user options (now). I will post a part of it since it's never ending log, ongoing, it does not stop. Basicly it prases the whole unreal engine, loads all the things from it in stead of just loading the project files and waiting for my call to do something.

I think this has to do with running in admin mode, go back to running it in user mode and I got the other problem with the DB file, (just a hunch what gets written in it is this never ending stuff outputed by the log but in the db file)
It's suppose to load the project and that is it, not do this, not load the whole engine inside Vscode.

Well I did my best to find out how to solve this, any answers ? Also worth mentioning is the fact that when trying to add a new c++ class from the UEngine it tells me that it cannot compile but that it added the C++ class, this after I changed the option inside the editor from Visual Studio to Visual Studio Code. So it has to do with VS code.

After trying to close the editor then reload the editor and reload the project for the editor the Editor says the module is not compiled and tries to compile says it's "made with another version" and says then that the project cannot be loaded and that compilation failed.

All this when I try to work with VScode.

When running the log I get recursive (recursive = repetative ?) meaning it loads the whole thing then repeats it's self, I left it for a few hours and it does not stop.

Part of the log from VScode log C++ output C_Cpp: Logging Level: File exclude: /.vscode File exclude: /.git File exclude: /.svn File exclude: /.hg File exclude: /CVS File exclude: /.DS_Store Search exclude: /node_modules Search exclude: /bower_components Search exclude: */.code-search IntelliSense Engine = Default. Enhanced Colorization is enabled. Error squiggles are enabled if all header dependencies are resolved. File discovery was aborted Discovering files: 23284 file(s) processed Done discovering files. Autocomplete is enabled. File exclude: /.vscode File exclude: /.git File exclude: /.svn File exclude: /.hg File exclude: /CVS File exclude: /.DS_Store Search exclude: /node_modules Search exclude: /bower_components Search exclude: */.code-search Populate include completion cache. Discovering files... Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/BUILDTOOLS/VC/TOOLS/MSVC/14.29.30037/ATLMFC/INCLUDE Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/BUILDTOOLS/VC/TOOLS/MSVC/14.29.30037/INCLUDE Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/CPPWINRT/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/SHARED/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/UCRT/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/UM/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/WINRT/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AIMODULE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ADDCONTENTDIALOG/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ANIMATIONCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ASSETREGISTRY/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ASSETTOOLS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOEXTENSIONS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOMIXER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOPLATFORMCONFIGURATION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUTOMATIONCONTROLLER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/BLUEPRINTGRAPH/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CHAOS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CLASSVIEWER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CLOTHINGSYSTEMRUNTIMEINTERFACE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CONTENTBROWSER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CONTENTBROWSERDATA/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/COREUOBJECT/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/DETAILCUSTOMIZATIONS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/DEVELOPERSETTINGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/EDITORSTYLE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/EDITORSUBSYSTEM/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ENGINE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ENGINEMESSAGES/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ENGINESETTINGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/FUNCTIONALTESTING/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GAMEPLAYDEBUGGER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GAMEPLAYTAGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GAMEPLAYTASKS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GRAPHEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/HEADMOUNTEDDISPLAY/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/IMAGEWRAPPER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/INPUTCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/INTERACTIVETOOLSFRAMEWORK/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/INTROTUTORIALS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/KISMET/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/LANDSCAPE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/LEVELEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/LOCALIZATION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MATERIALSHADERQUALITYSETTINGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MESHDESCRIPTION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MOVIESCENE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MOVIESCENETRACKS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/NAVIGATIONSYSTEM/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/NETCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PACKETHANDLER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PHYSICSCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PROPERTYACCESS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PROPERTYEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PROPERTYPATH/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/RENDERER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/SLATE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/SLATECORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/SOURCECONTROL/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/STATICMESHDESCRIPTION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/STRUCTVIEWER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/TIMEMANAGEMENT/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/TOOLMENUS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/TOOLMENUSEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/UMG/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/UNREALED/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/UNREALEDMESSAGES/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/VREDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/SOURCE/ Processing folder (recursive): C:/USERS/DAN~/DOCUMENTS/UNREAL PROJECTS/MYPROJECT45/INTERMEDIATE/BUILD/WIN64/MYPROJECT45EDITOR/DEVELOPMENT/ENGINE/ Processing folder (recursive): C:/USERS/DAN~/DOCUMENTS/UNREAL PROJECTS/MYPROJECT45/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/DEVELOPMENT/MYPROJECT45/ Processing folder (recursive): C:/USERS/DAN~/DOCUMENTS/UNREAL PROJECTS/MYPROJECT45/SOURCE/ Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/BUILDTOOLS/VC/TOOLS/MSVC/14.29.30037/ATLMFC/INCLUDE Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/BUILDTOOLS/VC/TOOLS/MSVC/14.29.30037/INCLUDE Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/CPPWINRT/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/SHARED/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/UCRT/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/UM/ Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.19041.0/WINRT/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AIMODULE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ADDCONTENTDIALOG/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ANIMATIONCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ASSETREGISTRY/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ASSETTOOLS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOEXTENSIONS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOMIXER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUDIOPLATFORMCONFIGURATION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/AUTOMATIONCONTROLLER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/BLUEPRINTGRAPH/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CHAOS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CLASSVIEWER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CLOTHINGSYSTEMRUNTIMEINTERFACE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CONTENTBROWSER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/CONTENTBROWSERDATA/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/COREUOBJECT/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/DETAILCUSTOMIZATIONS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/DEVELOPERSETTINGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/EDITORSTYLE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/EDITORSUBSYSTEM/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ENGINE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ENGINEMESSAGES/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/ENGINESETTINGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/FUNCTIONALTESTING/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GAMEPLAYDEBUGGER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GAMEPLAYTAGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GAMEPLAYTASKS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/GRAPHEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/HEADMOUNTEDDISPLAY/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/IMAGEWRAPPER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/INPUTCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/INTERACTIVETOOLSFRAMEWORK/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/INTROTUTORIALS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/KISMET/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/LANDSCAPE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/LEVELEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/LOCALIZATION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MATERIALSHADERQUALITYSETTINGS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MESHDESCRIPTION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MOVIESCENE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/MOVIESCENETRACKS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/NAVIGATIONSYSTEM/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/NETCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PACKETHANDLER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PHYSICSCORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PROPERTYACCESS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PROPERTYEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/PROPERTYPATH/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/RENDERER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/SLATE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/SLATECORE/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/SOURCECONTROL/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/STATICMESHDESCRIPTION/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/STRUCTVIEWER/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/TIMEMANAGEMENT/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/TOOLMENUS/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/TOOLMENUSEDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/UMG/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/UNREALED/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/UNREALEDMESSAGES/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/INC/VREDITOR/ Processing folder (recursive): C:/PROGRAM FILES/EPIC GAMES/UE_4.26/ENGINE/SOURCE/ Processing folder (recursive): C:/USERS/DAN~/DOCUMENTS/UNREAL PROJECTS/MYPROJECT/INTERMEDIATE/BUILD/WIN64/MYPROJECTEDITOR/DEVELOPMENT/ENGINE/ Processing folder (recursive): C:/USERS/DAN~/DOCUMENTS/UNREAL PROJECTS/MYPROJECT/INTERMEDIATE/BUILD/WIN64/UE4EDITOR/DEVELOPMENT/MYPROJECT/ Processing folder (recursive): C:/USERS/DAN~/DOCUMENTS/UNREAL PROJECTS/MYPROJECT/SOURCE/ Discovering files: 160518 file(s) processed 0 file(s) removed from database Done discovering files. Parsing remaining files... tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\HIERARCHICALLODOUTLINER\PRIVATE\LODLEVELITEM.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\LIBCURL\CURL-7.55.1\INCLUDE\ANDROID\X64\CURL\STDCHEADERS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\TEST-L\NEST74.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN64\VS2015\MEDIA\BASE\RTPDATAENGINE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\UNREALED\ACTORGROUPINGUTILS.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\UNREALED\CLASSES\ANIMATION\DEBUGSKELMESHCOMPONENT.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\LIBOPUS\OPUS-1.1\CELT\MODES.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\MAC\THIRD_PARTY\PROTOBUF\OBJECTIVEC\GPBROOTOBJECT.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\TIMEMANAGEMENT\ITIMEDDATAINPUT.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.1.1\INCLUDE\MAC\OPENSSL\X509V3.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\THIRD_PARTY\LIBJPEG\JINCLUDE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\VIEWMODELS\TRACKHEADER.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\TEST-L\NEST63.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\MODULES\AUDIO_PROCESSING\TEST\ECHO_CANCELLER_TEST_TOOLS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\GRAPHEDITOR\PRIVATE\KISMETNODES\SGRAPHNODESPAWNACTORFROMCLASS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\LLVM\8\INCLUDE\LLVM\TRANSFORMS\SCALAR\SIMPLELOOPUNSWITCH.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PHYSX3\APEX_1.4\MODULE\CLOTHING\EMBEDDED\LOWLEVELCLOTH\SRC\ALLOCATOR.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN64\VS2015\EXAMPLES\OBJC\APPRTCMOBILE\ARDEXTERNALSAMPLECAPTURER.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\UNREALED\BLENDSPACETHUMBNAILRENDERER.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\VS2013_FRIENDLY\INCLUDE\WIN64\VS2015\WEBRTC\LIBJINGLE\XMPP\MUCROOMLOOKUPTASK.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\LIBOPUS\OPUS-1.0.3\TESTS\TEST_OPUS_COMMON.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\SSESSIONINFOWINDOW.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\MODULES\AUDIO_CODING\CODECS\ISAC\MAIN\SOURCE\LPC_SHAPE_SWB16_TABLES.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\UNREALED\CLASSES\FACTORIES\FBXSCENEIMPORTOPTIONSSTATICMESH.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\THIRD_PARTY\LIBVPX\SOURCE\LIBVPX\RATE_HIST.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENEXR\OPENEXR-2.3.0\ILMBASE\IEX\IEXFORWARD.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\SSTARTPAGEWINDOW.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\WORLDBROWSER\PRIVATE\STREAMINGLEVELS\STREAMINGLEVELCUSTOMIZATION.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.1.1\INCLUDE\WIN32\VS2015\OPENSSL\BUFFERERR.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\SSTATSTABLECELL.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PHYSX3\PHYSX_3.4\INCLUDE\VEHICLE\PXVEHICLEUTILSETUP.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\GRAPHEDITOR\PRIVATE\KISMETNODES\SGRAPHNODEK2SEQUENCE.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PERFORCE\P4API-2018.1\INCLUDE\WIN64\VS2015\P4\ERROR.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\MAC\THIRD_PARTY\OPUS\SRC\CELT\PITCH.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\DATATABLEEDITOR\PRIVATE\SCOMPOSITEROWEDITOR.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\CPP-TEST\TEST-L\NEST70.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN64\VS2015\API\ORTC\RTPTRANSPORTINTERFACE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\STIMERSVIEW.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1_0_2H\INCLUDE\WIN32\VS2015\OPENSSL\RSA.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\COMMON_VIDEO\VIDEO_RENDER_FRAMES.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\DETAILCUSTOMIZATIONS\PRIVATE\MOVIEPLAYERSETTINGSDETAILS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\CPP-TEST\TEST-L\NEST8.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\CALL\TEST\MOCK_AUDIO_SEND_STREAM.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\STIMERSVIEWTOOLTIP.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PYTHON3\WIN64\INCLUDE\PYCONFIG.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN64\VS2015\MODULES\AUDIO_CODING\NETEQ\PACKET.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\ENGINE\MATERIALEXPRESSIONSMOOTHSTEP.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\UNREALED\PRIVATE\THUMBNAILRENDERING\ANIMSEQUENCETHUMBNAILRENDERER.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1_0_1S\INCLUDE\ANDROID\OPENSSL\CONF_API.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\THIRD_PARTY\LIBVPX\SOURCE\LIBVPX\THIRD_PARTY\LIBYUV\INCLUDE\LIBYUV\CONVERT_ARGB.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\DETAILCUSTOMIZATIONS\PRIVATE\MOVIESCENESEQUENCELOOPCOUNTCUSTOMIZATION.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\CPP-TEST\TEST-L\NEST78.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\STIMERTREEVIEW.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.1.1\INCLUDE\IOS\OPENSSL\ASN1ERR.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\GRAPHEDITOR\PRIVATE\KISMETPINS\SGRAPHPINBOOL.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\RUNTIME\EXPERIMENTAL\FIELDSYSTEM\SOURCE\FIELDSYSTEMENGINE\PRIVATE\FIELD\FIELDSYSTEMACTOR.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENEXR\OPENEXR-2.3.0\ILMBASE\IMATH\IMATHEULER.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\STEAMWORKS\STEAMV146\SDK\PUBLIC\STEAM\ISTEAMNETWORKINGSOCKETS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\STIMINGPROFILERTOOLBAR.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.12643\INCLUDE\WIN64\VS2015\WEBRTC\BASE\SSLROOTS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\BLUEPRINTGRAPH\PRIVATE\K2NODE_MATHEXPRESSION.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.0.2G\INCLUDE\WIN32\VS2012\OPENSSL\OBJECTS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\DETAILCUSTOMIZATIONS\PRIVATE\AMBIENTSOUNDDETAILS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\RPCLIB\SOURCE\INCLUDE\RPC\MSGPACK\ADAPTOR\VECTOR_BOOL.HPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACEINSIGHTS\PRIVATE\INSIGHTS\WIDGETS\STIMINGVIEWTRACKLIST.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PHYSX3\PHYSX_3.4\INCLUDE\COMMON\PXBASE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\ANDROID\ANDROIDPLATFORMEDITOR\PRIVATE\ANDROIDTARGETSETTINGSCUSTOMIZATION.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\TEST-T\NEST14.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\DETAILCUSTOMIZATIONS\PRIVATE\OBJECTDETAILS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.0.2G\INCLUDE\WIN32\VS2015\OPENSSL\X509V3.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\MAC\THIRD_PARTY\OPUS\SRC\SILK\ARM\LPC_INV_PRED_GAIN_ARM.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\COMPONENTVISUALIZERS\PUBLIC\RADIALFORCECOMPONENTVISUALIZER.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\MODULESERVICE.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\LLVM\8\INCLUDE\LLVM\IR\DEBUGINFOMETADATA.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\RUNTIME\ENGINE\PRIVATE\COMPONENTS\STATICMESHCOMPONENT.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\CPP-TEST\TEST-T\UNBAL4.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.12643\INCLUDE\MAC\TALK\APP\WEBRTC\OBJC\PUBLIC\RTCDATACHANNEL.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\ANALYZERS\ALLOCATIONSANALYSIS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\RUNTIME\LANDSCAPE\PRIVATE\MATERIALS\MATERIALEXPRESSIONLANDSCAPELAYERCOORDS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.12643\INCLUDE\WIN64\VS2015\WEBRTC\SDK\OBJC\FRAMEWORK\CLASSES\RTCPEERCONNECTIONFACTORY+PRIVATE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\DETAILCUSTOMIZATIONS\PRIVATE\SKELETALMESHREDUCTIONSETTINGSDETAILS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\TEST-T\UNBAL2.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\MODULES\CONGESTION_CONTROLLER\GOOG_CC\DELAY_INCREASE_DETECTOR_INTERFACE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\GRAPHEDITOR\PUBLIC\SNODEPANEL.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PHYSX3\APEX_1.4\MODULE\CLOTHING\INCLUDE\AUTOGEN\CLOTHINGACTORPARAM.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN64\VS2015\LOGGING\RTC_EVENT_LOG\EVENTS\RTC_EVENT_ALR_STATE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\UNREALED\EDITORBRUSHBUILDER.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.1.1\INCLUDE\WIN64\VS2015\OPENSSL\OBJECTS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\MAC\THIRD_PARTY\OPUS\SRC\SILK\FIXED\MIPS\NOISE_SHAPE_ANALYSIS_FIX_MIPSR1.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\UNREALED\CLASSES\ACTORFACTORIES\ACTORFACTORYCHARACTER.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\LIBOPUS\OPUS-1.1\SILK\CONTROL.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PYTHON\MAC\INCLUDE\CLASSOBJECT.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN64\VS2015\BASE\WIN\SCOPED_CO_MEM.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\ANALYZERS\COUNTERSTRACEANALYSIS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PERFORCE\P4API-2014.1\INCLUDE\P4\DEBUG.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\CONFIGEDITOR\PRIVATE\SCONFIGEDITOR.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENEXR\OPENEXR-2.3.0\ILMBASE\IMATHTEST\TESTQUATSETROTATION.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\ANALYZERS\CPUPROFILERTRACEANALYSIS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\CPP-TEST\TEST-T\UNBAL2.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\ANALYZERS\CSVPROFILERTRACEANALYSIS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\ICU\ICU4C-64_1\SOURCE\SAMPLES\LAYOUT\GDIFONTMAP.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\ENGINE\INTERPTRACKINSTFLOATANIMBPPARAM.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\NVTEXTURETOOLS\NVTEXTURETOOLS-2.0.6\SRC\SRC\NVMATH\RANDOM.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\ANALYZERS\MISCTRACEANALYSIS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PERFORCE\P4API-2014.1\INCLUDE\P4\NTMANGLE.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\ENGINE\KILLZVOLUME.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\TEST-L\NEST69.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\DETAILCUSTOMIZATIONS\PRIVATE\TEXTCUSTOMIZATION.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\PHYSX3\APEX_1.4\MODULE\CLOTHING_LEGACY\INCLUDE\CONVERSIONCLOTHINGMATERIALLIBRARYPARAMETERS_0P9_0P10.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\LANDSCAPE\LANDSCAPEMESHPROXYACTOR.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENEXR\OPENEXR-2.3.0\CONTRIB\DTEXTOEXR\PXDEEPOUTROW.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\COMMON\UTILS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.12643\INCLUDE\MAC\WEBRTC\MODULES\VIDEO_CAPTURE\VIDEO_CAPTURE_INTERNAL.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\UNREALED\CLASSES\ACTORFACTORIES\ACTORFACTORYVOLUME.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\MODEL\ALLOCATIONSPROVIDER.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1_0_2H\INCLUDE\ANDROID\X64\OPENSSL\TXT_DB.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\WIN32\VS2015\MODULES\AUDIO_DEVICE\ANDROID\AAUDIO_RECORDER.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\UNREALED\CLASSES\FACTORIES\DATATABLEFACTORY.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\RUNTIME\ENGINE\PRIVATE\GAMEFRAMEWORK\FORCEFEEDBACKEFFECT.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\MCPP\MCPP-2.7.2\TEST-L\IFDEF255.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\DEVELOPER\TRACESERVICES\PRIVATE\MODEL\COUNTERS.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.1.1\INCLUDE\IOS\OPENSSL\X509ERR.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\WEBRTC\REV.24472\INCLUDE\MAC\THIRD_PARTY\ABSEIL-CPP\ABSL\STRINGS\INTERNAL\BITS.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\BLUTILITY\PRIVATE\EDITORUTILITYBLUEPRINT.CPP tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\INTERMEDIATE\BUILD\WIN64\UE4EDITOR\INC\ENGINE\LEVELSTREAMINGVOLUME.GENERATED.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\EDITOR\PROPERTYEDITOR\PRIVATE\PRESENTATION\PROPERTYTABLE\PROPERTYTABLEROW.H tag parsing file: C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\OPENSSL\1.0.2G\INCLUDE\WIN64\VS2012\OPENSSL\RIPEMD.H.

Edit by me:

I just spent 3 days trying to go around Visual Studio, with no results to compile without it being installed.

Visual Studio is a pain, Vscode is nice fast, modern, I like it, too bad it does not work for me.

pepsi112-dude commented 3 years ago

Why does it parse files ? It loads them instantly under the tree project then starts parasing them ? this go's on and on, repeating. I think I'm getting closer to the problem, it's the build tools from microsoft, I did not install visual studio just the build tools, when trying to compile inside the game engine it says in the log [1/7] ERROR: Unable to create child process [2/7] Default.rc2.

So if I install the whole package with Visual Studio it does not do this, so no Visual Studio no VScode and no compability, you can have the msvc compiler for nothing because as long as it's not patched with special magic from Visual Studio the Game Engine will complain and VScode will complain saying "it's another version from another planet" because everything needs to go thru Visual Studio format like.

It's why everyone "likes Microsoft so much" that they try to avoid it. I see no other reason, Visual Studio worked fine except it is slow and takes a lot of disk space.

Check this out, this log from the Game Engine error log, (I don't have visual studio installed) I set the engine to Vscode, it was set on VStudio.

Log file: Using Visual Studio 2019 14.29.30037 toolchain (C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30037) and Windows 10.0.19041.0 SDK (C:\Program Files (x86)\Windows Kits\10). Building 7 actions with 2 processes... [1/7] ERROR: Unable to create child process [2/7] Default.rc2 CompilerResultsLog: New page: Compilation - Jul 21, 2021, 1:32:58 PM CompilerResultsLog: Creating makefile for MyProject3Editor (no existing makefile) CompilerResultsLog: Parsing headers for MyProject3Editor CompilerResultsLog: Running UnrealHeaderTool "C:\Users\Dan~\Documents\Unreal Projects\MyProject3\MyProject3.uproject" "C:\Users\Dan~\Documents\Unreal Projects\MyProject3\Intermediate\Build\Win64\MyProject3Editor\Development\MyProject3Editor.uhtmanifest" -LogCmds="loginit warning, logexit warning, logdatabase error" -Unattended -WarningsAsErrors -abslog="C: \Users\Dan~\AppData\Local\UnrealBuildTool\Log_UHT.txt" -installed CompilerResultsLog: Reflection code generated for MyProject3Editor in 50.685407 seconds CompilerResultsLog: Building MyProject3Editor... CompilerResultsLog: Using Visual Studio 2019 14.29.30037 toolchain (C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30037) and Windows 10.0.19041.0 SDK (C:\Program Files (x86)\Windows Kits\10). CompilerResultsLog: Building 7 actions with 2 processes... CompilerResultsLog: [1/7] ERROR: Unable to create child process CompilerResultsLog: [2/7] Default.rc2 LogMainFrame: MainFrame: Module compiling took 128.379 seconds LogSlate: Window 'Message' being destroyed Message dialog closed, result: Yes, title: Message, text: Successfully added class 'MyClassasd', however you must recompile the 'MyProject3' module before it will appear in the Content Browser. Failed to compile newly created game module. Would you like to open the Output Log to see more details? LogSlate: Window 'Add C++ Class' being destroyed LogSlate: Took 0.023471 seconds to synchronously load lazily loaded font '../../../Engine/Content/Slate/Fonts/DroidSansMono.ttf' (77K) LogAudioMixer: Display: Audio Buffer Underrun (starvation) detected.

=======================================================================

It is specific stranded on visual studio yet I changed the option to VS code, so no matter what the format that runs things thru is visual studio: CompilerResultsLog: Using Visual Studio 2019 14.29.30037 toolchain (C:\Program Files (x86)\Microsoft Visual Studio\2019.

I get this error only if I switch to Vscode mode inside the Editor, If I leave it on VS 2019 no error. I switched to Vscode to try to create a new C++ class and compile it and then load to Vscode to further work in it and compile there as well.

Who o why do people say "use VCcode" use it with Unreal Engine, and then there are others who say, it just does not work. I don't have a 500 GB hard drive. The build tools with all their dependencies with the sdk cost me 70gb already. Basiclly this log file is telling me to install "Visual Studio" so maybe Vscode may work with Unreal afterwards.

How come Microsoft, why do you do this ? (sense of humor).

So Vscode does not understand how to handle and process the C++ code coming from unreal engine without visual studio installed, nor the game engine, giving errors trying to use just the build tools ? without visual studio. Microsoft said Vscode is an alternative to Visual Studio that is heavy weight IDE. If it's so, why would I need to install Visual Studio since I'm trying to avoid it.

VScode should have such implementations I think where it sees visual studio formating and works with it without visual studio installed, just my opinion.

Tho VS2019 is not installed when you get the build tools it creates a VS2019 folder, this from the installer where you get all the C++ dependenciers and the sdk. So the compiler is there but VScode can't understand the format comming from unreal without vs2019 installed ?

Path from my setup: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30037\bin\Hostx64\x64\cl.exe

pepsi112-dude commented 3 years ago

other elements are popping up on my disk usage windows sdk10 , files from Vscode, files from my Unreal Engine project and so on, they are fluctuating on and off switching on my disk usage while I do nothing, overall my disk usage is constant, now that shuts off then that turns on and so forth as long as the project is loaded but I do nothing, if I close the project all this stops.

Are these other disk usage caused by processes from the C++ extension or from VS Code client without the C++ extension?

Could you provide logs from the C++ extension's language server by following instructions at https://code.visualstudio.com/docs/cpp/enable-logging-cpp#_enable-logging-for-the-language-server? This will help determine what process and other work that is being done by the C++ extension that's causing disk usage.

For performance issues, please provide performance analysis logs to help us troubleshoot the issue. https://github.com/microsoft/vscode-cpptools/wiki/Troubleshooting-Performance-Issues#windows

I also posted here, similar problem regarding MS build tools. https://forums.unrealengine.com/t/building-with-unreal-build-tools-my-project-i-get-an-error/241518/3

Anyone can help me use VCcode ? any ideas. Greatly appreciated.

michelleangela commented 3 years ago

@pepsi112-dude

Are you using the Unreal Editor to generate/export the VS Code project? Could you clarify how you setup the project so that we can see if this a concern with C++ extension or a concern with an third party editor?

Could you clarify what you mean by "running in admin mode"?

Depending on how a project is configured, it could affect how the C++ extension will process a project for IntelliSense features to work. For setting up large/complex projects with specific configurations, like Unreal Engine, I suggest to consult the Unreal Engine forums.

Some clarifications:

  1. Visual Studio is a full IDE, which provides C++ IntelliSense, MSVC compiler, and debugging out of the box when the C++ development tools are installed with it.
  2. VS Code without extensions or addons is a code editor with Typescript and JavaScript language support, debugging, and compiling built-in.
  3. The C++ extension for VS Code provides C++ IntelliSense features for coding editing and it also provides debugging. It does not provide a compiler, which is why a compiler has to be installed if a user wants to use a compiler for a project. The C++ extension also uses an installed compiler to get the system header files from the compiler's relative install path, and this information is used for IntelliSense features.
  4. In order for a user to compile a project with VS Code, user has to configure the tasks.json file with an installed compiler and specify compiler arguments and other compiling instructions.

About the C++ extension's tag parsing files:

About compiling the project: The following build issue is not related to the C++ extension:

CompilerResultsLog: Using Visual Studio 2019 14.29.30037 toolchain (C:\Program Files (x86)\Microsoft Visual Studio\2019.

I get this error only if I switch to Vscode mode inside the Editor, If I leave it on VS 2019 no error. I switched to Vscode to try to create a new C++ class and compile it and then load to Vscode to further work in it and compile there as well.

As stated above, the C++ extension does not provide a compiler and does not automatically configure compiling settings. There are simple compiling template that can be generated, but specific compiler arguments will not be set as there is no "project" concept on VS Code for the extension to know what information to provide to a compiler.

pepsi112-dude commented 3 years ago

Yes I'm using unreal to generate VCcode project inside VCcode. Problem when Unreal Editor opens up visual code, when I generate a new C++ class in unreal Editor it will open up VCcode with the project in it along with the class I created inside the project, but it starts fluctuating (VCcode that is) as showed in the log file.

1 Seems the latest Unreal version has some problems, so to make sure I reinstalled an older version that seems to do better and compiles now my C++ code without VISUAL STUDIO. (inside unreal engine with just the build tools) It's not the Unreal installation that has problems.

2 Unreal Engine has an option to set the Editor to load into VCcode instead of opening and loading the project in Visual Studio. It adds some files from Vscode into the project once you set it to Vscode with it's own folder then loads the whole project into Vscode, opens Vscode, it does just that.

Why is VScode recursive ? in reading the files ? Now I installed another version of unreal that is more stable and makes no problems when you run it internally, it compiles code with just the build tools now, no Visual Studio needed .

I now loaded the project into vscode from unreal and Browse.VC.DB is at it again just reading and writting (FOREVER). Browse.VC.DB is part of extension ? loaded by the CPP tools ?

You said: As stated above, the C++ extension does not provide a compiler and does not automatically configure compiling settings. There are simple compiling template that can be generated, but specific compiler arguments will not be set as there is no "project" concept on VS Code for the extension to know what information to provide to a compiler.

Well...I say: That is the problem , I'm not compiling nor doing anything and the extension is prasing files over and over and writting with CPP tools inside that data base non stop maybe without me compiling nor doing anything with the project ? I just load the project from Unreal into Vccode and it starts with the noise. I don't compile I don't do anything, as you can see, it's there with two files "Constantly writing on my disk"

I'm not making anything up, and not the first to complain that this file grows in time without reason, others have posted before me. It does not know how to handle code and becomes recursive , and people around are saying Intelisense is making us problems. I just not expect it to be active all the time like a "VULCANO" to store so much stuff on repetition mode. There it is with two files, they are prime files for making noise on my PC all the time.

The read and write bites per second stays all the time in around the range of 1.00.000 bites per second, this is ever going, on going, no stopping. diskmonitor

How is it unreal, this file is not part of unreal tools nor unreal engine.

It's clear that it's the extension doing this and that the extension does not handle the C++ code well coming from unreal. If you search GitHub this Browse.VC.DB is nothing but problems, everyone complaining about it, how it grows it sizes to 10gb and users are complaining (why 10 gb, I herd like 40 GB 50 Gb, why ? because it writes non stop) maybe because it's recursive ? writing and over-writing without any sense at all, just constantly re-writing data.

It's not my unreal installation that is the problem, it compiles and creates c++ code in a stable manner inside of it, when we toss it on the pipeline on the VCcode pipeline trouble starts. BrowseVC.DB is not part of Unreal, so Unreal is not to blame.

So: Unreal just unloads the C++ project into VCcode and says "Deal with it" It's not Unreal but VCcode that is the problem.

I think I will close this, since there is no solution.

pepsi112-dude commented 3 years ago

I can also see it's loading some files from the game engine "to repeat things" it has to do with some headers.

Fore example: The repetition/for.hpp header defines a generalized horizontal repetition construct. Usage

include <boost/preprocessor/repetition/for.hpp>

It just repeats things maybe because it does not read the header and other files in a proper manner, repeating without a limit, reading header files maybe in a wrong way.

This poster here: https://github.com/microsoft/vscode-cpptools/issues/150 Has the same problem as me, with the same file that he says is huge and it's not related to unreal, he says it's "repeating it's self"

From the posts of this thread: "except my hpp files. also I checked how many times a file is repeated by running: "select count(*) from code_items where name="iomanip";": 209

https://github.com/microsoft/vscode-cpptools/issues/3470 One poster: I had situations where .browse.VC.db files where ~10GB (yes, lot's of source files to be indexed). I'm fine with this, but there should be some check in place that prevents those files from occupying all available disk space. How about going into some degraded-service behavior if less than 0.5GB (or similar) is available?

https://github.com/microsoft/vscode-cpptools/issues/1114 C++ prasing never stops thread, and it has to do wit Browse.VC.db

Intelisense is an extension and Browse.Vb.db is part of it if I'm not mistaken.

It may be that it reads the header in a wrong way, the header may tell it to repeat to verify things maybe a few times, sometimes it needs to check, so this extension interprets it as "repeat on forever" + database growth.

It's clearly this extension, so many people having "the same issue" and none of them use Unreal Engine, they have other stuff with other headers that are similar to what I have.

VCcode is fun to code in, looks nice, has extension install on the fly, lite weight, fast, too bad it does this. I really liked it why I went this far here.

If you want me to close the thread I will, or leave it open maybe others will join and know more, participate and maybe find an answer to overall problems, or maybe give some advice, I don't know.

michelleangela commented 3 years ago

Thank you for the additional information.

It looks like some header file could be causing a crash to the extension's cpptools.exe process, which could result in tag parsing to repeat. To help confirm this we will need to see which file is causing the crash if there is a crash. If we identify the file that could be causing the crash, this will help us get a local repro and fix the issue of the repeating tag parsing.

Could you repro the issue and provide any of the following if it occurs:

  1. Open the project on VS Code and let the C++ extension tag parse the project and provide the logs that show which files were being tag parsed just before the message that shows the extension is tag parsing again. This message could be "Warning: Database safety check failed. Recreating database." which indicates that it will tag parse again because the database (Browse.VC.db) was corrupted from a crash. You can also attach the entire log from the time the project was opened in VS Code to the time when the C++ extension shows it's repeating tag parsing.
  2. Could you also verify if the following message occurs from the repro? image
pepsi112-dude commented 3 years ago

I can't choose cpptools on the log output. It's not availible. I have instelisense installed with the cpp tools, I see it on my disk activity monitor, yet I can't selected from Vscode log output. i get a bunch of options log window, log main log C# but no cpp.

I have instelisense main extension installed. I installed intelisense austin.code-gnu-global. I have C# for visual studio code extension , for my c# target files. Clang format Visual studio code extension

that is it, these are my extensions.

I had the option in the log last time, I did post the log, but after I installed another version of Unreal and generated the code solution with into the VScode editor, it no longer appears. This log is related to my work space and project files ? maybe the older version of unreal does not generate this kind of log file with it's solution when it generates the code in VScode.

But I know the headder files causing the problem because they remain active they are just beneath the browse.Vc.db They are called by the cpp tools from VCcode constantly, the headers instruct to repeat but for a limited time, sometimes the MSVC compiler makes errors with some form of code and it needs to re-check to make sure it's correct.

But these repeat headers don't instruct anything (forever) that is what Vccode does, or intelisense from VCcode.

Here are the headers along with Browse.Vc.db it's just under Browse.Vc.db, they get called again and again. diskmonitor

So some other people complained about the same header type and file size of the DB file, so intelisense has a bug, it's bugged. It does not read things in a proper maner.

Other headers may have similar issues inside my project that I don't know about, these just popped up on my resource monitor.

Maybe I can try to install an older version of VCcode ? has any work been done on intelisense with this database stuff ? maybe this is the problem.

pepsi112-dude commented 3 years ago

What I think Vscode should do is make support for Unreal Engine, because "hordes of people" want to use this and ditch Visual Studio that it is flawed in my view and not for personal use, it is for big corps, not for personal end user.

There is other thing other then "big corps", these are indi developers, free lancers with professional licence, individuals, artists and so on.

Edit

I took another version of Vscode, reinstalled VScode with it, reinstalled extensions. Still the same problem. VScode is an application that does not stand still, it's dynamic when it does not need to be, when I don't touch the controls.

Exactly what a lite IDE does not do, and Visual Studio does. Bother you "in off mode" with - let's do some tasks while you are not doing anything.

I give up.

Joke (please stand still while the commander is not at the controls "it's not your spaceship")

Make a better product Microsoft.

pepsi112-dude commented 3 years ago

Problem solved.
I had to let intelisense go uninstalled the extension, debugging directly from the output logs of the project that I added there with some options. Manual build and compille from command prompt with MS build tools. All errors are logged and returned into good old windows command prompt.

VCode is still good it still loads my project with all the files from unreal from the editor, it has unreal sniplets to generate code functions.

But for debugging, building and compiling I use command prompt.

So if you have problems just disable intelisense and just use Vcode in this manner.

sean-mcmanus commented 3 years ago

If you're hitting a parsing problem with certain files, you can add the folder to the C_Cpp.files.exclude setting to stop parsing files in those folder, e.g. "C:\PROGRAM FILES\EPIC GAMES\UE_4.26\ENGINE\SOURCE\THIRDPARTY\boost".

I tried with the boost 1.76.0 and I didn't see any problem tag parsing the boost/preprocessor/repetition/ folder.

Your experience is not "normal", and could be caused by your usage of an older Windows OS, and it's not due to us targeting big corporations instead of indie developers. We can't fix an issue if we're not able to reproduce it and don't know what is causing the issue. We thought maybe your cpptools process was crashing and causing an issue with re-parsing afterwards, but that may not be what's happening if you don't see the crash message.