[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:
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?
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
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!
answered Nov 01 '16 at 09:24 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here