Partitioned graph sourcing data from another partitioned graph fails to auto-update properly after loading scene without manual intervention

Development World Creation
, ,
1

I have a simple scene with two partitioned graphs, PCG_Generator and PCG_Reader. PCG_Generator simply scatters points on the surface, and PCG_Reader fetches the generated data and displays it via the debug node.

When I load the scene, I would assume that the data would be displayed properly without needing to go to the PCG_Reader graph and “reviving it”, for example, via pressing Force-generate on it(regular regenerate does not help). Is this a bug, or is there some setting that I’m missing?

The “Always requery actors” option on the PCG_Reader seems not to be helping either.

PCG_Generator:

[Image Removed]

PCG_Reader:

[Image Removed]

2

Steps to Reproduce

  1. Load the LV_PCGSupport map in the provided project.
  2. Observe that the partitioned graph PCG_Reader does not display points when the scene is loaded.
  3. Even pressing generate on the PCG component inside the PCG_Reader volume does not solve the issues either (Force refresh is necessary)

What I should see when I open the project:

[Image Removed]

What I actually get:

[Image Removed]

3

Hey Kyle,

I’ve fetched the latest changes that are published on the UE main stream, and the issue seems to be fixed.

Thanks,

Adam

4

Hello Adam,

I am currently investigating this issue to see if I can figure out the root cause behind it, but wanted to update you on a similar issue I found.

This blueprint node solved this issue for another user, however it does not explain why it is occurring in the first place.

I also found two other resources that give great rundowns of the PCG system, and while they aren’t indicative of any changes made on 5.7, they could still prove useful:

https://dev.epicgames.com/community/learning/knowledge-base/KP2D/unreal-engine-a-tech-artists-guide-to-pcg#overview

https://forums.unrealengine.com/t/how-to-affect-the-pcg-in-runtime-with-blueprint/1146953/7

I don’t see any issues similar to this on the public issue tracker, but I do see there’s many commits related to PCG that are not yet in 5.7.

CL 47218141 (5e67ed9) and CL 47218476 (6874121) could be worth checking out, amongst the many others I see.

Let me know if any of this helps!

Thanks,

Kyle B.

5

Hello Adam,

Glad to hear the issue is resolved! If you have anymore questions feel free to reach out here.

For now I will be closing this case.

Thanks,

Kyle B.