Migrated Material Lose Texture Reference in Destination Project

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:

  1. Open a project (we will use the Epic Zen Garden for example)
  2. Locate the waterfall (particle system) asset in the Content Browser
  3. Select the particle system asset (P_WaterFall_Vista )
  4. Right click and select “Asset Actions → Migrate…”
  5. Ignore (cancel) “Save Content” dialog
  6. Select the “Assets” folder of a destination project when prompted
  7. Save

IN OTHER PROJECT:

  1. Open project
  2. Navigate to the Water/Effects/Materials/Water folder
  3. Open the material; M_WaterFall_Vista

RESULT: ERROR! [SM5](Node TextureSample) Texture =Sample Missing input texture

Looking at texture nodes also shows three (3) empty texture nodes.

NOTE: This becomes a huge mess when migrating large numbers of assets and results in hours of lost time reconstructing materials.

Hello NinaSzeven,

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.

Let me know if you have further questions.

Thank you,

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!