boocs
boocs
@leonfs I think that means you're using the Tag Parser Intellisense(which is fine). The latest UE4/UE5 use compile commands which override the includePath setting so includePath shouldn't be affecting anything....
Tag Parser Intellisense is super fast but not as smart as the default Intellisense which is fast with cpp files but slow with header files because of how it works(updates...
@leonfs I created a new issue for you called M1 Mac issues
I don't know if you have have my latest extension version 3.2.0. But I changed the strict setting documentation to say only use it if the extension's path setting is...
Yep, I guess my extension change wouldn't have worked if /user/bin/clang is also an absolute path on some systems. Maybe I'll just detect it on Mac and make sure if...
You can also remove the strict setting and Generate Project Files to get back the full xcode clang path in your compile commands file. After you Generate Project Files, you...
Once you figure out the full path that Unreal chooses you can just copy and paste that into the path setting and reenable the strict setting. Actually since they're going...
Here's how I'll fix this. - Recommend not using strict setting anymore. (Keep it for Windows users who want to compile with clang or future compiler bugs) - Without the...
I released 3.3.0 with the path fixes. You can remove the strict setting and reset your project(Generate Project Files) to fix it. The path setting will now be auto set...
I've released my guide on how to check for VSCode config bugs. This is just a partial Include Errors release. Note: This will get reorganized and changed. https://github.com/boocs/Unreal-VSCode-diy-config-check-github