I have a problem with moving assets from one project, to another, when I moved all the assets, the references of these assets are none\empty, so blueprints\materials\skeletal meshes, all broken after moving. And yet, it’s not the case when I do it with the migrate option, but what if I wanted to move it to different PC? I can’t migrate it, so is there any fix for this nasty problem?
My steps:
Migrate some assets from one project, to my main project.
Connect to Source Control, marked for add, Sync In.
My colleague is importing new assets through p4v(We’re using perforce).
And boom, he have a lot of broken assets, with empty references.
This is expected behavior. The assets are looking for specific filepaths, so moving the folder without using the migrate option breaks those references and your assets will have to be manually re-referenced when placed in a new project or onto a new PC. What you could do is upload the initial project with your assets to perforce, have them download that project then migrate the contents using the migrate feature. This would allow them to properly move the assets to prevent referencing errors.