We currently have a forest, and it is divided into multiple PCG Partition actors. The problem is, the WPO disable distance is set to a value, and it’s far from being respected. All the actors have 2000 as value, but its looks more like 500. [Image Removed]
Hi Pedro,
Thanks for reaching out.
Do you have a repro project we could have a look at?
There are multiple things in play here that could impact this:
- Are you generating at runtime?
- If so:
- What are your generation radii ? cleanup radii?
- Otherwise:
- What’s your streaming/loading distance (world partition settings)
- If so:
- What kind of component are you spawning from PCG?
- In your example it looks like static mesh components?
Let us know more and we’ll help you out!
Cheers,
Julien
Hi Pedro,
Seems like the file isn’t available (?) could you re-upload it?
But let’s dig a bit more - your actor is name TO_DELETE… which seem to indicate an error in partitioning, maybe something to verify here. Any warnings in the logs?
These might be unhooked to PCG and could be garbage data here and that could explain this?
Cheers,
Julien
Hi Pedro,
If you can provide us a sample project to reproduce the issue, it would be a lot easier to dispatch your issue to the right team.
Seeing this is post-generation on a static mesh component, this might be a rendering issue and not a procedural issue,
Does this happen:
- only on static mesh components? (vs ISMs or HISMs)
- only on partition actors?
Do you do anything special in your material wrt WPO ?
Thanks,
Julien
Hi Julien, it’s only on static meshes and on partition actors. Nothing special in the material, it does reduce the WPO on distance, but the problem persists, with or without.
Hi Pedro,
How do you place your static meshes in PCG if they’re not ISM/HISM?
As far as I know, this isn’t stock PCG, so it’s not easy for me to help out.
Also, please provide an example to repro the issue.
Cheers,
Julien
Hi Julien, we don’t have a repro. But it’s not runtime pcg.
We are spawning vegetation, static meshes. About the world partition settings
Hi Julien, that’s not the case, it happens on all of them