I am having troubles upgrading my project to 4.14 from 4.13.
I am getting this error:
Running F:/4.14/Engine/Binaries/DotNET/UnrealBuildTool.exe -projectfiles -progress Messages while compiling F:\4.14\Spartan\Intermediate\Build\BuildRules\SpartanModuleRules.dll: f:\4.14\Spartan\Source\Spartan.Target.cs(72,26) : error CS0246: The type or namespace name 'GUBPFormalBuild' could not be found (are you missing a using directive or an assembly reference?) UnrealBuildTool Exception: ERROR: UnrealBuildTool encountered an error while compiling source files
If i go to my Target.cs and delete this:
it goes through but then i have (i assume because of this ) warnings all over my log.(https://forums.unrealengine.com/showthread.php?129505-You-re-exporting-a-UBlueprint-(-XXXX-)-editor-object-with-your-cook).
I have asked for help here a few days ago but the answer i got could not solve it. I get the warnings even for almost empty BP's so i know it has nothing to do with DEPRECATED stuff.
I am starting to speculate that the fact that you moved to the new Build Graph, is causing all this mayhem. I have read the answer here:https://answers.unrealengine.com/questions/524911/cant-open-project-after-update-to-414.html but it is nothing more than a generic exhortation to download the new and fixed version of the demo.
I obviously cannot do that since it is my game, that i have in development since 4.1.
Are there any specific instructions on what i have to do, in order to bring my project up to speed with the new method? I have no clue what that new method is, and where to point/modify my Target.cs in order to cure this.
I think that all of them are related, because I managed to fix it by taking a big risk, that fortunately paid off.
I created a vanilla 4.14 paper2d project and merged my assets to that one. After a lot of trouble of making it work again (collision channels, input, gamemodes, .ini's for the consoles, merging that project to my source control .etc) it loads up and compiles with zero warnings, meaning that I had nothing wrong with my code or assets. You guys just forgot/broke something to make that transition to the new system, trouble free.
I might have been lucky and fixed this, but in any case you should investigate why this happened in the first place. It could potentially destroy someone's project.
answered Nov 29 '16 at 10:44 PM
The build error that you mentioned referencing
The build error is, unfortunately, unrelated to the Blueprint warning messages that you mentioned receiving. The only thing that I can see that ties them together is that they both started to appear in 4.14. I am going to see if I can get together with someone to see if we can determine a situation that results in these warnings so we can give you a better idea of what to look for to clear them up.
The new Build Graph that is replacing the GUBP tools is intended to provide more flexibility and customization options when building a project or the Engine itself. I have not yet had an opportunity to work with the new Build Graph, but I can certainly look into it if you have additional questions about it.
answered Nov 29 '16 at 10:22 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here