GetDDC and dynamic mesh generation in PCG

Development Pipeline & Plugins
, ,
1

Hi UDN !

I’m generating DynamicMeshes saved in assets, on multiple PCG tools, and quite often (but still randomly) I get a big freeze which can last up to a minute.

After profiling a bit with insight in the editor, I noticed that it was the GetDDC() method which takes a long long time (very often looked like a timeout or something).

We might have an issue with our cache that we struggle to identify, but I was also wondering if that really makes sens to check the DDC in this case, as they are 100% unique meshes, and if there was a way to disable it in some cases like if the source mesh is a dynamic mesh ?

We tried to increase p.BodySetupSkipDDCThreshold but it didn’t help much …

Thanks for any insights or ideas on that matter !

[Image Removed]

[Attachment Removed]

2

Hi Guillaume, we don’t provide a way to skip DDC for static meshes. If you generate the dynamic meshes deterministically, which we recommend ensuring, then it should be able to find previously-built data in the DDC and save time even for dynamic meshes. If you want to look into where that time is going, I suggest running with the LogDerivedDataCache log category at Verbose or VeryVerbose verbosity and then inspect the log to see where that request takes a long time, e.g., in Zen or Cloud DDC or whatever.

[Attachment Removed]