Local Variable references inside Blueprints do not resolve correctly after Move
I am on a project where we have downloaded a Marketplace Asset that requires a move to a different location under the Content folder in order to starndardize our internal process. During the move of the "Rome Fantasy Pack I" Marketplace Asset a blueprint related error surfaced.
I will include instructions to simulate and recreate this bug from a new project.
Creation of Simulated Marketplace Asset containing example test Blueprint: (This will create something that resembles the Marketplace Asset that we have purchased with a Blueprint containing both a variable and local variable containing references to another asset.)
Simulation of Asset Move: 1. Launch UE and using the "TestProject" created above 2. In the Content Browser, select "Content" and create a new folder named "TestDestination". 3. Move "TestMarketplaceAsset" by left-clicking its folder and dragging it over "TestDestination". Select "Move Folder Here" when prompted. 4. Fix Redirectors from the Move source if necessary (There should not be any redirectors in this simple move.)
Verify Bug: 1. Select "TestBlueprint" from \TestDestination\TestMarketplaceAsset\TestBlueprints and open the Blueprint Editor for this object 2. Select Variables->Components->MaterialArray and view the 3 elements in its Default Value. The correct references are made to materials that have now moved to \TestDestination\TestMarketplaceAsset\Materials 3. Now select "Local Variables (UserConstructionScript)"->LocalMaterialArray and notice the 3 elements in its Default Value. All elements are listed as none and their references have been lost.
Can this be verified and submitted as a bug?
asked May 22 '17 at 09:20 PM in Bug Reports
Thank you for submitting a bug report. I have reproduced this issue and logged a report for it here
You can track the report's status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.
answered May 23 '17 at 06:16 PM
Thomas G ♦♦ STAFF
Hi. As 4.19, this bug is not fixed. If possible to reopen it please?
answered Mar 22 '19 at 11:24 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here