Foliage becomes invalid when moving an entire level

Development World Creation
, , ,
1

Hey everyone.

Does anyone know how to fix invalid foliage after moving a level?

What’s the correct way to move a level/instanced foliage actor?

Scenario: When you make levels, they usually share the same starting location.
If you add different levels into a level, you would have to move them to build the world you have in mind. But I noticed that after you move a completed level to another location, the foliage becomes invalid and you can no longer edit it.

I made a video to explain this problem using a new project.

I find no logic in this behavior. It makes sense to me that foliage actors take landscape/meshes as parents and attach to them even if you move the landscape/mesh.

2

Hi, i m having the same issue. Did you ever manage to fix this?

3

Select it all by clicking the invalid button, drag it up in the air a bit, and then press the home key for it to fall back down to where it’s valid.

Note that landscapes should not be moved unless you know what you are doing. And that after moving them you need to clear the grass node and set them up via console for some things to take effect.

What you should do is move levels around within a persistent via world composition.

1 Like
4

I have the same problem, and you will find that the invalid instances overlap