Dataflow Material Assignment seems to have broken in 5.6

Development Asset Creation
, ,
1

Hi there,

The Dataflow refactor from UMaterial to UMaterialInterface in 5.6 appears to have broken Geometry Collection Material Assignment from Dataflow GeometryCollectionTerminal nodes.

Previously functional Dataflow code from 5.5 like the following is affected:

(from [Content removed]

[Image Removed]

New Dataflow code like that displayed in the repro steps exhibits the same issue.

I had a look through the Licensee depot to try and locate the issue, but was unsuccessful.

Kind regards,

Josh.

2

Steps to Reproduce

  1. Make a Blueprint Actor
    1. Add 2 Mesh Components with non-default WorldGrid Material
  2. Place Blueprint Actor into Level
  3. Create New Geometry Collection using Actor
  4. Use the following Dataflow:
    1. [Image Removed]
  5. Observe Lack of Material in GC
  6. Place GC in Level
    1. Observe Lack of Material on GC
  7. Add Field System in Level to Fracture GC
    1. Simulate Level
    2. Observe Lack of Initial Material on GC
    3. Observe Correct Material upon Fracture
3

Hello [mention removed]​

Thank you for reaching out and bringing this issue to our attention.

I was able to verify the described behavior:

[Image Removed]I’ve checked in 5.5, it worked:

[Image Removed]CreateGeometryCollectionFromSources and GeometryCollectionTerminal are both getting a deprecation warning on 5.6.

The 5.6 version of those indeed generates a GS that seems to be lacking the material, only to appear once the GC breaks.

I’ll investigate some more and let you know.

All the best,

[mention removed]​

4

Heya [mention removed]​

Thank you for your investigation thus far!

Just wanted to update you that our Asset Art team have alerted that the same observable issue happens in Geometry Collections whose Materials are changed inside the Geometry Collection Asset Defaults.

Cheers,

Josh.

5

Hello [mention removed]​

Thank you again for bringing this issue to our attention.

I’ve made a JIRA report at: Unreal Engine Issues and Bug Tracker (UE\-306177)

Please note that it can take some time to be made publicly accessible.

We don’t provide updates on EPS, but if you would like to track the resolution, check the link for the status.

I’ll close the case, but feel free to reply if you have anything else to add.

All the best,

[mention removed]​