4.14 Compiling warnings

Hello,

I just upgraded my project to 4.14 from 4.13 and I get 300+ warnings about something that I have no clue what it is.
(XB1 build. Did not have time to test it for the other platforms)

It affects all my blueprints and not only. It even complains about things that must be default to the engine since i do not know what they are.

LogBlueprintSupport:Warning: You’re exporting a UBlueprint (‘DmgTypeBP_Environmental’) editor object with your cook. This is now DEPRECATED (the Blueprint’s class & CDO should be all that’s needed). Please fix up any relience you have on it, and add the following to your editor ini
file (these settings will become the default):

LogBlueprintSupport:Warning: You’re exporting a UBlueprint (‘LevelEditorAttract’) editor object with your cook. This is now DEPRECATED (the Blueprint’s class & CDO should be all that’s needed). Please fix up any relience you have on it, and add the following to your editor ini file
(these settings will become the default):

LogBlueprintSupport:Warning: You’re exporting a UBlueprint (‘LevelEditorOverview’) editor object with your cook. This is now DEPRECATED (the Blueprint’s class & CDO should be all that’s needed). Please fix up any relience you have on it, and add the following to your editor ini fil
e (these settings will become the default):

Even my game instance!

LogBlueprintSupport:Warning: You’re exporting a UBlueprint (‘SpartanGame_GameInstance’) editor object with your cook. This is now DEPRECATED (the Blueprint’s class & CDO should be all that’s needed). Please fix up any relience you have on it, and add the following to your editor in
i file (these settings will become the default):

Do you guys know what is going on??

Thank you!

You have a lot of deprecated stuff in your blueprints, the deprecated nodes should have a warning sign next to them and be red in color.

Hey,

There is not a single depreciated thing in my BP’s, and this problem is engine wide. It complains about everything.
This is probably related with some .ini settings or with this issue:

.

Hi ,

I replied to the other Answer Hub post. Some settings cannot be transferred to a new engine version and the engine will just return a warning message.

For example in the post you linked the warning message was appearing because the default preview scene settings were changed in the mesh viewer. These settings can’t be read and won’t transfer to the new engine version. It is a very trivial issue.

In this case it seems that some of your Blueprints have elements that are considered deprecated. This is just a recommendation from the engine against using the proposed deprecated item. The reasoning is it may include a feature that may be reworked or changed in a future release. Please investigate the assets in question to make sure that they are working properly.

If there isn’t any detrimental changes in your project that prevent you from working I wouldn’t be too concerned. If you are using nodes that are considered deprecated in your project they will be highlighted with a yellow warning strip. They should still work as intended.

Let me know if you have any additional issues,

Thank you Ed,

My problem is that I do not a single visual warning (yellow warning strip) on my project. But it complains about everything.

Is there a possibility for you to ask around what could cause these “silent” warnings?

I am using Paper2D, a plugin that has not been updated for over a year now and I fear that the lack of development might affected something.

We are nearing the completion of our game for all major platforms and the last thing I want is for everything to fall apart.

Thank you!

There have been quite a few deprecated functions/features listed in the 4.14 release notes. Just search for deprecated and you can see if there is something in your code that is using a deprecated function for example “Get Resource Size”.

Things are being marked as deprecated usually because they are getting replaced with something better. The log lists what UBlueprints to search.

Final note, I would not recommend working out of a new engine version for a project that is close to release. The only reason for upgrading is if there is a feature that is absolutely necessary for your project. Upgrading a heavily developed project is likely to introduce a lot of potential problems.

If you are using a paper 2d project I don’t think a 4.14 upgrade is worth the risk. Especially since 4.14 is still fresh and hasn’t been patched with hotfixes.

Regards,

Ed

Its not like i have a choice…

I need the latest SDK’s for the consoles in order to publish, and 4.13 would not cut it for a march release.

Thank you for the heads up. I will take a look and please try to tell us what setting must we change back in order to get rid off the other issue.

Cheers.

EDIT: I just saw the answer. !