When moving materials to a different project using the “Migrate…” feature on OSX in the asset browser, references to the textures used in the textureSample nodes of the material blueprints are broken (lost). This results in (essentially) untextured
STEPS:
Open a project (we will use the Epic Zen Garden for example)
Locate the waterfall (particle system) asset in the Content Browser
Select the particle system asset (P_WaterFall_Vista )
Right click and select “Asset Actions → Migrate…”
Ignore (cancel) “Save Content” dialog
Select the “Assets” folder of a destination project when prompted
Save
IN OTHER PROJECT:
Open project
Navigate to the Water/Effects/Materials/Water folder
In order to report this issue I will need to be able to reproduce it using the starter content and minimal assets. I just ran this test on my end using the starter content and the Zen garden content, and did not get the same results.
I would also try migrating assets in smaller chunks to see if that helps. I have seen this stuff happen before, but I couldn’t reproduce it going from the Zen project to a new blank one. Try migrating to a completely new project from the Zen project to see if there is a difference there. You could have some conflicting references, but it is hard to tell.
Like a line from the movie Brazil; “The pipes, they fixed themselves”.
I removed 4.13.2 and 4.12. Then reinstalled 4.13.2 and everything seemed to just work. Wonky install or weird configuration issue?.. I don’t know, but everything seems fine now. - Thanks!