Download

VSCode errors

Hi, does anyone know how to fix these errors?

I create the third person sample project with blueprints. Then I create a c++ class and after open it in vscode this is what I see. I can compile the project with “Win64 Delevopment Build” without problems, but these errors are still there.

I have found similar threads like this but nothing is working for me :frowning:

I’ve never made a BP project and added a C++ class later. Do you have the engine C++ as part of your project? It looks like you don’t.

yes everything works fine. I want a blueprint project but with some c++ blueprint nodes here and there when things get too much bloated. I can compile from VSCode and from UE main toolbar with the Compile button. I can even use my custom c++ nodes just fine.f Still I have those red warning/errors inside vscode which are a nuisance. I think they are related to intellisense but I don’t know hot to solve it.

Ah so it’s not an actual bug in your code but VSCode acting up. I’m assuming you have the C/C++ extension installed from Microsoft.

Not sure about a proper solution, you could try to write the full path to one of them and see if that fixes it.

There are ways to tell intelliSense to ignore errors on the following line. If nothing else, you could try to do that. It would probably be an annoying solution, as you’d have to do that with most includes, but it does get rid of the squiggles.

Yes I have that extension. Looks like the problem is OmniSharp pointing to some random project intead the one I’m using. But after I execute “Omnisharp: Select Project” I can’t find mine in the list. Lol no idea what’s going on.

Try my VSCode/UE Intellisense Fix extension or update the version you already have. I just released an update for 4.27.0

2 Likes

Oh wow it’s working!! Followed all the steps you mention (thanks for explaining them step by step) and it works perfectly on UE 4.27. You are a genius! Thanks a lot!!

Extension fixed include errors for me as well, thank you very much!

I was specifying a correct includePath in c_cpp_properties.json, but I wonder why that didn’t work, while by all logic it should have.