Ensure fail in GeometryCollection IdentifySimulatableElements

Development Asset Creation
, ,
1

We have currently no idea how data get in this state.

2

Steps to Reproduce
Hola! We have some GeometryCollection failing the ensure in FGeometryCollectionPhysicsProxy’s IdentifySimulatableElements() triggering the ReportError(TEXT(“Objects are not contiguous. This breaks assumptions later in the pipeline”)). We don’t see any behavior issue on the geometry collection in game.

We don’t know how the data get in this state nor how we could reorder these objects from the Facture tools.

Is this ensure a real threat?

Is there a way to reorder these objects in tools?

Cheers!

3

Hello [mention removed]​

Thank you for reaching out.

I’ve just been assigned this case and will look it up for you.

All the best,

[mention removed]​

4

Hello [mention removed]​

I’ve been trying to reproduce the issue, but I’ve been unsuccessful so far.

Can you give me more details on the specifics?

How are you authoring the offending Geometry Collection?

Are you using the Editor’s Fracture Mode?

Would it be possible to share the broken Geometry Collection in a clean project, so I can take a look?

I hope to hear from you soon.

All the best,

[mention removed]​

5

Hola [mention removed]​ !

Yes we use the Editor’s Fracture Mode, and we don’t know how it happen. If we figure out how to repro the issue, I’ll come back here to share the steps, and provide a clean project if required.

Cheers!

6

Hola [mention removed]​ !

No, it’s not stock 5.5. I don’t think we have any changes in geometry collection fracture tools, but I can’t be 100% sure.

Cheers!

7

Hola [mention removed]​!

Sure, let me know!

I’ll keep trying on my end as well.

Just to confirm, are you using stock 5.5?

All the best,

[mention removed]​

8

Hello [mention removed]​

I’m trying to reproduce this issue, but so far, I’ve had no success.

Am I right to assume this happens to a single, specific Geometry Collection?

If so, would it be possible to share it?

This happens during Play In Editor, regular physics simulation, or does it involve Chaos Cache Manager, Sequencer, etc.?

Are you using Async Physics?

Is this single or multiplayer, client or server side?

Do you suspect the issue might be tied to the mesh you are fracturing?

Any information helps.

I look forward to hearing from you soon.

All the best,

[mention removed]​