Hi
Sure.
So the main parts of the implementation here would be.
1. New custom NDC type that can internally store different FNiagaraDataChannelData.
Similar to how the Islands data channel does it but in your case you’d want to split these up by spatial location and physical surface etc or however else you’d like.
See UNiagaraDataChannelHandler_Islands::FindData().
2. A component type that would allow access to this surface data.
We currently use FNiagaraDataChannelSearchParameters to pass in the location data that we use to find which NDC Island we will pass the data into.
Ideally this would be more flexible and allow us to pass in whatever data the NDC needed to do it’s internal routing. In your case a surface type.
This is what I’m working to improve currently. Until this is available, there is also a Component ptr passed in.
The Islands NDC only uses this component to take it’s location.
However, with your own custom NDC type you could use this component to get the correct surface type for the current FindData() call.
You could pass in a custom component or you could possibly hijack the ComponentTags?
Hope that helps.
Simon