ue4-intellisense-fixes: Stuck on "Attempting to fix the json of launch.json..."
Apparently mine got stuck on Attempting to fix the json launch.json. I’m on a M1 Pro Mac.
Searching with fast-glob found nothing. (Sometimes isn't bug)
*.uproject file was found!
Extension "UE Intellisense Fixes" 3.5.0 is now active!
Found Unreal Engine v5.1.0
Fixing compiler paths in compile commands.
[...]
Attempting to fix UE workspace(Add empty tag parser).
UE's tag parser includes are set to empty array for performance.
The setting limitSymbolsToIncludedHeaders is already set to true.
End fix UE workspace(Add empty tag parser).
Attempting to fix wrong cppStandard.
Info : UE4 should be default c++14 (it can be c++17 with some special configuration)
Info : UE5 should be c++17
Extension's cppStandard setting was set to empty string.
Intellisense will use cpptools cppStandard setting instead of this extension's setting.
Current VSCode/cpptools cppStandard is: (Can be blank)
Current c_cpp_properties.json's cppStandard is: c++17 (Overrides VSCode/cpptools if not undefined)
Current c_cpp_properties.json's cppStandard is: c++17 (Overrides VSCode/cpptools if not undefined)
Current VSCode/cpptools cppStandard is: (Can be blank)
Current c_cpp_properties.json's cppStandard is: c++17 (Overrides VSCode/cpptools if not undefined)
Current c_cpp_properties.json's cppStandard is: c++17 (Overrides VSCode/cpptools if not undefined)
End fix wrong cppStandard.
Fixing launch.json.
Attempting to fix the json of launch.json...
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 19 (9 by maintainers)
It’ll be slow in header files but should be decently fast in source files once it loads.
I’m currently creating a clangd/unreal project creator extension. Its intellisense is decently fast in both header and source. Not sure how good it is though but I was going to thoroughly test it after I finished the extension. UE 5.1 made it a little easier since they fixed a lot of bugs they had in the clang database that unreal creates (at least for Windows). Still has a small bug, that needs to be fixed by my extension, but works nicely.
Nope, it should be fixing launch.json in your project’s .vscode folder.
Actually I should’ve been paying more attention to the log. You’re on UE 5.1 and using a Mac m1. You shouldn’t have to fix anything in launch.json so it should just check and skip over everything in the launch fix. Strange…
I’ll have to create an update, with detailed logs, to see exactly where it stops. I’ll do that later today.