4.7.1 Blueprint Function Library unable to save

anonymous_user_126fa609 · March 1, 2015, 2:26am

branch
4.7.1 Binary, as downloaded from launcher

build Version:
4.7.1-2462028+++depot+UE4-Releases+4.7

#Description of Issue
Cannot save Blueprint Function Library with any function that calls another function in same library. following error message is reported:

Can’t save …/…/…/…/…/…/Users/User/Documents/Unreal Projects/TestUpdateProject/Content/THIS_IS_THE_PROBLEM.uasset: Graph is linked to private object(s) in an external package.

External Object(s):

/Engine/Transient

Try to find chain of references to that object (may take some time)?

Screenshots

function library simply needs to be set up as in following screenshot to cause this issue

Reproduction Steps

Create a new Blueprint Function Library.
Create two functions in function library, “Foo” and “Bar”.
Make function “Foo” call function “Bar”.
Save and close project.
Re-open project
function library will be unable to save, giving error above.
Delete call to function “Bar” from function “Foo”.
function library will now be able to save.
Close and re-open project
function library will once again be unable to save.

Attachements

attached [ file][2] contains a function library that reproduces issue in a blank project.

anonymous_user_33800a51 · March 1, 2015, 9:53pm

Hi SuddenlyMuffins,

Thanks for report! I was able to reproduce this in 4.7.1 as well as our internal build, and I have entered a bug report for developers (UE-11185). I’ll let you know when I see any update on its progress. Thanks!

anonymous_user_4dea0a89 · March 6, 2015, 8:39pm

I would really love to see this fixed. I’ve been seeing this bug pretty regularly last few days – sometimes even in blueprints that I’m not modifying.

anonymous_user_33800a51 · March 6, 2015, 8:53pm

I know it’s being looked into currently, and it’s considered a Critical bug, so hopefully we’ll see a fix soon. I will update this post when I see progress on it. I have added a note that this is occurring for more people, as well. Thanks for your patience!

anonymous_user_126fa609 · March 6, 2015, 10:29pm

Thank you , It’s good to hear this is known and being fixed.

OhiraKyou · March 6, 2015, 10:39pm

Would you mind poking someone about this issue also related to function libraries? I can send a project download link if necessary.

anonymous_user_199281e7 · March 8, 2015, 2:38pm

I have had this issue since 4.3 if im not mistaken. not sure if it helps but all more info right…
I’m now up to having to replace over 100 connections after opening my project because of this… here’s what I do to make life a little less stressful…

use reroute nodes on either side of all function calls that go to same blueprint(so you can quickly make sure you have them re-pinned correctly)
comment all said function nodes as (Corruptable) of something similar so you can do a Ctrl-F and run a quick search for them all)

also notes on things I have found running a text comparison only differences I notice before and after reboot/ replacement is…

DefaultObject=Default__NewFunctionLibrary_C
gets changes to…
DefaultObject=REINST_NewFunctionLibrary_C_0
and pin numbers change to a much lower value however copy pasting back in to blueprint does not fix… pasting in to a text editor and correcting he above line and pasting back in to editor does correct issue. leading me to believe this is in fact issue.

note only REINST needs changed to default to save but it seams _0 at end will still cause a compile warning stating that Default_NewFunctionLibrary_C_0 cannot be found… refreshing nodes seams to correct compile warning however…

after going back and testing it is only easily reproducible on 4.7 however as I said it has been happening for some time previously (do to its semi random nature I attributed it to a mem leak though this no longer seems to be case.

nothing in here is a proper answer as it still require 30 min to fix every time project is opened… not sure why it was marked answered…

anonymous_user_33800a51 · March 8, 2015, 4:11pm

It’s marked as Resolved because a bug report has been put into our system. Once we have an update on it, we’ll post here.

anonymous_user_199281e7 · March 8, 2015, 4:30pm

o ok cool

anonymous_user_33800a51 · March 10, 2015, 3:42pm

Hi all,

This has been fixed in our internal build, and fix should be included in 4.7.3 release coming soon. Thanks for your patience! Please let us know if issue is not resolved after upgrading to 4.7.3.

anonymous_user_8f043ea0 · March 10, 2015, 3:43pm

Is this also a fix for this?

anonymous_user_33800a51 · March 10, 2015, 3:48pm

It’s possible, but without a solid reproduction for issue in that post I can’t be sure. It’s certainly worth trying again once 4.7.3 is released.

anonymous_user_3933a5bf · March 11, 2015, 10:36pm

Are there some specific commit SHA #'s you can post so we can pull down commits in our 4.7.2 build?? I have same bug and it was reported that following commits addressed it:

c9aa7ac0c080c10204ed1eaa5839f017ac1609e3 and
cb17e17a1d06e1e2e64bd402cf7247315cef3edf

However, I still get error so I’m wondering if there are more commits to get!

anonymous_user_33800a51 · March 12, 2015, 10:40pm

Hey jeffvoight,

Should be this commit:

Slayemin · March 18, 2015, 12:04am

I’ve been getting this issue as well. I am using 4.7.0 and added above changes to engine, completely rebuilt engine, and still got errors, though error message has changed slightly.

Old Error message: Warning Can’t save …/…/…/…/…/…/Unreal Projects/MageMaster2/Content/Assets/FuncLib.uasset: Graph is linked to external private object (unknown culprit) (unknown property ref)

New error message: Warning Error saving ‘…/…/…/…/…/…/Unreal Projects/MageMaster2/Content/Assets/FuncLib.uasset’

anonymous_user_33800a51 · March 18, 2015, 12:09am

Can you try opening a copy of project in 4.7.3 and see if it occurs there as well? Thanks!