A licensee has complained that if you assign a preview mesh to a Material Instance, it becomes a referenced asset, so migrating that MatInst will also migrate that mesh and whatever material is assigned to it. In some cases, this can bring over a bunch of stuff you don't need.
The normal material editor allows you to "clear" the preview mesh, but there seems to be no way to do that in the Material Instance editor.
*As a workaround, you can replace your preview mesh with something from engine content (cube, etc) and it won't try to migrate that.
1. Create a material and an instance of it
2. Assign a preview mesh (I used SM_Rock in Starter Content)
3. Try to migrate the Material Instance
Result: SM_Rock, its materials and textures will all be included in the migration.
How does TextureRenderTarget2D get TArray<uint8> type data?
How do I set a material as a post-processing material?
Why does the REMOVE method of map container remove elements have memory leaks?
How to delete some elements correctly when deleting an array loop?
UMG RichText not appear image when packaged
What is the difference between Camera and CineCamera?
How to implement springarm components to scale according to mouse position in spawn?
What controls of umg have mouse wheel events in UE4.27?
Why does UV setting float2(1,1) display incorrectly in the material's custom node?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-21045 in the post.