4.2 When a BP is loaded, it is marked as "changed"


I have a strange behavior. Anytime, a BP is loaded it is marked as changed even if I don’t do any modification.
More, if I save it and open it again, it is still marked as changed.

Last, if you launch a PIE Session, all the blueprint used will be saved again if you press CTRL+S.

It seems something has changed during the loading process that mark them as changed.


no one notice this? am I alone?

I think I am noticing this as well and when i save the blueprint assets and then diff them against the perforce depot using the UEd diff there are no actual changes.

I’m not sure if this is the exact thing you are seeing or not but it does seem similar.

I too am curious if anyone else has this issue.


Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.

If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.

Thank you.


I’m still expriencing this in 4.4.3 but now the scope is reduced to only the BP that I’m opening.

I just open it and it is mark as changed. Do you need other elements to track this?


Hi ,

Does this occur on a clean project with no additional content? Additionally, do you have blueprints that are calling the blueprint that is marked as changed? If so, have any changes been made to these blueprints?

Hi ,

We have not heard from you in quite some time. I am marking this as answered for tracking purposes. If you are still experiencing this error, please comment with the requested information. Thank you!


I double check in 4.5 release and it’s working as expected.

bug solved.