x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[Closed] Destructible Child Actor causes Incorrect Culling If Spawned Away from Origin

Title is self explanatory.

This is pretty easy to reproduce in vanilla 4.12.5:

  1. Create a Destructible Mesh (try with starter content shapes)

  2. Create a Destructible Actor and set the Destructible Mesh

  3. Create an Actor and add the Destructible Actor as a ChildActor.

  4. Spawn the Parent Actor anywhere other than the origin through the Blueprint Spawn Actor function.

  5. Press play and look at where you placed the destructible mesh with the origin out of view.

  6. Invisible!

  7. If you bring the origin into view, it will no longer be culled.

The hack workaround is to just move the actor at least one frame after constructing it. It looks like that calls "ApexDestructibleActor->setGlobalPose(GlobalPose)" in OnUpdateTransform. Do child actors maybe no longer have a scene yet on construction anymore?

Cheers, Rob

Product Version: Not Selected
Tags:
more ▼

asked Nov 01 '16 at 09:24 PM in Bug Reports

avatar image

Answers.Archive STAFF
1.9k 197 306 679

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed Nov 01 '16 at 09:26 PM by AndrewHurley for the following reason:

The question is answered, right answer was accepted


1 answer: sort voted first

Hi Robert,

I managed to reproduce the issue you reported in 4.12.5, however the issue has been fixed in 4.13 and the destructible appears as it should with correct bounds. I can't find any specific changes in that period in destructibles which would have caused or rectified this issue, it's possible that some changes to child actor registration have solved it.

Thanks for the report!

Benn.

more ▼

answered Nov 01 '16 at 09:24 PM

avatar image

Answers.Archive STAFF
1.9k 197 306 679

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question