[BUG REPORT] Destructible Mesh spawned as child actor has no bounds

Development Programming & Scripting Blueprint
, , , , ,
1

##Branch:
Binary

##Build version:
From 4.8 to 4.12

##Detailed description of the issue:

Destructible meshes that spawn as child actor components have no bounds.

They flash and flicker based on the camera position - also occluding everything behind them. Increasing bounds scale doesn’t help (multiplying by zero) nor does using the parent bounds.

The DMs works fine if it is not a child actor.

##Repro Steps

Action 1: Create destructible mesh

Action 2: Create BP actor that spawns said destructible mesh as a child actor.

Action 3: Use a “Get Bounds” and “Print String” : see the resulting 0.

Additional Information

  • This worked fine in 4.7 - and incorrectly since 4.8,4.9 and 4.10.
  • I am using Blueprints.
  • I posted this bug report in June 2014. It would be nice to have an official response.

##System Specs:

  • Windows 10
  • AMD FX 8350
  • AMD 7970
  • 16GB DDR3 RAM
  • 2x 7200RPM HDDs in Raid-0
2

It sounds like you are spawning multiple meshes on top of each other. Make sure you use an index variable in the get array.

3

Thanks for the reply.

Sadly it’s not an issue of Z-fighting. Sometimes they will flat out disappear if the camera is at a certain angle.

The index for this particular one is required to be 1 - the actual location is set in a separate function and the objects correctly spawn in their multiple locations.

This also worked in previous iterations of 4.8 (I think)

EDIT:

I’ve just played the game with “Show Bounds Enabled” and noticed that the destructible meshes have no visible bounds - unlike the other child components, which do have visible bounds (and do not flicker.)

These do have bounds when not child components (but they are required to be so here)

Also just tried 4.9 preview, same deal.

Also, using a “Get Component Bounds” and attached to a Print String - the results were 0 - furthering what I had thought.

4

This was asked in June, it’s now September - BUMP

5

experiencing the same issue too…any advice?

6

Bump?

This was asked in June…it’s now November

7

Still doesn’t work in 4.10

8

Bump, please I have the same issue and it’s really annoying, is there a workaround for this? I cannot spawn any actors from C++ that contain a Destructible Mesh or they will flicker/disappear.

Edit: I found a workaround at least to see the DM ingame, just set simulate physics to true.

9

Glad you found a workaround. Sadly this doesn’t work for me since there are a lot of moving elements, having physics set kinda messes that up.

10

This is still a problem as of 4.12.5, but I think I found a possible workaround - parent the object to an appropriately sized cube, make the cube have no collisions and not visible and then make the DM “Use Attach Parent Bound.” This essentially lets you customise the bounds box as you see fit, even though the DM bounds are missing.

Obviously this isn’t a great solution as having to wrap most objects in my levels in an invisible cube just to get it render is bound to have some overhead, but at least they’re working for now.

11

This one is similar to my problem: Destructible child actor transform bug - World Creation - Unreal Engine Forums

12

Thanks, I’m checking it out now - hopefully this does work for me in 4.13 too.

13

This appears to have been fixed since 4.13/4.14 (though now there are other issues with child actors…but that’s a different story!)