Moving Actors with InstancedStaticMeshes leaves collision behind

anonymous_user_adcf0aef · May 6, 2015, 1:25pm

Hello! I’d like to report a bug. When moving, scaling, or rotating an actor that uses instances mesh components, the component’s collision is left behind. But when using regular static meshes, the collision follows the actor. It would be great if this could be fixed before 4.8 releases.

anonymous_user_b9532c9a · May 6, 2015, 2:28pm

Hi ,

This is a known issue that is currently under assessment as UE-13673. It is marked as major but has no resolution as of yet. Unfortunately I do not have a timeframe of when this will be fixed.

John_Alcatraz · February 22, 2016, 9:30pm

I think I have never seen a “major” bug taking so long time to get fixed

anonymous_user_3149ac211 · March 8, 2016, 6:37am

[=;285919]
Hello! I’d like to report a bug. When moving, scaling, or rotating an actor that uses instances mesh components, the component’s collision is left behind. But when using regular static meshes, the collision follows the actor. It would be great if this could be fixed before 4.8 releases.
[/]

Right before to transform some actor which used ISMC, use the node “Set Collision Enabled”->“No Collision” and right after transforming restore the collision with the node “Set Collision Enabled”->“Query Only”