Migrating from the default M4 project to our own custom project takes a little bit of setup before hand so that everything (the Terrain Generator, Virtual Heightfield Mesh, RVT, etc.) can be used fully in our custom game.
Follow the steps below to Migrate M4 to a custom project in Unreal Engine 5, with everything set up and ready to go.
Preparing your custom project
Step 1:
Let’s first set up our project that we’re wanting to Migrate M4 to.
In your custom project, go up to Settings at the top of the Editor and click “Project Settings“.
In the window that pops up, type in “Enable virtual texture support“, toggle this on.
Don’t restart your editor just yet if it tells you to, we’re going to enable a couple of other things first.
Step 2:
Now go up to Settings again and press Plugins. This time, the Plugins window will pop up.
Type “Landmass” into the window and enable the Landmass Plugin.
Still don’t restart just yet, one more setting left.
Step 3:
In the same Plugins window, now type in “Virtual Heightfield Mesh“, let’s enable this too.
After that, restart the Editor by pressing the button at the lower right hand corner.
Migrating M4 to your custom Project
Step 4:
In the M4 project downloaded from the Marketplace, right-click the M4 folder and press Migrate.
A window will pop up, make sure to UNTICK the Landmass folder in here. Then push the “OK” button, in this pop up.
Landmass is automatically included with the engine in UE5 and not needed to Migrate. This is just something weird UE5 is doing, trying to migrate engine content.
IMPORTANT, not doing this step will cause an error.
I imagine Epic’s going to fix this in a future update to UE5. Since the same thing happens on a blank Third Person Template project too in UE5, but with Control Rig instead.
Step 5:
Next it will ask you to choose a Content folder to Migrate M4 to.
Choose the Content folder of the custom project, which you’re wanting to Migrate M4 to.
We’re now ready to fully use M4 in our custom project
