I came across this after searching for an efficient way to convert to a geometry collection.
However, after reading the documentation and trying it out, I had more questions.
1.Why do I need to specify a Static Mesh? This is a complete duplication of work as we already create collections from static meshes.
2.How can I share a flow with other Collections? I tried to share it with another collection, but it required a static mesh to be specified, so it got overridden by that mesh. This completely wasted my fracturing.
3.How do I delete a Dataflow? I want to undo the mentioned override.
4.I want to stop being asked if I want to use Dataflow when opening collection settings. Very annoying.
If you have already a geometry collection that you have created using the fracture editor, you need to create the collection from the source geometry
In Dataflow you can do it this way :
You can share a single Dataflow with many geometry collection, this will work perfectly fine with the the method I describe above using the source geometry
If you still want to use static mesh, in 5.6, you can define an static mesh as an input variable and override its value for each geometry collection using it
You can remove a Dataflow reference from a GeometryCollection by editing the DataflowInstance properties on the Asset Details tab in the Dataflow Editor
There’s no way to get rid of the popup asking for creating or adding a Dataflow
The logic for that is in UAssetDefinition_GeometryCollection::OpenAssets is you compile from source and want to locally change the logic
