Cascade - LOD's dont auto-update replacing mesh or texture from highest

4.16 up to latest.

When an emitter has LOD’s active, even when untouched or “shared from highest” (not copied from higher/highest) static meshes and materials are not properly updated into other LOD’s when changing them in LOD0.
Meaning that if you duplicate an emitter and replace its material or texture, once the LOD1 or lower kicks in, the old mesh/material will be shown.

any other module that has regular float values and the like do update their changes properly to other LOD’s. (when not set to copy from higher/highest or in other words “Shared from highest”)

edit: This is easiest seen when “enabling particle lod switching” under “project and editor settings > previewing”

I’d make a video right now, but got me a deadline in a few hours.

additionally: this also seems to happen when you create a graph for i.e. color over life, create two lods that are shared, then copy the emitter to another system.
now the LOD’s copied to this new system cant find their graphs because the graph-data table was not copied along with it, and cascade cant find it in the new one. causing: https://i.gyazo.com/906fd4089380485a603e51be651b3685.png

Hi Luos,

Thank you for your report. We will begin investigating this issue as soon as possible. If we are unable to reproduce the problem, or need more information, we will follow up with some additional questions for you. Otherwise, we will post an ‘Answer’ once the issue has been logged in our bug database or we have a solution for it.

Hey Jon, thanks for checking the bug out.
In the meantime I recorded a video of it happening with the mesh module, but it happens with most modules that have values.

Steps: 1. duplicate & share 2. replace a shared module. 3. modules in other LOD's are not replaced.

Hi Luos, I’ve consulted with our subject matter experts and this is by design- the system does not automatically carry changes from one LOD to another.

A module carries the LOD data with it when you duplicate or share the module so the new copy (or reference) will share LODs 0, 1, and 2. But if you change LOD 0 without regenerating LODs (or manually changing LODs 1 and 2) those will still reference the old mesh, material, or whatever.

To fix this, you would select the Mesh Data (or whichever module isn’t working like you want) in the LOD that seems to be wrong, right-click on the module and Duplicate From Higher (or Highest) to regenerate just that module and make your changes to it at that LOD level.

So switch to LOD 1, right-click on Mesh Data in Shared Duplicate emitter, and duplicate from higher should fix.

1 Like