When you load the editor after an upgrade, the log will warn you about deprecated blueprint nodes that need replacing, like this:
LogBlueprint:Warning: [Compiler PS_GameInstance] Warning K2Node_CallFunction_2978 is deprecated; Use the new version of Set Input Mode UI Only instead
It appears though, that the warning is only given if the deprecated node is in the event graph or a macro (one inside a function will slip under the radar).
It’s fairly minor but I figured it’s worth reporting. I noticed after upgrading to 4.13 that several classes were giving the warning (e.g. GameInstance) but my PlayerController wasn’t, and the node’s location appears to be the only difference.
I haven’t taken the time to reproduce it in an empty project, but it’d go something like this:
In a blank 4.12 project, make two blueprint classes A and B.
In class A, add a “Set Input Mode UI Only” node in the event graph
In class B, add a “Set Input Mode UI Only” node inside a function.
Compile both classes, save and close.
Upgrade the project to 4.13 using the “Open a copy” method.
When loading the project in 4.13, you will receive a warning about the deprecated node in class A, but not class B. It should warn you about all.
Unfortunately I see the warning you are seeing in both blueprints. Do you have any other steps I can take to recreate this on my end? Did the second blueprint already get updated to the non-depreciated node?
To tell, the “Lock Mouse to Viewport” boolean should have been changed to a “In Mouse Lock Mode” enum.
Ok - no the ones that weren’t giving the warning were still the old deprecated ones (coloured red). Only thing I can think of that might affect it was that it got compiled/run a few times.
I’ll up the 4.12 version of my project and send that to you, it’s fairly small.
OK I sent through the 4.13 version actually (via forum PM), so you don’t need to migrate it yourself - just opening it should hopefully reproduce what I’m seeing. Let me know if that doesn’t.
I see what you are seeing. Try moving the depreciated node out of the custom function, when you do this and then migrate the project to 4.13, do you see the same error?
I’m not really going have time to mess around with it too much I’m afraid - however I did remember one other thing that I should add:
That PS_PlayerController is a child of another PlayerController blueprint (the ones that give the deprecated node warning correctly aren’t) - this sticks out to me as the more likely culprit.
That would make sense. In general, unless you override the function, it is inherited and not subject to direct editing. The error would appear in the parent, but not the child because you can’t edit it in the child directly anyways.
The parent in this case is mostly empty (has none of the deprecated nodes in it) - the PlayerController that should be giving the warning has the deprecated nodes inside it’s own unique functions.