Is the DynamicMeshComponent's distance field generation option editor-only?

Hello and thank you! Here is my log, but I’m not sure it is very useful because it doesn’t give much information. Here, I subclass UDynamicMeshComponent, don’t verrride anything and add to it some geometry. In GenerateDistanceField mode there is a crash, otherwise there isn’t.
DWI_core.log (94.6 KB)

As you can see, I also generate distance field data myself and log this about it but it is actually never used anywhere in the code in this version. However, it is still relevant as my distance field function is the exact same as the default one copy-pasted except for sign computation of the SDF which I changed, so it should give results which are exactly the same size in bytes, and i noticed that “Resource size bytes” is significantly bigger in packaged builds as compared to editor builds. Moreover, it is completely consistent in all packaged builds, and completely consistent in all editor builds. I wonder if it’s generating unwanted data that causes issues when the lumen cards are generated.

Note that without the “GenerateDistanceField” mode, everything works as intended