This was the solution. Thank you. Hopefully my like and comment will push this toward the top of the Google results.
Works for 5.5
1 Like
Did everything that has been posted in this topic and still got this message, found this in the engine source
bool bNaniteDisabledButNoFallbackMeshes = !UseNanite(Scene->GetShaderPlatform()) && !AreNaniteFallbackMeshesEnabledForPlatform(Scene->GetShaderPlatform());
// ...
if (bNaniteDisabledButNoFallbackMeshes)
{
static const FText Message = NSLOCTEXT("Renderer", "NaniteDisabledButNoFallbackMeshes", "Nanite is disabled but fallback meshes were stripped during cooking for this platform due to project settings. Meshes might not render correctly.");
Writer.DrawLine(Message);
}
What finally freed me from this message was enabling “Generate Nanite Fallback Meshes” in Project Settings → Platforms → Windows (as I’m developing on Windows).
As far as I know, this option does absolutely nothing on meshes that don’t have Nanite enabled - am I correct?
It might be helpful to alter this message to something like this
"Nanite is disabled but fallback meshes were stripped during cooking for this platform due to project settings (relevant property: bGenerateNaniteFallbackMeshes). Meshes might not render correctly."
This is not a bug. Disabling Nanite in the project settings turns the feature off, but individual meshes may still have Nanite enabled, especially if you are using marketplace assets.
r.nanite 0 only turns the message off once for that session. Restarting the project means the message will appear again.
The actual solution is what Wormy said: Nanite is enabled but cannot render - #6 by Mautar55
Select your Content folder and filter Static Mesh. Ctrl + A to select all the meshes, then right click and look at the Nanite bool and you’ll find that there’s a - in the Nanite Enabled checkbox. This means that some of the meshes in your project have Nanite turned on, so you need to click on the box to make sure it becomes unchecked. This will actually fix the issue.
