I was making a project via blueprints that I need to convert to C++ due to some features I need to add that aren’t as accessible in BPs.
Followed a bunch of tutorials and guides, both official and unofficial, but two problems keep occurring:
1st is that, even with the naming convention .editorconfig file, VS22 still says that it cannot “Open source file” (using include, as an example) or similar errors, I have C++ for gamedev installed in VS but it looks like it doesn’t exist, reading like I don’t have it.
2nd is that now that I’ve “managed” to create a new C++ class inside UE5.4, after I close the engine/project, it refuses to open again, saying:
"The following modules are missing or built with a different engine version:
[ProjectName]
Would you like to rebuild them now?"
After I click “yes” to rebuild it, it gives this message:
“[ProjectName] could not be compiled. Try rebuilding from source manually.”
But when I try to rebuild it from source (or at least, what I think it is - new guy into this), it just doesn’t work.
Hey there @LuhBonettoRD! I’ve seen your other recent topics on issues with your C++ project. So considering the infos you’ve provided there as well, there’re a multiple things to cover here:
The reason for the error & warning messages you’re encountering is likely due to the VS version you’re using. The latest VS 2022 version (17.12) seems to have NuGet related issues when used with UE 5.4. The officially recommended VS 2022 version for UE 5.4 is 17.8.
It also appears that you later converted your blueprint project into a C++ one. Things might have gone wrong there if you also upgraded your engine version along with that. So instead of regenerating the VS related files, I’d recommend you creating a blank project and migrating your assets into the new project. Make sure to enable all the plugins you use in your original project before migrating your assets!
You can migrate assets by right clicking on an asset, navigating to the Asset Actions on the menu that pops up and then selecting the Migrate option. Do not uncheck any of the already ticked dependencies and just click on OK, and then select the new project’s Content folder as their new home. You can also migrate multiple assets at once, or just right click on a folder to migrate all of the contents inside! When you right click on a folder, the Migrate option won’t be hidden behind any additional menus.
If your new project crashes while migrating or you’re unable to build / open it after migrating your assets, try migrating the assets in separate bulks to see which one’s causing the issue.