This issue has been closed as 'Won't Fix' due to an extended period of time without updates. If this issue is important to you please let us know by posting on the AnswerHub or UDN, and Epic will re-open the ticket for further review.
Currently, after migrating a blueprint that is based on a code class to a new project, the blueprint breaks due to unknown parent ([Link Removed])
Migrating & copy/pasting the code along with the blueprint still causes the BP parent to become unset after migration and the blueprint is unusable.
Result:
Blueprint has no reference to its parent after migrating and cannot be opened. This occurs even if the code class is copy/pasted into the second project before migrating the blueprint
Expected:
Migrating code/blueprints from one project to another update references to the new project
Repro Rate:
3/3
Head over to the existing Questions & Answers thread and let us know what's up.
10 |
Component | UE - Gameplay - Blueprint |
---|---|
Affects Versions | 4.11 |
Created | Mar 22, 2016 |
---|---|
Resolved | Mar 26, 2018 |
Updated | Mar 26, 2018 |