0
\$\begingroup\$

I'm currently trying to migrate some VFX assets (meshes, materials, textures, material instances, niagara emitters and niagara systems) to another project on another machine.

My folder structure looks like this: C:\Users\Documents\MyName\UnrealProjects\MyProject\Content\ThirdPersonBP\MyVFX

My current workflow is like this:

  1. In Unreal I right click on "MyVFX" and choose to migrate it and then choose a destination folder (not another project).
  2. Zip the migrated folder and put it on another machine.
  3. Unzip "MyVFX" from the zip to C:\Users\Documents\OtherName\UnrealProjects\OtherProject\Content\ThirdPersonBP
  4. Put the niagara system into the level

The problem that now occurs is that references are not set. For example, the Sample Texture node in a material does not contain a set texture or a niagara system does not have anything set in the Mesh Renderer module (neither mesh nor material).

Everything works again as intended once the references are set again manually. But, that's tedious work of course and I don't want my teammates to do that for every effect I create.

\$\endgroup\$
5
  • \$\begingroup\$ Try to fixup redirectors before the mograte \$\endgroup\$ Jun 13, 2020 at 13:25
  • \$\begingroup\$ @ColdSteel that didn't make a difference :( \$\endgroup\$
    – iQew
    Jun 23, 2020 at 9:23
  • \$\begingroup\$ You may want to check the Unreal bug tracker and see if anyone has encountered this - you've a better chance of getting a reply from an Unreal Dev on the Unreal Forusm \$\endgroup\$
    – Natalo77
    Jun 23, 2020 at 13:50
  • \$\begingroup\$ Try to unzip to content and not to content/thirdpersonBP since migration assumes it is going to be in content and nowhere else \$\endgroup\$ Jun 23, 2020 at 22:52
  • \$\begingroup\$ @ColdSteel this didn't make any difference, unfortunately. \$\endgroup\$
    – iQew
    Jun 24, 2020 at 15:07

0

You must log in to answer this question.

Browse other questions tagged .